June 2020 - Users - libvirt List Archives

Disable virtlockd
by Felix Queißner 10 Jun '20

10 Jun '20

Hello! Is it possible to disable the virtlockd daemon or VM file locking? I start qemu with a -snapshot option which prevents and changes to the disk image anyways. Using <readonly /> is not supported for IDE disks. Another option would be to not require locking on the NFS share, but i have no idea how. Can someone help me with that? Regards Felix Queißner

2 2

No outbound connectivity from guest VM(fedora 32)
by Justin Stephenson 10 Jun '20

10 Jun '20

Hi, I recently installed a fresh install of Fedora 32 and I am having trouble with my virtual machine networking, I can ssh and connect into my guest VMs from my host, but the guest VMs cannot ping out to the internet. I am using the "default" NAT virtual network, the interesting thing is I have made no configuration changes on my host or in the guest VMs, simply created and installed two VMs(Fedora and RHEL8) in Fedora where the VMs are having the same issue. I am happy to provide any logs or command output if that would help. -Justin

3 3

Permission to disk set wrong when restoring from memory snapshot?
by Liran Rotenberg 09 Jun '20

09 Jun '20

Hi all, Passing on Bug 1840609 <https://bugzilla.redhat.com/show_bug.cgi?id=1840609> - Wake up from hibernation failed:internal error: unable to execute QEMU command 'cont': Failed to get "write" lock. In Ovirt/RHV there is a specific flow that prevents the VM from starting on the first host. The result is: 2020-06-09T12:12:58.111610Z qemu-kvm: Failed to get "write" lock Is another process using the image [/rhev/data-center/3b67fb92-906b-11ea-bb36-482ae35a5f83/4fd23357-6047-46c9-aa81-ba6a12a9e8bd/images/0191384a-3e0a-472f-a889-d95622cb6916/7f553f44-db08-480e-8c86-cbdeccedfafe]? 2020-06-09T12:12:58.668140Z qemu-kvm: terminating on signal 15 from pid 177876 (<unknown process>) We have a rerun mechanism. Therefore the VM starts again on another host if available. On the second try the VM does succeed to run. After looking in the debug logs (attached in the bug), I have seen this on the first host: 2020-06-09 12:12:46.288+0000: 177879: debug : qemuSetupImageCgroupInternal:139 : Not updating cgroups for disk path '<null>', type: file 2020-06-09 12:12:46.288+0000: 177879: debug : qemuSetupImagePathCgroup:75 : Allow path /rhev/data-center/3b67fb92-906b-11ea-bb36-482ae35a5f83/4fd23357-6047-46c9-aa81-ba6a12a9e8bd/images/0191 384a-3e0a-472f-a889-d95622cb6916/7f553f44-db08-480e-8c86-cbdeccedfafe, perms: rw *2020-06-09 12:12:46.288+0000: 177879: debug : qemuSetupImagePathCgroup:75 : Allow path /rhev/data-center/mnt/yellow-vdsb.qa.lab.tlv.redhat.com:_Compute__NFS_GE_compute-ge-4_nfs__0/4fd23357-6047-46c9-aa81-ba6a12a9e8bd/images/0191384a-3e0a-472f-a889-d95622cb6916/7f553f44-db08-480e-8c86-cbdeccedfafe, perms: r* And immediately after retry on the second host: 2020-06-09 12:13:01.839+0000: 15781: debug : qemuSetupImagePathCgroup:75 : Allow path /rhev/data-center/mnt/yellow-vdsb.qa.lab.tlv.redhat.com:_Compute__NFS_GE_compute-ge-4_nfs__0/4fd23357-60 47-46c9-aa81-ba6a12a9e8bd/images/0191384a-3e0a-472f-a889-d95622cb6916/7f553f44-db08-480e-8c86-cbdeccedfafe, perms: rw Is it intended and might cause the QEMU error? Regards, Liran.

2 4

libvirt-defined network vs/and openvswitch bridge
by Po Dragonwarrior 01 Jun '20

01 Jun '20

Hi all, Can you please explain to me what is the difference (or maybe the relation?) between a libvirt defined network and an openvswitch bridge? best, Po

2 1