- Users - libvirt List Archives

unsubscribe
by FRANK, Michael 11 Jan '22

11 Jan '22

unsubscribe The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.

1 0

error during host deploy
by Dana Elfassy 11 Jan '22

11 Jan '22

Hi, While running a test case of adding hosts on ovirt system tests there was a failure while the following command was executed: vdsm-tool configure --force On libvirtd log I found this error: 2021-12-17 00:11:41.753+0000: 28031: error : virNetTLSContextNew:732 : Unable to generate diffie-hellman parameters: Error in public key generation. How would you suggest to debug this failure? attaching libvirtd & journalctl logs libvirt version: 7.10.0, package: 1.module_el8.6.0+1046+bd8eec5e Thanks, Dana The error from host deploy log: "2021-12-17 01":"11":"45 CET - fatal":[ ost-basic-suite-master-host-0 ]:"FAILED! =>"{ "changed":true, "cmd":[ "vdsm-tool", "configure", "--force" ], "delta":"0:00:06.908971", "end":"2021-12-17 01:11:42.815057", "msg":"non-zero return code", "rc":1, "start":"2021-12-17 01:11:35.906086", "stderr":"Error: ServiceOperationError: _systemctlStart failed\nb'Job for libvirtd.service failed because a fatal signal was delivered causing the control process to dump core.\\nSee \"systemctl status libvirtd.service\" and \"journalctl -xe\" for details.\\n' ", "stderr_lines":[ "Error: ServiceOperationError: _systemctlStart failed", "b'Job for libvirtd.service failed because a fatal signal was delivered causing the control process to dump core.\\nSee \"systemctl status libvirtd.service\" and \"journalctl -xe\" for details.\\n' " ], "stdout":"\nChecking configuration status...\n\nlvm is configured for vdsm\nCurrent revision of multipath.conf detected, preserving\nlibvirt is already configured for vdsm\nSUCCESS: ssl configured to true. No conflicts\nsanlock is configured for vdsm\nManaged volume database is already configured\n\nRunning configure...\nReconfiguration of libvirt is done.\nReconfiguration of passwd is done.", "stdout_lines":[ "", "Checking configuration status...", "", "lvm is configured for vdsm", "Current revision of multipath.conf detected, preserving", "libvirt is already configured for vdsm", "SUCCESS: ssl configured to true. No conflicts", "sanlock is configured for vdsm", "Managed volume database is already configured", "", "Running configure...", "Reconfiguration of libvirt is done.", "Reconfiguration of passwd is done." ] }

2 8

回复： Failed in using LD_PRELOAD to hook mmap system call in qemu(through libvirt)
by Xiong。 07 Jan '22

07 Jan '22

On Thu, Jan 06, 2022 at 07:44:25PM +0800, Xiong。 wrote: > Dear sir: >     I want to hook mmap system call in qemu, and I use > libvirt to passthrough the environment argument like this: >  <qemu:commandline> >    <qemu:env name='LD_PRELOAD' value='/glibcHookMMAP.so'/> >  </qemu:commandline> > But it failed. I can hardly find out what is the matter! > The log in libvirt like this:ERROR: ld.so: object > '/glibcHookMMAP.so' from LD_PRELOAD cannot be preloaded > (cannot open shared object file): ignored.    Firstly, > I think it's the problem of authority. But the file > glibcHookMMAP.so has been done with command `chmod 777`. > My environment is as follows: Ubuntu 18.04.2 Linux > 5.4.0-92 libvirt 4.0.0 qemu 2.11.1 On Thu, Jan 06, 2022 at 09:47:25PM +0800, Daniel P. Berrangé。 wrote: > Aside from normal file permissions, the other likely problem on Ubuntu > will be AppArmor policy. It likely won't allow QEMU to load files from > the / directory - if you put your .so in /usr/local/lib it might > work. On Thu, Jan 07, 2022 at 09:27:25AM +0800, Xiong。 wrote: > I have a try, but it does not work and makes the same warning: > ld.so: object '/usr/local/lib/glibcHookMMAP.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. > However, I use qemu command directly and it works. Command is like this: > sudo LD_PRELOAD=/usr/local/lib/glibcHookMMAP.so qemu-system-x86_64 -enable-kvm ...(other args). > After that, I get print information with my hook program. And I think the problem is in passing the environment args in libvirt. Sorry, I find out what's the matter. The AppArmor policy limits the libvirt, and modifing configuration works. Thank you for your advise!

1 0

Failed in using LD_PRELOAD to hook mmap system call in qemu(through libvirt)
by Xiong。 07 Jan '22

07 Jan '22

Dear sir:      I want to hook mmap system call in qemu, and I use libvirt to passthrough the environment argument like this:<qemu:commandline> <qemu:env name='LD_PRELOAD' value='/glibcHookMMAP.so'/> </qemu:commandline>    But it failed. I can hardly find out what is the matter! The log in libvirt like this:ERROR: ld.so: object '/glibcHookMMAP.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.    Firstly, I think it's the problem of authority. But the file glibcHookMMAP.so has been done with command `chmod 777`.    My environment is as follows: Ubuntu 18.04.2 Linux 5.4.0-92 libvirt 4.0.0 qemu 2.11.1     Look forward to your feedbacks.     Sincerely yours

2 2

config vhost-user-scsi
by Jiatong Shen 06 Jan '22

06 Jan '22

Hello, I am trying spdk vhost-user. I managed to plug in vhost-user-blk, but did not find the doc guiding me through setting up vhost-user-scsi. Is it supported now? Thank you. -- Best Regards, Jiatong Shen

1 0

Allow unsafe migration - ?
by lejeczek 06 Jan '22

06 Jan '22

Hi guys. Is it possible to allow 'unsafe' migration globally? many thanks, L.

3 4

simulating multiple hypervisors with the test driver
by Tom Ammon 05 Jan '22

05 Jan '22

Hello, I'm working on a python application that will manage multiple remote libvirt hypervisors. I've been using the test:///default uri for single-hypervisor tests, and it works great. I'd like to simulate connecting to two different remote hypervisors, however, in my testing so far it appears that multiple connections to the test:///default uri just look like different connections to the same hypervisor. Here's what I tried : conn_one = libvirt.open('test:///default') <build and start some domains> one_vms = conn_one.listAllDomains(0) for x in one_vms: print(f"The vm in set one is {x.name()}") <get list of all the domains I just built> conn_two = libvirt.open('test:///default') <build and start some different domains> two_vms = conn_two.listAllDomains(0) for z in two_vms: print(f"The vm in set one is {z.name()}") <get list of ALL domains including those created with conn_one, not just those created using the conn_two instance> What I would like is to be able to spin up two completely independent instances of the test driver so that it can simulate two different hypervisors/instances of libvirtd. Is that possible? Thanks, Tom -- ----------------------------------------------------------------------------- Tom Ammon M: (737) 400-9042 thomasammon(a)gmail.com -----------------------------------------------------------------------------

2 2

Best way to install guest when it is not listed in output of osinfo-query os
by john doe 04 Jan '22

04 Jan '22

Hello all, I would like to install Debian Bullseye using virt-install, as part of the command I usually specify the OS used with the option '--os-variant'. This works great untill Buster ('debian10'), but now the guest is Bullseye ('debian11') and is not listed in the output of 'osinfo-query os' (1). If I don't use the '--os-variant' flag I get the following warning: "WARNING No operating system detected, VM performance may suffer. Specify an OS with --os-variant for optimal results." Should I ignore the warning or what is the best way forward to install a Debian Bullseye guest? Both the host and the guest are Debian 11. 1) https://lists.debian.org/debian-user/2021/12/msg00742.html -- John Doe

5 6

[FOSDEM][CFP] Virtualization & IaaS Devroom
by Piotr Kliczewski 16 Dec '21

16 Dec '21

We are excited to announce that the call for proposals is now open for the Virtualization & IaaS devroom at the upcoming FOSDEM 2022, to be hosted virtually on February 5th 2022. This year will mark FOSDEM’s 22nd anniversary as one of the longest-running free and open source software developer events, attracting thousands of developers and users from all over the world. Due to Covid-19, FOSDEM will be held virtually this year on February 5th & 6th, 2022. About the Devroom The Virtualization & IaaS devroom will feature session topics such as open source hypervisors and virtual machine managers such as Xen Project, KVM, bhyve, and VirtualBox, and Infrastructure-as-a-Service projects such as KubeVirt, Apache CloudStack, Foreman, OpenStack, oVirt, QEMU and OpenNebula. This devroom will host presentations that focus on topics of shared interest, such as KVM; libvirt; shared storage; virtualized networking; cloud security; clustering and high availability; interfacing with multiple hypervisors; hyperconverged deployments; and scaling across hundreds or thousands of servers. Presentations in this devroom will be aimed at users or developers working on these platforms who are looking to collaborate and improve shared infrastructure or solve common problems. We seek topics that encourage dialog between projects and continued work post-FOSDEM. Important Dates Submission deadline: 20th of December Acceptance notifications: 25th of December Final schedule announcement: 31st of December Recorded presentations upload deadline: 15th of January Devroom: 6th February 2022 Submit Your Proposal All submissions must be made via the Pentabarf event planning site[1]. If you have not used Pentabarf before, you will need to create an account. If you submitted proposals for FOSDEM in previous years, you can use your existing account. After creating the account, select Create Event to start the submission process. Make sure to select Virtualization and IaaS devroom from the Track list. Please fill out all the required fields, and provide a meaningful abstract and description of your proposed session. Submission Guidelines We expect more proposals than we can possibly accept, so it is vitally important that you submit your proposal on or before the deadline. Late submissions are unlikely to be considered. All presentation slots are 30 minutes, with 20 minutes planned for presentations, and 10 minutes for Q&A. All presentations will need to be pre-recorded and put into our system at least a couple of weeks before the event. The presentations should be uploaded by 15th of January and made available under Creative Commons licenses. In the Submission notes field, please indicate that you agree that your presentation will be licensed under the CC-By-SA-4.0 or CC-By-4.0 license and that you agree to have your presentation recorded. For example: "If my presentation is accepted for FOSDEM, I hereby agree to license all recordings, slides, and other associated materials under the Creative Commons Attribution Share-Alike 4.0 International License. Sincerely, <NAME>." In the Submission notes field, please also confirm that if your talk is accepted, you will be able to attend the virtual FOSDEM event for the Q&A. We will not consider proposals from prospective speakers who are unsure whether they will be able to attend the FOSDEM virtual event. If you are experiencing problems with Pentabarf, the proposal submission interface, or have other questions, you can email our devroom mailing list[2] and we will try to help you. Code of Conduct Following the release of the updated code of conduct for FOSDEM, we'd like to remind all speakers and attendees that all of the presentations and discussions in our devroom are held under the guidelines set in the CoC and we expect attendees, speakers, and volunteers to follow the CoC at all times. If you submit a proposal and it is accepted, you will be required to confirm that you accept the FOSDEM CoC. If you have any questions about the CoC or wish to have one of the devroom organizers review your presentation slides or any other content for CoC compliance, please email us and we will do our best to assist you. Call for Volunteers We are also looking for volunteers to help run the devroom. We need assistance with helping speakers to record the presentation as well as helping with streaming and chat moderation for the devroom. Please contact devroom mailing list [2] for more information. Questions? If you have any questions about this devroom, please send your questions to our devroom mailing list. You can also subscribe to the list to receive updates about important dates, session announcements, and to connect with other attendees. See you all at FOSDEM! [1] https://penta.fosdem.org/submission/FOSDEM22 [2] iaas-virt-devroom at lists.fosdem.org

1 1

Libvirt on little.BIG ARM systems unable to start guest if no cpuset is provided
by Qu Wenruo 14 Dec '21

14 Dec '21

Hi, Recently I got my libvirt setup on both RK3399 (RockPro64) and RPI CM4, with upstream kernels. For RPI CM4 its mostly smooth sail, but on RK3399 due to its little.BIG setup (core 0-3 are 4x A55 cores, and core 4-5 are 2x A72 cores), it brings quite some troubles for VMs. In short, without proper cpuset to bind the VM to either all A72 cores or all A55 cores, the VM will mostly fail to boot. Currently the working xml is: <vcpu placement='static' cpuset='4-5'>2</vcpu> <cpu mode='host-passthrough' check='none'/> But even with vcpupin, pinning each vcpu to each physical core, VM will mostly fail to start up due to vcpu initialization failed with -EINVAL. This brings a problem, in theory RK3399 SoC should out-perform BCM2711 in multi-core performance, but if a VM can only be bind to either A72 or A55 cores, then the performance is no longer competitive against BCM2711, wasting the PCIE 2.0 x4 capacity. I guess with projects like Asahi Linux making progress, there will be more and more such problems. Any clue on how to properly pass all physical CPU cores to VM for little.BIG setup? Thanks, Qu

5 17

Guest vm doesn't recover after the nfs connection resume
by Liang Cong 14 Dec '21

14 Dec '21

Dear developers： I found one issue during regular test and I could not confirm whether it is a libvirt|qemu issue or it is a nfs client issue or it is not an issue, so could you help to check it? Below is the issue reproduce steps: 1.there is a nfs server with exports file like: /nfs *(async,rw,no_root_squash) 2. host machine soft mount nfs: mount nfs_server_ip:/nfs /var/lib/libvirt/images/nfs -o v4,soft 3. start a guest vm with disk tag xml like below: <disk type='file' device='disk'> <driver name='qemu' type='qcow2'/> <source file='/var/lib/libvirt/images/nfs/RHEL-8.6.0-20211102.1-x86_64.qcow2' index='1'/> <backingStore/> <target dev='vda' bus='virtio'/> <alias name='virtio-disk0'/> </disk> 4.Start the vm and during the guest vm boot, apply the iptables rule to drop the nfs connection to nfs server iptables -A OUTPUT -d nfs_server_ip -p tcp --dport 2049 -j DROP 5. Wait until the error log appear in /var/log/message kernel: nfs: server nfs_server_ip not responding, timed out 6. delete the iptables rule to retain the connection to nfs server iptables -D OUTPUT -d nfs_server_ip -p tcp --dport 2049 -j DROP 7. check the guest vm, found the boot process with error and can not recover. rror: ../../grub-core/disk/i386/pc/biosdisk.c:546:failure reading sector 0x7ab8 from `hd0'. error: ../../grub-core/disk/i386/pc/biosdisk.c:546:failure reading sector 0x9190 from `hd0'. error: ../../grub-core/disk/i386/pc/biosdisk.c:546:failure reading sector 8. found there is error message in /var/log/message kernel: NFS: __nfs4_reclaim_open_state: Lock reclaim failed! Thanks Liang Cong

2 3

internal error - invalid characters
by lejeczek 13 Dec '21

13 Dec '21

Hi guys. Have you seen something like this below? ... internal error: The string resource has invalid characters in its value internal error: The provided value contains invalid characters: Solarstorm SFN5162F SFP+ Server Adapter this if from journal logs. This hardware model of the NICs which comprise make up a team/bridge which libvirt net use, but what would 'libvirtd' bother with that? many thanks, L.

3 3

Libgfapi gone too?
by lejeczek 12 Dec '21

12 Dec '21

Hi guys. Is glusterFS/libgfapi support removed (permanently) too? In CentOS 9 Stream. thanks, L.

5 13

a test email (& dmarc) @admins
by lejeczek 10 Dec '21

10 Dec '21

hi guys. I sent email a while ago and I wonder, also having not received a single reply, because I did not get that own email - is there are problem I'm having here or DMARC(yahoo & others?) are not fixed in by this mailing list - would an admin(anybody) know? many thanks, L.

2 4

Qemu monitor info tlb gives unable to encode message payload
by Philipp Klocke 09 Dec '21

09 Dec '21

Hi, the command virsh qemu-monitor-command ubuntu_vm --hmp --cmd "info tlb" fails with "error: Unable to encode message payload". I found a bugtracker entry for a similiar error [1], but I don't if this is the same error (message too large). I also don't know how large an info tlb message is. Preferably I would not have to recompile libvirt just to issue this monitor command.. Then I thought about circumventing the error by connecting directly to the qemu monitor via netcat, but I found a thread [2] that says I cannot add my own "-monitor tcp:..." to the Qemu commandline arguments. Could someone help me with this? Best, Philipp [1] https://bugzilla.redhat.com/show_bug.cgi?id=1440683 [2] https://libvirt-users.redhat.narkive.com/E0UTmdhU/is-there-a-way-to-disable…

3 5

No QXL in CentOS 9 Stream?
by lejeczek 07 Dec '21

07 Dec '21

Hi. There seems to be no QXL (and Spice?) support in versions from CentOS 9 repos. Would anybody know if that intended, because something else replaces qxl perhaps? thanks, L

2 1

Libvirt Snapshot Question
by Elias Mobery 03 Dec '21

03 Dec '21

Hi everybody! I'm using a snapshot purely for writes and was wondering if it's possible to clear/empty the snapshot after it reaches a certain size? Created with: virsh snapshot-create-as --disk-only I tried deleting and recreating it but get an error at deletion: virsh snapshot-delete Error: source for disk 'vda' is not a regular file I also tried virsh snapshot-create-as --no-metadata --disk-only But the same error as above pops up when trying to delete. Any ideas?

2 8

qemu-img create with extended_l2=on, followed by virt-install
by Richard Taubo 02 Dec '21

02 Dec '21

Hi! I have read the following blog post: https://blogs.igalia.com/berto/2020/12/03/subcluster-allocation-for-qcow2-i… and watched the video displayed there. 1) To make qcow2 as fast as possible, does it make sense to do the following: [#] qemu-img create -f qcow2 -o extended_l2=on,cluster_size=128k my_image.qcow2 1000GB And then: [#] virt-install —name=MyVM --disk path=my_image.qcow2,size=1000 . . . Will this overwrite the qcow2 file already created or will it keep its characteristics? Does it make sense? 2) I wont’t be moving the VM around much and have the space I need, so I wonder if it will be faster to do the following: [#] qemu-img create -o preallocation=full -f qcow2 my_image.qcow2 1000GB And then: [#] ] virt-install —name=MyVM --disk path=my_image.qcow2,size=1000,bus=scsi,sparse=false . . . (Running bus=scsi so I can trim the image ). I could use a dedicated disk for the VM instead of using qcow2, but I like the flexibility of qcow2. Thanks a lot for any information about this! :-) Best regards, Richard Taubo

1 0

migrate libvirt config between machines
by daggs 01 Dec '21

01 Dec '21

Greetings, I'd like to migrate my current libvirt config from one machine to another, what is the best way to do so? Thanks

3 4

qemu-img create with preallocation=full and compression_type=zlib
by Richard Taubo 01 Dec '21

01 Dec '21

Hi! When running this command on Fedora 35 I get: [#] qemu-img create -o preallocation=full -f qcow2 /var/vm_mail/mytest.qcow2 10GB => Formatting '/var/vm_mail//mytest.qcow2', fmt=qcow2 . . . preallocation=full compression_type=zlib . . . ." Question: When using 'preallocation=full’ I was surprised that the resulting qcow2 image includes the 'compression_type=zlib’ part. Why/when is this compression used when the qcow2 image is fully preallocated? Thanks for input on this! :-) Best regards Richard Taubo

2 2

virsh create fails with "Unable to find any firmware to satisfy 'efi'" for aarch64 guest on macOS
by Nathan Vander Wilt 30 Nov '21

30 Nov '21

I am having trouble when I `virsh create test.xml` with an aarch64 guest on a macOS (Apple Silicon) host. I've wrestled with a variety of issues but the one I simply haven't been able to get past is this regarding the UEFI firmware: error: Failed to create domain from test.xml error: operation failed: Unable to find any firmware to satisfy 'efi' This is with `virsh --version` of 7.9.0 and `qemu-system-aarch64 --version` of 6.1.0, both installed via the common `brew` tool from its main 'homebrew/core' tap. I have confirmed that the loader/nvram files referenced do exist. Running `qemu-system-aarch64 -L help` outputs two lines: /opt/homebrew/Cellar/qemu/6.1.0_1/bin/../share/qemu-firmware /opt/homebrew/Cellar/qemu/6.1.0_1/bin/../share/qemu The …/share/qemu-firmware folder does NOT exist, but symlinking it to a …/share/qemu/firmware folder which does exist does not improve the situation. I have also tried renaming the …/share/qemu/firmware folder (e.g. `mv firmware zzz-firmware`) as some notes I found led me to believe that libvirst might ignore my loader/nvram settings entirely if QEMU had the "new" firmware JSON configuration stuff there? But again no improvement…. How can I debug this further? What should I try next? thanks, -natevw --- the test.xml domain configuration I am trying --- <domain type="qemu" xmlns:qemu="http://libvirt.org/schemas/domain/qemu/1.0"> <name>test1</name> <uuid>D45FCA3E-B873-4608-A0B8-3D8529E7CFB7</uuid> <memory unit="MiB">2048</memory> <cpu mode="host-model" check="partial" /> <vcpu>2</vcpu> <clock offset="utc"/> <qemu:commandline> <qemu:arg value='-accel'/> <qemu:arg value='hvf'/> </qemu:commandline> <os firmware="efi"> <type arch="aarch64" machine="virt">hvm</type> <loader readonly="yes" secure="no" type="pflash">/opt/homebrew/share/qemu/edk2-aarch64-code.fd</loader> <nvram template="/opt/homebrew/share/qemu/edk2-arm-vars.fd">/Users/me/vm_testing/vm-test1.efi.fd</nvram> <bootmenu enable="no"/> <boot dev="hd"/> </os> <features> <acpi/> <gic version="3"/> <pae/> </features> <devices> <emulator>/opt/homebrew/bin/qemu-system-aarch64</emulator> <disk type="file" device="disk"> <driver name="qemu" type="qcow2"/> <source file="/Users/me/vm_testing/vm-test1.qcow2"/> <target dev="vda" bus="virtio"/> </disk> <interface type="network"> <source network="default"/> <model type="virtio"/> </interface> <console type="pty"> <target type="serial" port="0"/> </console> <rng model="virtio"> <backend model="random">/dev/urandom</backend> </rng> </devices> </domain>

5 10

Fwd: Installing virtiofs drivers on Windows 11....
by Mario Marietto 30 Nov '21

30 Nov '21

Hello to everyone. I'm testing Windows 11 with bhyve and I've found an annoying problem that prevents me from completing some tasks that I'm working on. It seems that the virtio-9p driver does not work inside the Windows 11 os emulated with bhyve and maybe also with qemu-kvm. When Windows 11 is launched,I don't see the folder "mnt" mounted on the root folder of Windows 11. Below you can see which bhyve parameters I've used : bhyve -S -c 4 -m 8G -w -H \ -s 0,hostbridge \ -s 1,ahci-cd,/home/marietto/Downloads/virtio/virtio-win-0.1.208.iso \ -s 2,ahci-hd,/mnt/da0p1/Backups/OS/bhyve/Windows/win11.img \ -s 3,fbuf,tcp=0.0.0.0:5900,w=1440,h=900,wait \ -s 8,virtio-net,tap0 \ ----> -s 9,virtio-9p,sharename=/mnt \ -s 30,xhci,tablet \ -s 31,lpc \ -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd \ vm0 Investigating a little bit more and reading from this tutorial : https://virtio-fs.gitlab.io/howto-windows.html I've realized that there should be some problem with the WinFsp <http://www.secfs.net/winfsp> - Windows File System Proxy and or with the virtiofs PCI device driver because I'm not able to enable the virtiofs service with the command used on the tutorial : C:\> sc start VirtioFsSvc it gives the error : "the dependency service does not exist or it has been marked for the elimination. I've attached some screenshots to help you to understand what's happening. Please help me,thanks. Attached screenshots : https://ibb.co/m5vm1hd https://ibb.co/Qd6TS5d https://ibb.co/3018SGd -- Mario.

2 7

virsh blockjob $domain --abort
by Jeff Brown 30 Nov '21

30 Nov '21

Please advise: After a scheduled crontab snapshot backup of a VM it failed to do a blockcommit, and is currently writing to both the snapshot and the original QCOW2 images. (I don't think it's a bug, and suspect that I caused it by running the backup script manually while the snapshot was already running.) $ virsh blockcommit VM sda --active --pivot --shallow --verbose error: block copy still active: disk 'sda' already in active block job $ virsh blockjob VM sda --info Active Block Commit: [100 %] $ virsh domblkerror VM No errors found Running on Debian 9 (Stretch). $ virsh version Compiled against library: libvirt 3.0.0 Using library: libvirt 3.0.0 Using API: QEMU 3.0.0 Running hypervisor: QEMU 2.8.1 Now, I've read up on the probable solution, somewhat, but running $ virsh blockjob $domain --abort on this production server scares me; and I'm just asking whether it would be advisable to stop services and make a full data backup prior to doing so? It would entail taking the services offline for at least an hour. The snapshot is currently at 12GB, and according to blockjob --info the VM image is 100% in synch. Will appreciate any advice. Thank you. Best regards, Jeff

2 1

Libvirt + Debian Live = Heart Attack
by Elias Mobery 25 Nov '21

25 Nov '21

Hi everyone! I've built a Debian Live ISO with packages qemu and libvirt to run a VM in the live environment. The guest images are placed in /var/lib/libvirt/images and 2GB each. Everything works great, except for one issue. When starting a VM, libvirt automatically issues a chown command to the images, changing ownership. This results in a copy of the images being created in /run/live/overlay/rw/var/lib/libvirt/images I don't want these copies to be made but can't stop it. I've tried editing qemu.conf user/group, dynamic ownership etc. without any luck. Is there a way to STOP libvirt from changing the ownership of these images?

3 8

Questions on device-added and device-removed events
by Han Han 23 Nov '21

23 Nov '21

Hi developers, When the guest OS is booting, the event for live attachment could be caught by libvirt, while the event for live detachment could not. Version: libvirt-7.9 qemu-kvm-6.1 Steps: Terminal 1: ➜ ~ virsh event --loop --all Terminal 2: ➜ ~ virsh start avocado-vt-vm1; qemu-img create /tmp/vdb 10M; virsh attach-disk avocado-vt-vm1 /tmp/vdb vdb; virsh detach-disk avocado-vt-vm1 vdb The outputs from terminal 1: event 'agent-lifecycle' for domain 'avocado-vt-vm1': state: 'disconnected' reason: 'domain started' event 'lifecycle' for domain 'avocado-vt-vm1': Resumed Unpaused event 'lifecycle' for domain 'avocado-vt-vm1': Started Booted event 'device-added' for domain 'avocado-vt-vm1': virtio-disk1 event 'agent-lifecycle' for domain 'avocado-vt-vm1': state: 'connected' reason: 'channel event' As you can see, the device live attachment and the device detachment are both executed when the guest OS is booting, but there is only the event 'device-added' is recorded. So my questions are: 1. Is it the expected results for the results above? 2. If so, what is the internal difference between 'device-added' and 'device-removed'? 3. I notice there is the DEVICE_DELETED event in qmp? Any relation between the 'device-removed' of libvirt and the DEVICE_DELETED of qmp?

2 1