- Users - libvirt List Archives

virsh domifaddr domain does not show static IP
by Kaushal Shriyan 12 Sep '21

12 Sep '21

Hi, I have assigned static IP for all the below KVM Guest VM's. Is there a way to find out the IP of the below VM's from virsh utility or any other utility? virsh domifaddr testdobssbahrainms does not show the static IP. # virsh list --all Id Name State ----------------------------------------- 1 testdobssbahrainms running 2 testdosstomcatpibms running 3 testdobsstomcatkineticms running 4 testdobsstomcatmsbms running 5 testdobsstomcatfdms running 6 testdobsstomcathsbcnetms running 7 testdobsstomcatdbbms running 8 testdobssapigeedev running # # virt-install --version 2.2.1 # cat /etc/redhat-release CentOS Stream release 8 #virsh domifaddr testdobssbahrainms #Name MAC address Protocol Address ------------------------------------------------------------------------------- Please guide. Thanks in advance. Best Regards, Kaushal

3 4

startupPolicy issue when changing CD
by Vojtech Juranek 10 Sep '21

10 Sep '21

Hi, when adding support for CD disk on block based storage into oVirt, I spotted following issue. When starting VM without CD, we add startupPolicy='optional' attribute into <source> element. Whole XML looks like this: <disk type='file' device='cdrom'> <driver name='qemu' error_policy='report'/> <source startupPolicy='optional'/> <target dev='sdc' bus='sata'/> <readonly/> <alias name='ua-d7003457-63c3-4c98-80f0-08ab5042c65e'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> To change/insert CD we use libvirt.updateDeviceFlags() with XML which looks like this (for block based disk): <?xml version='1.0' encoding='utf-8'?> <disk device="cdrom" type="block"> <source dev="/rhev/data-center/mnt/blockSD/cdac2a0c-b110-456d-a988-7d588626c871/images/638247d7-b4b1-4d98-87fa-c90235fcf4b1/145e7cd2-f92d-4eec-a8fb-6835b4b652e1" /> <target bus="sata" dev="sdc" /> </disk> However, updateDeviceFlags() fails with libvirt.libvirtError: XML error: 'startupPolicy' is only valid for 'file' type volume What is the reason for this error? We don't use `startupPolicy` attribute for block based disks, as shown on example above. Thanks in advance. Vojta

2 3

snapshot creation broken recently?
by Štěpán Němec 09 Sep '21

09 Sep '21

Hello, until very recently I had been happily creating snapshots of running VMs (created using virt-install) simply with virsh --connect qemu:///system snapshot-create-as <domain-name> <snapshot-name> Now when I try to do that I get the following error: Error creating snapshot: operation failed: Failed to take snapshot: pre-save failed: qxl Same thing trying to create a snapshot from virt-manager (which also used to work). Here's the full backtrace (as displayed in virt-manager): Error: Error while writing VM state: Unknown error -1 Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 65, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/details/snapshots.py", line 237, in _do_create_snapshot self.vm.create_snapshot(xml) File "/usr/share/virt-manager/virtManager/object/domain.py", line 1124, in create_snapshot self._backend.snapshotCreateXML(xml, flags) File "/usr/lib/python3.9/site-packages/libvirt.py", line 3059, in snapshotCreateXML raise libvirtError('virDomainSnapshotCreateXML() failed') libvirt.libvirtError: operation failed: Failed to take snapshot: pre-save failed: qxl Error: Error while writing VM state: Unknown error -1 I am on Arch Linux (x86_64), using the distro packages. Checking my pacman logs, might update of qemu-headless from 6.0.0 to 6.1.0 have something to do with that? (Since then, libvirt has also been updated from 7.6.0 to 7.7.0, but I see no change WRT the problem described.) I would appreciate any advice on how to further investigate and/or work around the problem. (I checked https://gitlab.com/libvirt/libvirt/-/issues and didn't find anything that seemed related.) Thanks, Štěpán

2 2

one qustion about the snapshot of the libvirt, thanks.
by Guozhonghua 06 Sep '21

06 Sep '21

Hello, When we test snapshot features and review the code of libvirt, there is one question, not an issue. /* do the memory snapshot if necessary */ if (memory) { /* check if migration is possible */ if (!qemuMigrationSrcIsAllowed(driver, vm, false, 0)) goto cleanup; While making one snapshot with memory on one vm, but it is not allowed while the vm which has some src devices, such as pci devs, with which the vm is not allowed to be migrated. I want to known the reason, why should it check this conditions? Thank You!

2 2

vm vcpu uses isolated cores
by Jiatong Shen 02 Sep '21

02 Sep '21

Hello, I am trying to understand why qemu vm CPU threads uses isolated cpus. I have a host which isolates some cpus using isolcpu like isolcpus=1,2,3,4,5,7,8,9,10,11. unfortunately, vcpupin does not mask out these cpus (vcpupin is still something like ffffffff). When I log in to the system, seems qemu cpu thread only runs on these isolcpus. I do not quite understand this behavior, because I think by using isolcpu, kernel schedule will exclude these cpus and thus vcpu thread shouldn't use these cores unless taskset explicitly got called.. So my question is how does cpu thread got scheduled on isolated cpus? Thank you. -- Best Regards, Jiatong Shen

3 2

We need excellent and well-written documentation for setting up open source NAS software
by Turritopsis Dohrnii Teo En Ming 31 Aug '21

31 Aug '21

Subject: We need excellent and well-written documentation for setting up open source NAS software Good day from Singapore, Our company, which is a Systems Integrator (SI) in Singapore, is evaluating more than 30 different open source Network Attached Storage (NAS) software. We need excellent and well-written documentation for your open source NAS software. Please provide us with links on how to setup your open source NAS software. We are looking forward to your replies. Thank you very much for your kind assistance. Mr. Turritopsis Dohrnii Teo En Ming, 43 years old as of 31 August 2021, is a TARGETED INDIVIDUAL living in Singapore. He is an IT Consultant with a System Integrator (SI)/computer firm in Singapore. He is an IT enthusiast. -----BEGIN EMAIL SIGNATURE----- The Gospel for all Targeted Individuals (TIs): [The New York Times] Microwave Weapons Are Prime Suspect in Ills of U.S. Embassy Workers Link: https://www.nytimes.com/2018/09/01/science/sonic-attack-cuba-microwave.html ******************************************************************************************** Singaporean Targeted Individual Mr. Turritopsis Dohrnii Teo En Ming's Academic Qualifications as at 14 Feb 2019 and refugee seeking attempts at the United Nations Refugee Agency Bangkok (21 Mar 2017), in Taiwan (5 Aug 2019) and Australia (25 Dec 2019 to 9 Jan 2020): [1] https://tdtemcerts.wordpress.com/ [2] https://tdtemcerts.blogspot.sg/ [3] https://www.scribd.com/user/270125049/Teo-En-Ming -----END EMAIL SIGNATURE-----

1 0

issues with vm after upgrade
by daggs 30 Aug '21

30 Aug '21

Greetings, a few weeks ago I've upgraded my system, this resulted with qemu and libvirt being upgraded to 6.0.0 and ~7.5.0 respectfully. I have two vms running on my system, router and streamer. the router vm works great, the streamer vm doesn't. after the streamer vm start, the monitor screen gets black and thats it. no relevant error are found in the log, see: http://dpaste.com/ERWDEJQPC the xml ca be found at https://dpaste.com/FQDN6NTN2 in contrast the following oneliner works: qemu-system-x86_64 \ -machine pc-q35-5.0,accel=kvm,usb=off,smm=on,dump-guest-core=off \ -cpu host,migratable=on \ -m 15360 \ -smp 4,sockets=1,dies=1,cores=2,threads=2 \ -drive file=/home/streamer/streamer.img.qcow2.new,if=virtio,format=qcow2 \ -device vfio-pci,host=0000:00:02.0,romfile=/home/streamer/gpu-8086:5912-uefi.rom,multifunction=on \ -device vfio-pci,host=0000:00:1f.3,multifunction=on \ -usb \ -device usb-host,vendorid=0x046d,productid=0xc52e \ -device usb-host,vendorid=0x2548,productid=0x1002 \ -display none \ -netdev tap,id=hostnet0,ifname=virtsw-streamer,script=no,downscript=no \ -device e1000e,netdev=hostnet0,id=net0,mac=52:54:00:5a:4c:8c \ -blockdev '{"driver":"file","filename":"/usr/share/edk2-ovmf/OVMF_CODE.secboot.fd","node-name":"libvirt-pflash0-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"driver":"file","filename":"/var/lib/libvirt/qemu/nvram/streamer-vm-q35_VARS.fd","node-name":"libvirt-pflash1-storage","auto-read-only":true,"discard":"unmap"}' another issue encountered caused by this param: "-audiodev id=audio1,driver=none" which is auto added to the qemu line. if I add the line to the above oneliner, the guest doesn't detects the pt sound card. without it it does and it works. help on solving both issues will be appreciated. Thanks, Dagg

5 30

Question The order of the output of virsh guestinfo --filesystem
by liuyd.fnst＠fujitsu.com 24 Aug '21

24 Aug '21

Hi all. I'm curious about the output order of virsh guestinfo --filesystem. Is the output random? E.g Guest info ``` [root@localhost ~]# lsblk -Jp -o KNAME,FSTYPE,TYPE,MOUNTPOINT,PKNAME,SERIAL { "blockdevices": [ {"kname": "/dev/sr0", "fstype": null, "type": "rom", "mountpoint": null, "pkname": null, "serial": "drive-scsi0-0-0-0"}, {"kname": "/dev/vda", "fstype": null, "type": "disk", "mountpoint": null, "pkname": null, "serial": null}, {"kname": "/dev/vda1", "fstype": "vfat", "type": "part", "mountpoint": "/boot/efi", "pkname": "/dev/vda", "serial": null}, {"kname": "/dev/vda2", "fstype": "xfs", "type": "part", "mountpoint": "/boot", "pkname": "/dev/vda", "serial": null}, {"kname": "/dev/vda3", "fstype": "LVM2_member", "type": "part", "mountpoint": null, "pkname": "/dev/vda", "serial": null}, {"kname": "/dev/vdb", "fstype": null, "type": "disk", "mountpoint": null, "pkname": null, "serial": null}, {"kname": "/dev/vdb1", "fstype": "xfs", "type": "part", "mountpoint": "/mnt/test1", "pkname": "/dev/vdb", "serial": null}, {"kname": "/dev/vdb2", "fstype": "xfs", "type": "part", "mountpoint": "/mnt/test2", "pkname": "/dev/vdb", "serial": null}, {"kname": "/dev/vdb3", "fstype": "xfs", "type": "part", "mountpoint": "/mnt/test3", "pkname": "/dev/vdb", "serial": null}, {"kname": "/dev/dm-0", "fstype": "xfs", "type": "lvm", "mountpoint": "/", "pkname": "/dev/vda3", "serial": null}, {"kname": "/dev/dm-1", "fstype": "swap", "type": "lvm", "mountpoint": "[SWAP]", "pkname": "/dev/vda3", "serial": null} ] } ``` virsh guestinfo output. It is not sorted by name or total-bytes/used-bytes ``` [root@hpe-apollo80-01-n00 ~]# virsh guestinfo fj-kvm-vm --filesystem fs.count : 6 fs.0.name : dm-0 fs.0.mountpoint : / fs.0.fstype : xfs fs.0.total-bytes : 7946108928 fs.0.used-bytes : 3202314240 fs.0.disk.count : 1 fs.0.disk.0.alias : vda fs.0.disk.0.device : /dev/vda3 fs.1.name : vda2 fs.1.mountpoint : /boot fs.1.fstype : xfs fs.1.total-bytes : 1063256064 fs.1.used-bytes : 180252672 fs.1.disk.count : 1 fs.1.disk.0.alias : vda fs.1.disk.0.device : /dev/vda2 fs.2.name : vda1 fs.2.mountpoint : /boot/efi fs.2.fstype : vfat fs.2.total-bytes : 627900416 fs.2.used-bytes : 7065600 fs.2.disk.count : 1 fs.2.disk.0.alias : vda fs.2.disk.0.device : /dev/vda1 fs.3.name : vdb2 fs.3.mountpoint : /mnt/test2 fs.3.fstype : xfs fs.3.total-bytes : 204111872 fs.3.used-bytes : 12185600 fs.3.disk.count : 1 fs.3.disk.0.alias : vdb fs.3.disk.0.device : /dev/vdb2 fs.4.name : vdb3 fs.4.mountpoint : /mnt/test3 fs.4.fstype : xfs fs.4.total-bytes : 751706112 fs.4.used-bytes : 39084032 fs.4.disk.count : 1 fs.4.disk.0.alias : vdb fs.4.disk.0.device : /dev/vdb3 fs.5.name : vdb1 fs.5.mountpoint : /mnt/test1 fs.5.fstype : xfs fs.5.total-bytes : 99254272 fs.5.used-bytes : 6213632 fs.5.disk.count : 1 fs.5.disk.0.alias : vdb fs.5.disk.0.device : /dev/vdb1 ``` -- Best Regards. Yiding Liu

2 2

vmware ESXi in KVM
by Gunnar 11 Aug '21

11 Aug '21

I am trying to install esxi7 inside a KVM machine virt-install --name=esxi7 \ --vcpus=2 \ --memory=4096 \ --cdrom=/home/username/isos/VMware-VMvisor-Installer-7.0U2a-17867351.x86_64.iso \ --disk size=33 \ --os-variant=unknown the installation process starts but does not get fails with a "No network adapters" error. This does not happen with other VM's. What do I have to add to above command in order to attach the default network adapter to the machine? or is there any other trick I have to be aware of when it comes to installing ESXi thx ... Gunnar

3 2

RX throttling causes keep-alive timeout
by Ivan Teterevkov 05 Aug '21

05 Aug '21

Hello folks, I recently discovered that the max_client_requests configuration option affects the keep-alive RPC and can cause the connection timeout, and I wanted to verify if my understanding is correct. Let me outline the context. Under certain circumstances, one of the connected clients in my setup issued multiple concurrent long-standing live-migration requests and reached the default limit of five concurrent requests. Consequently, it triggered the RX throttling, so the server stopped reading the incoming data from this client's file descriptor. Meanwhile, the server issued the keepalive "ping" requests but ignored the "pong" responses from the client due to the RX throttling. As a result, the server concluded the client was dead and closed the connection with the "connection closed due to keepalive timeout" message after the default five "ping" attempts with five seconds timeout each. The idea of throttling makes perfect sense: the server prevents hogging of the worker thread pool (or would prevent the unbounded growth of the memory footprint if the libvirtd server continued parsing the incoming data and queued the requests). What concerns me is that the server drops the connection for the alive clients when they're throttled. One approach to this problem is implementing the EAGAIN-like handling: parse the incoming data above the limit and respond with the error response, but handle the keep-alive RPCs gracefully. However, I see two problems here: either it's a backwards-compatibility concern if implemented unconditionally or polluting the configuration space if implemented conditionally. What is the community's opinion on the above issue? Kind regards, Ivan

2 2

ERROR Couldn't find hvm kernel for Ubuntu tree.
by Kaushal Shriyan 05 Aug '21

05 Aug '21

Hi, I am running the below command to spawn Ubuntu 18.04 based Virtual Machine using KVM based technology. #virt-install --version 1.5.0 # virt-install --name=snipeitassetmanagement > --file=/linuxkvmguestosdisk/snipeitassetmanagement.img --file-size=40 > --nonsparse --vcpus=2 --ram=8096 --network=bridge:br0 --os-type=linux > --os-variant=ubuntu18.04 --graphics none > --location=/linuxkvmguestosdisk/var/lib/libvirt/isos/ubuntu-18.04.5-live-server-amd64.iso > --extra-args="console=ttyS0" > > Starting install... > Retrieving file .treeinfo... > > | 0 B 00:00:00 > Retrieving file content... > > | 0 B 00:00:00 > Retrieving file info... > > | 70 B 00:00:00 > ERROR Couldn't find hvm kernel for Ubuntu tree. > Domain installation does not appear to have been successful. > If it was, you can restart your domain by running: > virsh --connect qemu:///system start snipeitassetmanagement > otherwise, please restart your installation. > > Any clue and i look forward to hearing from you. Thanks in advance. Best Regards,

2 3

Usage of virsh commands on guest lxc container are failing
by Yuva Raj 05 Aug '21

05 Aug '21

Hi Team, I am new to the Qemu/KVM, libvirt and these technologies. Hypervisor is running on linux kernel with libvirtd version 1.3.2. I am trying to spawn LXC ubuntu(21.04) container using virsh -c lxc:// commands on the hypervisor and ubuntu container is running now. On the ubuntu 21.04 container, I have installed debian "libvirt-clients" package to use the virsh utility. Updated the /etc/libvirt/libvirt.conf with to the hypervisor Qemu URI. When I run virsh commands without URI, observing below error root@host:~# virsh list error: failed to connect to the hypervisor error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory root@host:~# virsh -c <Qemu URI> list Id Name State ------------------------- 2 VM running If I execute the virsh commands without "-c" option, then ubuntu 21.04 container would display the VM's running as same as hypervisor. Could you please help to manage this on the LXC ubuntu container? LIBVIRT xml used to spawn LXC ubuntu 21.04 container: <domain type='lxc'> <name>host</name> <uuid>096f46bf-80bb-4441-a512-043a9c7a64d4</uuid> <memory unit='KiB'>1048576</memory> <currentMemory unit='KiB'>1048576</currentMemory> <vcpu placement='static' cpuset='7'>1</vcpu> <os> <type arch='x86_64'>exe</type> <init>/sbin/init</init> </os> <features> <capabilities policy='allow'> <audit_control state='on'/> <audit_write state='on'/> <block_suspend state='on'/> <chown state='on'/> <ipc_lock state='on'/> <ipc_owner state='on'/> <kill state='on'/> <mac_admin state='on'/> <mac_override state='on'/> <mknod state='on'/> <net_admin state='on'/> <net_bind_service state='on'/> <net_broadcast state='on'/> <net_raw state='on'/> <sys_admin state='on'/> <sys_boot state='on'/> <sys_ptrace state='on'/> <sys_rawio state='on'/> <sys_resource state='on'/> <sys_time state='on'/> <syslog state='on'/> </capabilities> </features> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>destroy</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/lib64/libvirt/libvirt_lxc</emulator> <filesystem type='mount' accessmode='passthrough'> <source dir='/junos/lxc/jdm/jdm1/rootfs'/> <target dir='/'/> </filesystem> </devices> </domain> Thanks, Yuvaraj.

2 1

attach a pcie root port as hostdev
by Jiatong Shen 04 Aug '21

04 Aug '21

Hello community, I am working on plugging a xilinx fpga card as a hostdev. This fpga card has 2 functions, each has a different role, for some reason, I would like to attach both of them but do not want to attach them separately, so I have tried to attach a pci bridge where fpga cards connect to. but got the following error, error: Failed to attach device from bridge.xml error: internal error: Non-endpoint PCI devices cannot be assigned to guests so, my question is is it possible to attach a pci-bridge as hostdev? thank you. -- Best Regards, Jiatong Shen

2 2

Sharing dhcp leases between multiple host systems
by Michael Ablassmeier 04 Aug '21

04 Aug '21

hi, assume i have multiple host systems which spin up virtual machines using the vagrant/vagrant-libvirt provider. Both host systems have a defined network (which has the same name on both hosts) which the first network interface of the virtual machine is assigned to. During boot of the virtual machine, the first network device is configured via DHCP and vagrant uses the mac address table or libvirt dhcp leases table to find out about the IP address that was assigned to the virtual machine: From that point on, i can reach the virtual machine locally on the host system. This works nicely if the network is a libvirt NAT network, as the IP addresses are unique on both host systems. Now i want to change the situation and provide routed addresses, thus i want to make sure that an IP that is assigned for a virtual machine on host A is not re-used on host B to not have IP address conflicts. What im searching for is the "libvirt" way to have a central lease file between multiple hosts for the same network (without having another layer like OVS/OVN). What i guess would work is: 1) share /var/lib/libvirt/dnsmasq between both host systems, of course means the virtual bridge for the network has to have the same name on both systems. 2) replace /usr/libexec/libvirt_leaseshelper with my own version, that stores the leases in an central place. 3) a way that exists and i dont know about? Option 2) sounds the best for me, but i currently dont see a way to specify the dhcp-script used for a network on libvirt side .. any opinions on this? Using libvirt 7.x and alike from the centos 8 advanced virtualization stream. thanks, - michael

2 1

Disk extend during migration
by Vojtech Juranek 02 Aug '21

02 Aug '21

Hi, as a follow-up of BZ #1883399 [1], we are reviewing vdsm VM migration flows and solve few follow-up bugs, e.g. BZ #1981079 [2]. I have couple of questions related to libvirt: * if we run disk extend during migration, it can happen that migration finishes sooner than disk extend. In such case we will try to set disk threshold on already stopped VM (we handle libvirt event that VM was stopper, but due to Python GIL there can be a delay between obtaining appropriate signal from libvirt and handling it). In such case we get libvirt VIR_ERR_OPERATION_INVALID when setting disk threshold. Is it safe to catch this exception and ignore it or it's thrown for various reasons and the root cause can be something else than stopped VM? * after disk extend, we resume VM if it's stopped (usually due to running out of the disk space). Is it safe to do so also when we do the disk extend during migration and VM can be stopped because it was already migrated? I.e. can we assume that libvirt will handle such situation and won't resume VM in such case? We do some checks before resume and try to avoid situation when we resume migrated VM, but there can be some corner cases and it would be useful to know if we can rely in libvirt to prevent resuming VM in unwanted cases like one when VM is stopper after migration. Thanks Vojta [1] https://bugzilla.redhat.com/1883399 [2] https://bugzilla.redhat.com/1981079

2 4

Passthrough PCI GPU device fails on reboot
by Francesc Guasch 28 Jul '21

28 Jul '21

Hello. I have a host with an NVIDIA RTX 3090. I configured PCI passthrough and it works fine. We are using it for CUA and Matlab on Ubuntu 20.04. The problem comes sometimes on rebooting the virtual machine. It doesn't happen 100% of the times but eventually after 3 or 4 reboots the PCI device stops working. The only solution is to reboot the host. Weird thing is this only happens when rebooting the VM. After a host reboot if we shutdown the virtual machine and we start it again, it works fine. I wrote a small script that does that a hundred times just to make sure. Only a reboot triggers the problem. When it fails I run "nvidia-smi" in the virtual machine and I get: No devices were found Also I spotted some errors in syslog NVRM: installed in this system is not supported by the NVIDIA 460.91.03 driver release. NVRM: GPU 0000:01:01.0: GPU has fallen off the bus NVRM: the NVIDIA kernel module is unloaded. NVRM: GPU 0000:01:01.0: RmInitAdapter failed! (0x23:0x65:1204) NVRM: GPU 0000:01:01.0: rm_init_adapter failed, device minor number 0 The device is there because typing lspci I can see information: 0000:01:01.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:2204] (rev a1) Subsystem: Gigabyte Technology Co., Ltd Device [1458:403b] Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia I tried different Nvidia drivers and Linux kernels in the host and the virtual machine with the same results. I wonder if some process is keeping hold of the PCI device but every thing I tried failed. I made sure the virtual machines are down. Then I start it again. I also tried restarting libvirtd. I was thinking about a hardware problem but we 3 different GPUs of the same model and it happens with all of them. I know this is hard but I wonder if anyone here has any idea of what can I do to fix this. thank you for your time

2 2

investigate locks on a domain
by Jiatong Shen 20 Jul '21

20 Jul '21

Hello community, I am seeing following log in production, 2021-07-20 07:43:49.417+0000: 3918294: error : qemuDomainObjBeginJobInternal:4945 : Timed out during operation: cannot acquire state change lock (held by qemuProcessReconnect) 2021-07-20 07:44:19.424+0000: 3918296: warning : qemuDomainObjBeginJobInternal:4933 : Cannot start job (modify, none) for domain instance-0000074e; current job is (modify, none) owned by (3919429 qemuProcessReconnect, 0 <null>) for (2183193s, 0s) 2021-07-20 07:44:19.424+0000: 3918296: error : qemuDomainObjBeginJobInternal:4945 : Timed out during operation: cannot acquire state change lock (held by qemuProcessReconnect) 2021-07-20 07:44:49.428+0000: 3918296: warning : qemuDomainObjBeginJobInternal:4933 : Cannot start job (query, none) for domain instance-0000074e; current job is (modify, none) owned by (3919429 qemuProcessReconnect, 0 <null>) for (2183223s, 0s) 2021-07-20 07:44:49.428+0000: 3918296: error : qemuDomainObjBeginJobInternal:4945 : Timed out during operation: cannot acquire state change lock (held by qemuProcessReconnect) 2021-07-20 07:45:19.429+0000: 3918298: warning : qemuDomainObjBeginJobInternal:4933 : I am confused about what is qemuProcessReconnect and why it acquires a domain state lock.. -- Best Regards, Jiatong Shen

3 2

Failed to terminate process 1901409 with SIGKILL: Device or resource busy
by 梁朝军 19 Jul '21

19 Jul '21

Hi All, I hit another issue that libvirt sometimes throw exception like 'Failed to terminate process 1901409 with SIGKILL: Device or resource busy’ once we try to destroy vm through 'conn.lookupByID(id_).destroy()’. After this issue occur, it will caused the socket fd and pipe increased and finally caused fd leak. Who know the root cause of this issue or give some cues? Any comments are appreciated Thanks !

1 0

Re: how to build a github release tarball
by Andrea Bolognani 15 Jul '21

15 Jul '21

[re-adding the list] On Thu, Jul 15, 2021 at 01:25:02PM +0800, Jiatong Shen wrote: > On Thu, Jul 15, 2021 at 5:54 AM Jiatong Shen <yshxxsjt715(a)gmail.com> wrote: > > thank you very much for reply. but what should I do if I want to > > build release tarball myself (for 6.0.0..)? I would like to backport some > > features > > to 6.0.0.. > > hmm. it looks like `make -j3 dist` could produce a tarball for 6.0.0.. Is > it the right > approach? Yes, if your goal is to create a release archive for libvirt 6.0.0 with some patches on top[1] then the best way to go about it is to clone the repo, branch off the v6.0.0 tag, cherry-pick the changes you're interested in and then generate the archive using 'make distcheck'. [1] You could have told us this in the first place instead of asking a more generic question for which a different answer was more appropriate ;) -- Andrea Bolognani / Red Hat / Virtualization

1 0

openVswitch won't get to a virtual IP
by lejeczek 14 Jul '21

14 Jul '21

Hi guys. Among all the mailing lists I'm subscriber of this one I thought, would where chances to find 'openvswitch'+'libvirtd' experts to share thoughts & suggestions should be grater. A case: a) all guests are KVM. b) I have NM managed OVS bridge and libvirtd network to/on that bridge c) "regular" NM bridge and network off it in libvirt problem is - guests on OVS network can _not_ ping a virtual IP of a guest(s) on 'regular' bridge network, but.. can ping "actual" IP of that same guest(s) okey. any thoughts and ideas on how & what to investigate are very appreciated. many thanks, L.

2 2

how to build a github release tarball
by Jiatong Shen 14 Jul '21

14 Jul '21

Hello community, I am trying to figure out a way to build a release tarball like https://github.com/libvirt/libvirt/releases?after=v6.2.0, for libvirt 6.0.0, but don't know how. Could anyone teach me how to package it? thank you. -- Best Regards, Jiatong Shen

3 2

DAC & glusterFS - errors
by lejeczek 14 Jul '21

14 Jul '21

Hi guys I'm trying to spin up a VM whose image is on a GlusterFS vol, and I fail: -> $ virsh create /var/lib/pacemaker/conf.d/win10Pro.xml error: Failed to create domain from /var/lib/pacemaker/conf.d/win10Pro.xml error: failed to initialize gluster connection (src=0x7f0af807b410 priv=0x7f0af8090070): Invalid argument In logs: ... 2021-07-05 21:13:12.950+0000: 141524: warning : virSecurityDACSetOwnership:828 : Unable to restore label on 'win10Pro.qcow2'. XATTRs might have been left in inconsistent state. internal error: child reported (status=125): failed to initialize gluster connection (src=0x7f0b00097030 priv=0x7f0b000956c0): Invalid argument Any ideas & suggestions greatly appreciated. thanks, L.

5 5

virsh qemu-monitor-command block_resize not working
by arjen-libvirt＠gugu.be 14 Jul '21

14 Jul '21

Hi List, some version info: ]# /usr/libexec/qemu-kvm -version QEMU emulator version 4.2.0 (qemu-kvm-4.2.0-48.module+el8.4.0+534+4680a14e) Copyright (c) 2003-2019 Fabrice Bellard and the QEMU Project developers ]# virsh version Compiled against library: libvirt 6.0.0 Using library: libvirt 6.0.0 Using API: QEMU 6.0.0 Running hypervisor: QEMU 4.2.0 information about block devices for one specific guest: ]# virsh qemu-monitor-command uat-win201202.uat.gugu.be --hmp info block libvirt-2-format: /data/kvm/storage/diskimages01/uat-win201202_disk1_C.qcow2 (qcow2) Attached to: /machine/peripheral/virtio-disk0/virtio-backend Cache mode: writeback ide0-0-0: [not inserted] Attached to: ide0-0-0 Removable device: not locked, tray closed But then, when I want to resize the block device, I just cannot seem to find the correct device. I tried all of these: virsh qemu-monitor-command uat-win201202.uat.gugu.be --hmp block_resize libvirt-2-storage 48G Error: Cannot find device=libvirt-2-storage nor node_name= virsh qemu-monitor-command uat-win201202.uat.gugu.be --hmp block_resize drive-libvirt-2-storage 48G Error: Cannot find device=drive-libvirt-2-storage nor node_name= virsh qemu-monitor-command uat-win201202.uat.gugu.be --hmp block_resize virtio-disk0 48G Error: Cannot find device=virtio-disk0 nor node_name= virsh qemu-monitor-command uat-win201202.uat.gugu.be --hmp block_resize drive-virtio-disk0 48G Error: Cannot find device=drive-virtio-disk0 nor node_name= In a previous qemu version this worked (EL 7). Can someone help me out? Best regards, Arjen Van Drie, Antwerp

2 2

host identifier
by Jiatong Shen 05 Jul '21

05 Jul '21

Hello community, I am using OpenStack nova and realize that nova now uses host fqdn from libvirt as a uniq identifier for a compute node. The issue is that host might need to change its fqdn under some rare circumstances and lose some usage data due to the nova manages compute node resources. My question is: does libvirt already export host uuid identifier to other applications? I skim through the code base and find there is host uuid related code which reads /etc/machine-id to obtain a uniq uuid for migration, but seems this uuid cannot be obtained through virsh interface. Thank you for you help. -- Best Regards, Jiatong Shen

2 2

Fail to do blockcopy to network dest xml with --reuse-external
by Han Han 28 Jun '21

28 Jun '21

Hello, libvirt developers, Recently I find an issue of libvirt blockcopy: Versions: libvirt-7.4.0 qemu-kvm-6.0.0 Steps: 1. Create a nbd server # qemu-img create -f qcow2 /var/lib/libvirt/images/fedora-1.qcow2 10G -o preallocation=full # qemu-nbd -e 10 /var/lib/libvirt/images/fedora-1.qcow2 -p 10001 2. Prepare a running VM # virsh list Id Name State ------------------------ 3 fedora running # virsh dumpxml 3|xmllint --xpath //disk - <disk type="file" device="disk"> <driver name="qemu" type="qcow2"/> <source file="/var/lib/libvirt/images/fedora.qcow2" index="1"/> <backingStore/> <target dev="hda" bus="ide"/> <alias name="ide0-0-0"/> <address type="drive" controller="0" bus="0" target="0" unit="0"/> </disk> 3. Blockcopy to a nbd dest xml with --reuse-external # cat /tmp/copy.xml <disk type='network' device='disk'> <driver name='qemu' type='qcow2'/> <source protocol="nbd"> <host name="localhost" port="10001" /> </source> <backingStore/> <target dev='hda' bus='ide'/> </disk> # virsh blockcopy fedora hda --xml /tmp/copy.xml --transient-job --wait --verbose --finish --reuse-external error: unsupported configuration: reused mirror destination format must be specified But it works without --reuse-external # virsh blockcopy fedora hda --xml /tmp/copy.xml --transient-job --wait --verbose --finish Block Copy: [100 %] Successfully copied Since it is clear that the format of dest image is qcow2, the error message "reused mirror destination format must be specified" is wrong. The blockcopy with network disk + --reuse-external should either be supported or post a better error message. I am not sure if --reuse-external flag is only for file type disk. It seems the description of VIR_DOMAIN_BLOCK_COPY_REUSE_EXT( https://github.com/libvirt/libvirt/blob/7c08141f906e20e730c4b6407bc638e743d…) indicates this flag is for file only: * VIR_DOMAIN_BLOCK_COPY_REUSE_EXT flag is present stating that the file * was pre-created with the correct format and metadata and sufficient * size to hold the copy. In case the VIR_DOMAIN_BLOCK_COPY_SHALLOW flag * is used the pre-created file has to exhibit the same guest visible contents * as the backing file of the original image. This allows a management app to * pre-create files with relative backing file names, rather than the default * of absolute backing file names. Please help to confirm if it is a bug here.

1 0