- Users - libvirt List Archives

Migrate to a bigger disk possible?
by Paul van der Vlis 11 Jun '20

11 Jun '20

Hello, I have a qcow2 disk what needs to become increased. I don't have space on the location where it is now to have it two time, so I want to live-migrate it to another host. On the other host I have to create a qcow2 disk before I can migrate. What would happen when I would create there a bigger qcow2 disk then the original one? Can I resize the filesystem after the migration? With regards, Paul van der Vlis -- Paul van der Vlis Linux systeembeheer Groningen https://www.vandervlis.nl/

3 9

Fwd: Hello
by K. Kahurani 11 Jun '20

11 Jun '20

---------- Forwarded message --------- From: K. Kahurani <k.kahurani(a)gmail.com> Date: Sun, May 31, 2020 at 2:26 PM Subject: Hello To: <eblake(a)redhat.com> Hello, Hopefully this finds you well. This is not a bug report but more or less an inquiry as based on the information acquired from Jim Fehlig a while back, it is possible you would have some important information regarding this. It is currently not possible for me to compile libvirt right from the word go while configuring with the error [1]. From the look of it and a bit of searching on the internet, it does look like the package portablexdr is obsolete. Could it be that this is a known issue? Could it be there already is a workaround this? Do you suppose this should go into the mailing list? Sincerely, David. [1] checking for WIRESHARK_DISSECTOR... no checking for xdrmem_create in -lportablexdr... no checking for library containing xdrmem_create... no configure: error: Cannot find a XDR library

2 2

Disable virtlockd
by Felix Queißner 09 Jun '20

09 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 09 Jun '20

09 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

About Libvirt Setmem&dommemstat Function
by 🍭 20 May '20

20 May '20

I have sent a similar email about this problem. But I did not describe carefully, so I would like to explain it in more details. I am using 'virsh setmem' to ajust vm memory online. However, I don't know what is the lowerlimit that can be set to. And I try to use 'virsh dommemstat' to get 'unused' memory so that I can calculate the lowerlimit memory with this value, but it doesn't work when it comes to windows systems as I cannot set vm memory down to 'available - unused' in windows system. I suppose it's caches memory that causes this problem, so I upgrade my libvirt & qemu in order to get 'stat_disk_caches'. Although I upgrade libvirt to v4.10.0, qemu upgrade to v4.1.0, I cannot get this value. In summary, I came across two problems. How can I know the exact lowerlimit memory that can be set to in one vm? And if I need 'stat_disk_caches' value, how can I get it properly? My libvirt version: v4.10.0, qemu version:v4.1.0, hypervisor working on centos7.6 system.

1 0

macvtap direct
by Subhendu Ghosh 19 May '20

19 May '20

Hi Couple of questions around macvtap direct usage: 1) is the document here current? https://libvirt.org/formatnetwork.html#examplesDirect I have been able to get host to guest network traffic without any special configuration or switch since Fedora 28 when I first started using it. Using <forward mode=vepa> requires switch port mirroring, but just using <forward mode=bridge> doesn't. 2) do any of the language libraries make assumptions that libvirt networks must have a <bridge name=xx> attribute? Foreman's Ruby interface to libvirt errors out with attempting to build a VM on a KVM host with a network defined with <forward mode=bridge> https://projects.theforeman.org/issues/25890 thanks Subhendu

2 3

About Libvirt Setmem&dommemstat Function
by 🍭 19 May '20

19 May '20

I am using 'virsh setmem' to adjust the vm memory. But I don't know what is the lowerlimit memory that can be adjusted to, so I try to update the version of libvirt&qemu to get caches of the vm memory so that I can calculate the lowerlimit. And when I upgrade libvirt to 4.10.0, qemu upgrade to 4.1.0, still, I cannot get 'stat-disk-caches'.  How can I solve it ? Thx.

1 0

Firmware auto-select limitation
by GUOQING LI 15 May '20

15 May '20

Hi everyone and Martin I would like to confirm the conversation we had in regard the possible limitation of firmware auto-select feature that’s been released since v5.20. I recall you saying that there were a lot of issues with auto select and later they shipped it into a Json file , it still didn’t solve all the problems, did it? Is it better to explicitly specify the loader and nvram path than using auto-select ? Just today, I encountered the issue of using firmware=“efi” on libvirt 5.4.0 I am running Ubuntu eoan 19.10, I am wondering how did it happen. Detailed error Error starting domain: internal error: process exited while connecting to monitor: 2020-05-15T14:19:06.033267Z qemu-system-x86_64: -drive file=/usr/share/OVMF/OVMF_CODE.fd,if=pflash,format=raw,unit=0,readonly=on: Failed to lock byte 100 Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 111, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 66, in newfn ret = fn(self, *args, **kwargs) File "/usr/share/virt-manager/virtManager/object/domain.py", line 1279, in startup self._backend.create() File "/usr/lib/python3/dist-packages/libvirt.py", line 1080, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirt.libvirtError: internal error: process exited while connecting to monitor: 2020-05-15T14:19:06.033267Z qemu-system-x86_64: -drive file=/usr/share/OVMF/OVMF_CODE.fd,if=pflash,format=raw,unit=0,readonly=on: Failed to lock byte 100

3 2