- Users - libvirt List Archives

Question about encryption and tls
by Kamil Jońca 29 Sep '23

29 Sep '23

(Posted few days ago on qemu group but no reactions) Do I understand correctly that ssl shoudl be configured independently for libvirt and each hypervisor? I asked because I configured libvirt connection as qemu+tls://bambus.kjonca/system?pkipath=... (and on bambus in /etc/libvirt/libvirtd.conf) I set key_file = ... cert_file = ... ca_file = ... But after connect and lauching (on bambus) vm I tried to snif traffic to bambus:5900 on client) and wireshark was able to detect "VNC" protocol (BTW not spice?), so I am confused. should I configure in /etc/libvirt/qemu.conf spice_tls option and certificates ? KJ

3 4

Re: Help ! libvirt
by Bhasker C V 22 Sep '23

22 Sep '23

Adding libvirt mailing list apologies for cross-posting libvirt version: 9.7.0-1 On Thu, Sep 21, 2023 at 8:39 AM john doe <johndoe65534(a)mail.com> wrote: > On 9/21/23 09:32, Bhasker C V wrote: > > I am getting an error with libivrt when I create a VM > > > > ``` > > $ sudo virsh create ./win11.xml > > error: Failed to create domain from ./win11.xml > > error: internal error: mishandled storage format 'none' > > > > ``` > > > > This is after I have done a dist-upgrade (was working fine before) > > debian trixie. > > > > error message says > > qemuBlockStorageSourceGetBlockdevFormatProps:1227 : internal error: > > mishandled storage format 'none' > > > > You might want to post this as well to the Libvirt mailing list. > > -- > John Doe > >

6 10

virtio-mem with virt-install to share memory between guest and host on-demand
by Daniel Krajnik 21 Sep '23

21 Sep '23

Hi I'm trying to Passthrough a GPU to a VM and have it still share its free memory with the host (just like it would with virtio-balloon). Is this something virtio-mem is capable of? I've tried to run it, but it immediately took over 9GB of memory: virt-install --name test --cpu cell0.cpus=0,cell0.memory=4194304,cell1.cpus=1,cell1.memory=4194304 --memory maxMemory=65536,maxMemory.slots=8 --memdev model=virtio-mem,target.node=0,target.block=2048,target.size=1000 --disk size=400 --network network=ai --location=/tmp/debian-12.1.0-amd64-netinst.iso --os-variant=debian11 --graphics none --extra-args "console=ttyS0 Best wishes, Daniel

2 2

CAN virtualization
by Sánta, Márton (ext) 18 Sep '23

18 Sep '23

Dear Users, I use KVM with libvirt 9.0.0. The host and guest OS-es are also AGL needlefish images. I am currently trying to virtualize a CAN driver and provide virtual machines access to the physical CAN channels. I started with the virtual network handling as CAN interface is a network interface, I tried to find analogies, solutions like "traditional" network handling but it did not work. I also tried out to define a nodedev device via .xml config file. The interesting thing is, that when I list all the available nodedev devices with 'virsh nodedev-list', I can see 'net_can0' and 'net_can1' on the output as 'net' type device but I cannot attach these devices to the guests, and I do not know how to define it in the guest .xml file. I tried out many different things, but when I try to add it as a 'hostdev' device with different mode and type settings, I always get an error (e.g. not a PCI device or not supported device type etc.). It would be long to write down all the configurations I tried out, so my first question would be that does anybody know how could I provide access to guests to the physical CAN interfaces? The aim is to be able to send CAN messages from guest OS-es. If no direct access is possible, it would be also OK to have access to virtual CAN interfaces on the host and then transfer messages to the physical CAN channel. Thank you in advance for an early reply! Best regard, Márton Sánta This transmission is intended solely for the addressee and contains confidential information. If you are not the intended recipient, please immediately inform the sender and delete the message and any attachments from your system. Furthermore, please do not copy the message or disclose the contents to anyone unless agreed otherwise. To the extent permitted by law we shall in no way be liable for any damages, whatever their nature, arising out of transmission failures, viruses, external influence, delays and the like.

2 3

how to build libvirt-go-module statically
by Jiatong Shen 06 Sep '23

06 Sep '23

Hello community, I want to know how to build libvirt-go-module statically? My go version is 1.17 and libvirt-go-module version is v1.9007.0. Thank you very much for the help. -- Best Regards, Jiatong Shen

2 2

SEV, SEV-ES, SEV-SNP
by Derek Lee 29 Aug '23

29 Aug '23

When SEV is enabled in domcapabilities does that just mean any of SEV, SEV-ES, SEV-SNP is possible on the hardware? Similarly, does enabling SEV as a launchSecurity option in a domainXML mean that whichever SEV is available will be enabled? And if the guest policy has the ES flag set, it will not be created unless ES is enabled? Sorry if these questions don't make sense or are ill-formed. Best, Derek

3 2

Performance Discrepancies and Limitations in Local Storage IOPS Testing
by Jan Wasilewski 24 Aug '23

24 Aug '23

Hi, In the past few weeks, I conducted performance tests to evaluate IOPS (Input/Output Operations Per Second) performance for locally attached disks. The original discussion started on the openstack-discuss mailing list since all the tests were conducted within an OpenStack cloud environment. However, I decided to initiate a discussion here, as it appears that the performance differences might be rooted in lower-level factors rather than the OpenStack platform itself. It seems that these differences are closely related to variations in libvirt/qemu versions and kernel configurations. Ultimately, I discovered that the performance is significantly enhanced when the hypervisor is deployed on top of Ubuntu 22.04LTS. Under this setup, I was able to achieve around 100,000 IOPS during my fio tests [1][2]. In contrast, conducting a similar test with the hypervisor deployed on Ubuntu 20.04LTS yielded significantly lower results, averaging around 20,000 IOPS [3][4]. An intriguing observation is that attaching an nvme disk to my Ubuntu 22.04LTS system and utilizing it as local storage led to slightly diminished performance, hovering around 90,000 IOPS [5]. This outcome is somewhat unexpected, as I initially anticipated higher figures. It's particularly noteworthy that when I conduct the same test directly on top of the hypervisor, the numbers align more closely with expectations [6][7]. This pattern suggests that there might be a limitation imposed either by libvirt/qemu or the kernel itself. Having meticulously reviewed all the release notes, I failed to come across any information pertaining to noteworthy performance enhancements concerning local storage and IOPS. Given this, I'd like to reach out to you directly to inquire if you possess any insights into such limitations. Any guidance or suggestions that could help optimize my local storage results would be greatly appreciated. Looking forward to your input. Best regards /Jan Wasilewski *References:[1] Configuration details(libvirt/qemu/kernel version) for Ubuntu 22.04: https://paste.openstack.org/show/b8svl0bOfX0WHTGvgI1h/ <https://paste.openstack.org/show/b8svl0bOfX0WHTGvgI1h/>[2] fio results for VM test with Ubuntu 22.04: https://paste.openstack.org/show/bUpiq1y0o58S1ThNgqLd/ <https://paste.openstack.org/show/bUpiq1y0o58S1ThNgqLd/>[3] Configuration details(libvirt/qemu/kernel version) for Ubuntu 20.04: https://paste.openstack.org/show/b005K2L6ZutGxDrCOZbL/ <https://paste.openstack.org/show/b005K2L6ZutGxDrCOZbL/>[4] fio results for VM test with Ubuntu 20.04: https://paste.openstack.org/show/b8JeVOn4YCPSX7uaqR0N/ <https://paste.openstack.org/show/b8JeVOn4YCPSX7uaqR0N/>[5] fio results for VM test with Ubuntu 22.04 and nvme as a local storage disk: https://paste.openstack.org/show/b75M4bI00LQePTmYSaUI/ <https://paste.openstack.org/show/b75M4bI00LQePTmYSaUI/>[6] fio results for hypervisor test with Ubuntu 22.04 and nvme storage: https://paste.openstack.org/show/bj7NeSiwwiWS6MbJROts/ <https://paste.openstack.org/show/bj7NeSiwwiWS6MbJROts/>[7] fio results for hypervisor test with Ubuntu 22.04 and ssd storage: https://paste.openstack.org/show/bSeEHXcbrY9YlYWQWGKS/ <https://paste.openstack.org/show/bSeEHXcbrY9YlYWQWGKS/>*

1 0

Warning : Failed to set up UEFI / The Libvirt version does not support UEFI / Install options are limited...
by Mario Marietto 21 Aug '23

21 Aug '23

Hello to everyone. I'm trying to use qemu 5.1 with virt-manager and libvirt on my ARM chromebook (armhf 32 bit cpu) running with Devuan 4 as host o.s. By default it uses qemu and its dependencies,version 5.2. I remember that I can't use qemu 5.2,because it doesn't have any support for KVM as you can read here : https://lists.gnu.org/archive/html/qemu-devel/2020-09/msg02074.html For this reason,I've compiled qemu 5.1 from source. Below I shown how I have configured everything such as a little piece of compilation messages : # apt install libgtk-3-dev libpulse-dev libgbm-dev libspice-protocol-dev libspice-server-dev libusb-1.0-0-dev libepoxy-dev # cd /usr/share # mv qemu qemu_ # cd /usr/lib # mv qemu qemu_ # cd /usr/lib/arm-linux-gnueabihf # mv qemu qemu_ # cd /usr/lib/ipxe # mv qemu qemu_ # cd /usr/share/bash-completion/completions/ # mv qemu qemu_ # mv qemu-kvm qemu-kvm_ # mv qemu-system-i386 qemu-system-i386_ # mv qemu-system-x86_64 qemu-system-x86_64_ # cd /usr/bin # mv qemu-system-arm qemu-system-arm_ # cp /root/Desktop/qemu-v5.1.0/arm-softmmu/qemu-system-arm /usr/bin # CFLAGS=-Wno-error ./configure --target-list=x86_64-softmmu --enable-opengl --enable-gtk --enable-kvm --enable-guest-agent --enable-spice --audio-drv- list="oss pa" --enable-libusb A little piece of the log messages that I've got from the compilation of qemu 5.1 : https://pastebin.ubuntu.com/p/8DYfgPvhXy/ These are the resulting versions of my frankenstein operation : # virsh version Compiled against library: libvirt 7.0.0 Using library: libvirt 7.0.0 Using API: QEMU 7.0.0 Running hypervisor: QEMU 5.1.0 At this point I've run virt-manager. It has been able to detect qemu,but I get the following error : Warning : Failed to set up UEFI. The Libvirt version does not support UEFI. Install options are limited. Do you have some suggestions to give me to fix this error ? I'm sure to have missed something, thanks. -- Mario.

1 0

Does libvirt support intra-host KVM migration?
by Eric Wheeler 17 Aug '23

17 Aug '23

Hello all, I'm reposting this to the libvirt-users list: I looked around for documentation on intra-host KVM migration but haven't found much. For example, this could be useful to "migrate" VM to run on an upgraded version of `qemu-kvm` without migrating to a different host and migrating back. We tested migrating a VM to the same host on an old version of libvirt (el7), and it complained about UUID conflicts if the destination already hosts the same VM. Changing the name or the UUID in the destination XML during migration (`virsh migrate --xml`) gives an error that the UUID or name does not match during migration: UUID change: error: unsupported configuration: Target domain uuid 66a113f4-a101-4db1-8478-49cf088fedb9 does not matchsource b5256b25-e137-45b8-bddb-78545ab55fc4 Name change: error: unsupported configuration: Target domain name 'diskless2' does not match source 'diskless' Questions before we do more testing: - Do modern versions of libvirt support intra-host migration? - If so, which version? - Documentation? Any help you can provide would be greatly appreciated! -- Eric Wheeler

2 1

You will need to grant the 'libvirt-qemu' user search permissions for the following directories....
by Sebastien WILLEMIJNS 09 Aug '23

09 Aug '23

Hello, Why LIBVIRT software/libs need to chown "near the root level" (home/blahblah/) when raw/vdi/vhd can contains lots of directories as /home/user/Virtual_HDs/desktop/daddy/private/bedroom/number2/hd.vdi ? on ubuntu, "/media/hostname" can contains all our external HD's without relation with virtualization !!! :-( another sample picked up in the net: WARNING /home/jwright/virtualMachines/images/fedora25.qcow2 may not be accessible by the hypervisor. You will need to grant the 'qemu' user search permissions for the following directories: ['/home/jwright']

2 2