- Users - libvirt List Archives

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