- Users - libvirt List Archives

ANNOUNCE: Forthcoming changes to libvirt mailing list hosting
by Daniel P. Berrangé 13 Oct '23

13 Oct '23

Hello Libvirt Community, For the last 18(!) years, libvirt community mailing lists have been kindly hosted by Red Hat Corporate IT on the redhat.com Mailman installation. In retrospect this wasn't the ideal home for community mailing lists but that decision is ancient history. Unfortunately as a consequence of infrastructure changes, the redhat.com Mailman service is scheduled to be decomissioned, and in the very near future ($low weeks) will cease to be able to send/receive mail for libvirt lists. As a result, all the libvirt mailing lists will need to move to a new Mailman installation, managed on our behalf by the Red Hat Open Source Community Infrastructure team[1], who provide services for a variety of OSS projects. It is intended that this new service will be dedicated for our community and thus located somewhere under the libvirt.org domain. It should go without saying that all existing mail archives will be migrated over to the new server. None of the historical record should be lost. It is not considered appropriate netiquette, however, to bulk-resubscribe all current list members under a new domain. Thus anyone who wants to remain on the community lists will soon be requested to take action to enroll on the new mailman service. The new service is not quite ready for use yet. This mail serves as a heads up that the changes will be coming in the next couple of weeks that will require action. A further announcement will be sent when the new mailman is ready to accept subscriptions, as well as warnings before the old lists stop accepting messages. With regards, Daniel [1] https://www.osci.io/ -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|

1 0

Problem starting Windows 11 EE
by Rahul S 13 Oct '23

13 Oct '23

Hi, I configured a W11EE VM using virt-manager and joined it to my work domain. Everything was fine for a while. Later when I tried to reboot, I got the "Preparing Automatic Repair" message and when I selected "Startup Repair", I got the error "Startup repair couldn't repair your PC". I then went to command prompt, started 'diskpart' and ran "list disk" and got the error "there are no fixed disks to show". I have tried re-installing several times - it always ends up in this state. A few details of my system: host OS: OpenSUSE 15.5 libvirt version: 9.0.0-150500.4.3 virtio drivers: https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-vi… Disk device type: virtio bitlocker is enabled in VM I am able to configure and use W11-professional without joining my work domain. The above problem isn't seen there. I booted the broken VM using my linux rescue disk image and examined the partition table. Everything seems to be proper. But windows isn't able to find the disk as I explained above. Can anybody provide any pointers for troubleshooting this ? Thanks, -Rahul

2 1

any advantage to using pool type glusterfs if no GFAPI
by W Kern 10 Oct '23

10 Oct '23

I have used fuse mounted gluster with 'dir' for years. Works great, aside from having to use the --unsafe flag on migrations. I am building up a new system and wondering if using the glusterfs type would be a better/safer choice. I'm not concerned about gfapi (host is U22LTS so I'm not even sure if it has it). I'm not concerned about the automount feature as that happens on start up anyway. I'm more interested if there is any technical or performance reasons to prefer 'glusterfs' pool type over 'dir' of course not having the --unsafe flag would be nice, but thats all scripted in anyway. -wk

2 2

Issue accidentally creating a '--type' defined pool
by Joshua Blake 05 Oct '23

05 Oct '23

Hello, I seem to have accidentally created a pool called "--type", but it doesn't appear in 'virsh pool-list'. See below. [root@vh01 /]# virsh pool-define-as --name --type dir --target /data/storage/ Pool --type defined [root@vh01 /]# virsh pool-list Name State Autostart ------------------------------ isos active yes jblake active yes [root@vh01 /]# virsh pool-destroy '--type' error: command 'pool-destroy' doesn't support option --type I can't also create a new "default" type because the directory exists for this defined '--type' [root@vh01 /]# virsh pool-define-as --name default --type dir --target /data/storage/ error: Failed to define pool default error: operation failed: Storage source conflict with pool: '--type' [root@vh01 /]# virsh pool-delete "--type" error: command 'pool-delete' doesn't support option --type Any help would be greatly appreciated.

3 3

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) 19 Sep '23

19 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 22 Aug '23

22 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 18 Aug '23

18 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

ipv6 can not work for direct type interface
by Yalan Zhang 07 Aug '23

07 Aug '23

Hi there, I have a question regarding direct type interfaces. Would someone be able to take a look at it? When I start 2 VMs on the same host with interface "direct type + bridge mode", just as below: <interface type="direct"> <mac address="52:54:00:9e:7b:51"/> <source dev="eno1" mode="bridge"/> <model type="virtio"/> </interface> The 2 VMs can connect to each other via ipv4, but can not connect to each other via ipv6. Maybe it's related to some kernel parameters, but I don't know how to debug. Is there anyone who can help me? Thank you! BR, Yalan

1 1

Security Logs
by Simon Fairweather 23 Jul '23

23 Jul '23

Hi Is there a way to enable logging of security revents, i.e. a remote client connecting to VNC/SPICE for console. I cannot see/find any documentation, I have also requested a feature request on QEMU gitlab. Regards Simon.

1 0

Issue with libvirtd service and virsh on Debian 13 "trixie" (testing)
by pascal 15 Jul '23

15 Jul '23

Hi, I just upgraded to Debian 13 and observing an issue related to libvirtd service. It happens during up time, the service is initially running and all is working fine. I can run virt-manager and use VMs. Then close virt-manager. After some time (5min), here is what happens : - virt-manager keeps on "Connecting... " when launching it. - "sudo virsh net-list --all" command hangs and does not respond. I have to type Ctrl-C. At that step, I need to restart the libvirtd service : "sudo systemctl restart libvirtd" Then everything is back and running as expected... For 5 minutes as issue comes back. All logs here : https://pastebin.com/qHQWLF4i -=- Versions used : sudo apt policy qemu-system Installé : 1:8.0.2+dfsg-3 sudo apt policy libvirt-daemon-system Installé : 9.5.0-1 $ sudo apt policy virt-manager Installé : 1:4.1.0-2 Can you help here ? Thanks and regards, Pascal

2 1

Cannot access guest with bridged networking when using firewalld (nftables backend) on Debian 12 Bookworm
by Niccolò Belli 12 Jul '23

12 Jul '23

firewalld version 1.3.0-1 libvirt version 9.0.0-4 network-manager version 1.42.4-1 # firewall-cmd --get-active-zones libvirt interfaces: br28 public interfaces: dac0 dac0.100 dac0.28 ftth # firewall-cmd --list-all --zone=public public (active) target: default icmp-block-inversion: no interfaces: dac0 dac0.100 dac0.28 ftth sources: services: dhcpv6-client ssh ports: protocols: forward: yes masquerade: no forward-ports: source-ports: icmp-blocks: rich rules: dac0 is a Direct Attach cable with several vlans. dac0.100 is the vlan where I create the ppoe connection from my FTTH provider. ftth is the ppp name. dac0.28 is the vlan for the public /28 IPv4 subnet. br28 is the bridge where dac0.28 is attached. # brctl show bridge name bridge id STP enabled interfaces br28 8000.d2605c025b1d no dac0.28 vnet1 # firewall-cmd --list-all --zone=libvirt libvirt (active) target: ACCEPT icmp-block-inversion: no interfaces: br28 sources: services: dhcp dhcpv6 dns ssh tftp ports: protocols: icmp ipv6-icmp forward: no masquerade: no forward-ports: source-ports: icmp-blocks: rich rules: rule priority="32767" reject # nft list tables table inet firewalld table ip mangle # nft list table ip mangle # Warning: table ip mangle is managed by iptables-nft, do not touch! table ip mangle { chain FORWARD { type filter hook forward priority mangle; policy accept; oifname "ftth" tcp flags syn / syn,rst tcp option maxseg size 1400-65495 counter packets 0 bytes 0 tcp option maxseg size set rt mtu } } The previous rule is created by NetworkManager to clamp-mss-to-pmtu for the ftth pppoe. This is how I create the bridge and the dac0.28 vlan with NetworkManager: # nmcli con add ifname br28 type bridge con-name br28 ipv4.method manual ipv4.addresses MY_IP/28 connection.zone libvirt # nmcli connection add type vlan con-name dac0.28 ifname dac0.28 vlan.parent dac0 vlan.id 28 ipv4.method disabled ipv6.method disabled master br28 slave-type bridge I also have isc-dhcp-server, wide-dhcpv6-client and radvd running. # nmcli con NAME UUID TYPE DEVICE ftth f370639c-2712-49c2-9749-e39f17102346 pppoe ftth br28 e4d2aad3-ef2d-4ac0-bda5-58471f21655c bridge br28 lo f0327b03-bbc3-4078-8bd1-5225df0ce153 loopback lo vnet1 25ae75cd-1606-4fd7-8213-09f4ef1280c4 tun vnet1 dac0 040e747e-fd7e-41e9-b6a6-ccec9e73c022 ethernet dac0 dac0.100 147c1632-2c60-42f3-a97a-a6733ef69f4c vlan dac0.100 dac0.28 cefb4bf3-dda9-465a-95d0-512ac1294a5b vlan dac0.28 enp1s0 81a44a95-efdc-47e2-9c12-76a0a140ca5a ethernet -- The previous are all dark green expect lo and vnet1 which are light green (externally managed) and enp1s0 which is white (disconnected). The br_netfilter module is not loaded and thus net.bridge.bridge-nf-call-ip6tables, net.bridge.bridge-nf-call-iptables, net.bridge.bridge-nf-call-arptables are not even exposed to /proc/sys/net/bridge. I don't have any nwfilter enabled yet, I'd like to get the basics working first. The guest gets an IP (both v4 and v6) and can reach the internet. Unfortunately the guest cannot be reached from the outside: $ ping GUEST_IP PING GUEST_IP (GUEST_IP) 56(84) bytes of data. From FTTH_IP icmp_seq=1 Packet filtered $ ssh GUEST_IP ssh: connect to host GUEST_IP port 22: No route to host Routed networking works fine, but libvirt is in charge to create everything in that case (creating the bridge, assigning the libvirt-routed zone, enabling the libvirt-routed policies, etc) while bridged networking must be configured manually (at least on non-RedHat distros). What's wrong? It looks suspiciously similar to https://bbs.archlinux.org/viewtopic.php?id=274670 Thanks, Niccolo' Belli

1 0

Starting guest VM with default NAT network breaks host routing
by Mathias Gibbens 20 Jun '23

20 Jun '23

I'm running libvirt 9.0.0 on a Debian 12 bookworm host, setting up a Windows 11 guest using qemu-kvm and the default NAT network[1]. When I start the guest VM, it successfully acquires a DHCP lease, and I can ping other hosts on my local network subnet, but something then happens which messes up routing on the *host* machine, resulting in no access to anything beyond my LAN. If I shutdown the VM, network access returns to normal on the host system. I've been unable to figure out how to fix this, and unfortunately the terms are generic enough that Google isn't much help -- most of the results are about issues with NAT setup (which is working), not route configuration of the host. I did find one similar report[2], but there's no reported solution. I feel like this should be a very common use case, so maybe I've just setup something wrong. Since I haven't been able to solve it on my own, I'm hoping someone will have a pointer to get me going in the right direction. Further details are below, and I'm happy to provide anything else that might prove useful. Thanks, Mathias Before starting the guest VM, routes on the host are: > $ ip route > default via 172.20.1.1 dev wlan0 proto dhcp src 172.20.1.110 metric 600 > 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown > 172.20.1.0/24 dev wlan0 proto kernel scope link src 172.20.1.110 metric 600 > 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown A few seconds after the guest finishes booting, the host gets some new routes, and connectivity outside of the local LAN subnet breaks: > $ ip route > 0.0.0.0 dev vnet0 scope link > default dev vnet0 scope link > default via 172.20.1.1 dev wlan0 proto dhcp src 172.20.1.110 metric 600 > 169.254.0.0/16 dev vnet0 proto kernel scope link src 169.254.103.112 > 169.254.0.0/16 dev virbr0 scope link metric 1000 > 172.20.1.0/24 dev wlan0 proto kernel scope link src 172.20.1.110 metric 600 > 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 Within the guest, I can ping the NAT gateway (192.168.122.1), the host's IP (172.20.1.110), and another computer on the network (172.20.1.105), so NAT appears to be working correctly: > C:\Users\user>ipconfig /all > > Windows IP Configuration > > Host Name . . . . . . . . . . . . : DESKTOP-LGNEPEC > Primary Dns Suffix . . . . . . . : > Node Type . . . . . . . . . . . . : Hybrid > IP Routing Enabled. . . . . . . . : No > WINS Proxy Enabled. . . . . . . . : No > > Ethernet adapter Ethernet: > > Connection-specific DNS Suffix . : > Description . . . . . . . . . . . : Red Hat VirtIO Ethernet Adapter > Physical Address. . . . . . . . . : 52-54-00-AE-05-B2 > DHCP Enabled. . . . . . . . . . . : Yes > Autoconfiguration Enabled . . . . : Yes > Link-local IPv6 Address . . . . . : fe80::2881:98b7:34b8:fe2%11(Preferred) > IPv4 Address. . . . . . . . . . . : 192.168.122.203(Preferred) > Subnet Mask . . . . . . . . . . . : 255.255.255.0 > Lease Obtained. . . . . . . . . . : Monday, June 19, 2023 14:03:57 > Lease Expires . . . . . . . . . . : Monday, June 19, 2023 15:03:57 > Default Gateway . . . . . . . . . : 192.168.122.1 > DHCP Server . . . . . . . . . . . : 192.168.122.1 > DHCPv6 IAID . . . . . . . . . . . : 340939776 > DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-2C-0E-E6-F4-52-54-00-AE-05-B2 > DNS Servers . . . . . . . . . . . : 192.168.122.1 > NetBIOS over Tcpip. . . . . . . . : Enabled > > C:\Users\user>ping 192.168.122.1 > > Pinging 192.168.122.1 with 32 bytes of data: > Reply from 192.168.122.1: bytes=32 time<1ms TTL=64 > Reply from 192.168.122.1: bytes=32 time<1ms TTL=64 > Reply from 192.168.122.1: bytes=32 time<1ms TTL=64 > Reply from 192.168.122.1: bytes=32 time<1ms TTL=64 > > Ping statistics for 192.168.122.1: > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > Approximate round trip times in milli-seconds: > Minimum = 0ms, Maximum = 0ms, Average = 0ms > > C:\Users\user>ping 172.20.1.110 > > Pinging 172.20.1.110 with 32 bytes of data: > Reply from 172.20.1.110: bytes=32 time<1ms TTL=64 > Reply from 172.20.1.110: bytes=32 time<1ms TTL=64 > Reply from 172.20.1.110: bytes=32 time<1ms TTL=64 > Reply from 172.20.1.110: bytes=32 time<1ms TTL=64 > > Ping statistics for 172.20.1.110: > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > Approximate round trip times in milli-seconds: > Minimum = 0ms, Maximum = 0ms, Average = 0ms > > C:\Users\user>ping 172.20.1.105 > > Pinging 172.20.1.105 with 32 bytes of data: > Reply from 172.20.1.105: bytes=32 time=49ms TTL=63 > Reply from 172.20.1.105: bytes=32 time=31ms TTL=63 > Reply from 172.20.1.105: bytes=32 time=26ms TTL=63 > Reply from 172.20.1.105: bytes=32 time=26ms TTL=63 > > Ping statistics for 172.20.1.105: > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > Approximate round trip times in milli-seconds: > Minimum = 26ms, Maximum = 49ms, Average = 33ms ----- [1] -- Here's the NAT configuration: > <network> > <name>default</name> > <uuid>ff6cd6ed-a8fe-4e50-8852-3c93a169e156</uuid> > <forward mode="nat"> > <nat> > <port start="1024" end="65535"/> > </nat> > </forward> > <bridge name="virbr0" stp="on" delay="0"/> > <mac address="52:54:00:4e:80:30"/> > <ip address="192.168.122.1" netmask="255.255.255.0"> > <dhcp> > <range start="192.168.122.2" end="192.168.122.254"/> > </dhcp> > </ip> > </network> [2] -- https://unix.stackexchange.com/questions/723091/kvm-booting-guest-breaks-ne…

1 0

Changing EFI boot order via API
by Lukas Zapletal 19 Jun '23

19 Jun '23

Hello, I would like to be able to change the boot order of an EFI VM via libvirt API. Specifically, I am looking into configuring a VM to boot over HTTP UEFI Boot or HTTPS UEFI Boot (also available as HTTP IPv4 in the firmware). Is this possible? I cannot find anything relevant in the documentation. Thanks. -- Later, Lukas @lzap Zapletal

2 2

Re: virsh not connecting to libvertd ?
by Jerry Buburuz 17 Jun '23

17 Jun '23

Michal PrÃvoznÃk > On 6/12/23 20:17, Jerry Buburuz wrote: >> Just found my issue. >> After I removed the cephfs mounts it worked! >> I will debug ceph. >> I assumed because I could touch files on mounted cephfs it was working. Now virsh list works! > Out of curiosity. Do you perhaps have a storage pool defined over cephfs? I can see two possible sources for the problem: > 1) autostarted storage pool that makes libvirt mount cephfs, or My storage is hard mounted in fstab. This works and it does mount on boot. # fstab on hypervisor user@.mynamefs-01=/ /data ceph noatime,_netdev 0 0 usern@.mynamefs-02=/ /data2 ceph noatime,_netdev 0 0 > 2) a storage pool defined over a path where cephfs is mounted. > The problem with 1) is obvious (in fact it's not specific to ceph, if it was NFS/iSCSI and the server wasn't responding then libvirtd would just hang). I agree with NFS/cephfs or any storage over the network if its not available libvirtd defined pools will cause problems. > The problem with 2) is that for some types of storage pools ('dir' typically) libvirt assumes they are always 'running'. And proceeds to enumerate volumes in that pool (i.e. files under the dir). And if there's a stale mount point, this might stuck libvirtd. But again, this is not limited to ceph, any network FS might do this. > Michal In my case I built this hypervisor using cephfs as my primary storage for virtualmachines over the past year. Its has worked until recently. Recently I had issue with my ceph which likely caused a stale mount. In the past if the storage went offline, after fixing the issue I had no problems and my virualmachines came back to life. In the current case I found: * cephfs working as normal. healthy. * hypervisors mounting using fstab as usual. * libvirtd starts normally no errors (even with cephfs mounted) * virsh fails to connect to libvirt when the cephfs is mounted. If I umount /cephfs, and systemctl restart libvirtd. virsh works! Example "virsh list" , "virsh version" ..etc. I am going to try and maybe delete the iso pools I have. One interesting thing I found yesterday after I restart the hypervisor and try umount /cephfs, libvirtd has one of my pools locked and opened. Its the pool with iso in it. I know someone in a previous response to me mentioned they had issues with iso being stored on cephfs and libvirtd. In order for me to umount /cephfs I have to stop all libvirtd services(livrtd, libvirtd.socket .. ro .. and admin). This makes sense libvirtd has defined pools in my cephfs. thanks jerry

1 0

virsh not connecting to libvertd ?
by Jerry Buburuz 16 Jun '23

16 Jun '23

I have identical two hypervisors same operating system: Ubuntu 22.04.2 LTS Recently both virsh stopped talking to the libvirtd. Both stopped within a few days of each other. Currently if I run: virsh uri virsh version virsh list # virsh list ..nothing just hangs When I ran strace on these broken machines it get stuck at same spot: strace virsh list ... access("/var/run/libvirt/virtqemud-sock", F_OK) = -1 ENOENT (No such file or directory) access("/var/run/libvirt/libvirt-sock", F_OK) = 0 socket(AF_UNIX, SOCK_STREAM, 0) = 5 connect(5, {sa_family=AF_UNIX, sun_path="/var/run/libvirt/libvirt-sock"}, 110) = 0 getsockname(5, {sa_family=AF_UNIX}, [128 => 2]) = 0 futex(0x7fa716a672f0, FUTEX_WAKE_PRIVATE, 2147483647) = 0 fcntl(5, F_GETFD) = 0 fcntl(5, F_SETFD, FD_CLOEXEC) = 0 fcntl(5, F_GETFL) = 0x2 (flags O_RDWR) fcntl(5, F_SETFL, O_RDWR|O_NONBLOCK) = 0 futex(0x7fa716a67348, FUTEX_WAKE_PRIVATE, 2147483647) = 0 eventfd2(0, EFD_CLOEXEC|EFD_NONBLOCK) = 6 write(6, "\1\0\0\0\0\0\0\0", 8) = 8 write(4, "\1\0\0\0\0\0\0\0", 8) = 8 write(4, "\1\0\0\0\0\0\0\0", 8) = 8 futex(0x7fa70c001cb0, FUTEX_WAKE_PRIVATE, 1) = 1 futex(0x7fa716a6786c, FUTEX_WAKE_PRIVATE, 2147483647) = 0 futex(0x7fa716a67378, FUTEX_WAKE_PRIVATE, 2147483647) = 0 write(4, "\1\0\0\0\0\0\0\0", 8) = 8 futex(0x7fa70c001cb0, FUTEX_WAKE_PRIVATE, 1) = 1 write(6, "\1\0\0\0\0\0\0\0", 8) = 8 rt_sigprocmask(SIG_BLOCK, [PIPE CHLD WINCH], [], 8) = 0 poll([{fd=5, events=POLLOUT}, {fd=6, events=POLLIN}], 2, -1) = 2 ([{fd=5, revents=POLLOUT}, {fd=6, revents=POLLIN}]) read(6, "\2\0\0\0\0\0\0\0", 16) = 8 write(6, "\1\0\0\0\0\0\0\0", 8) = 8 write(6, "\1\0\0\0\0\0\0\0", 8) = 8 futex(0x5628ce6e9710, FUTEX_WAKE_PRIVATE, 2147483647) = 0 write(6, "\1\0\0\0\0\0\0\0", 8) = 8 write(6, "\1\0\0\0\0\0\0\0", 8) = 8 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 write(5, "\0\0\0\34 \0\200\206\0\0\0\1\0\0\0B\0\0\0\0\0\0\0\0\0\0\0\0", 28) = 28 write(6, "\1\0\0\0\0\0\0\0", 8) = 8 rt_sigprocmask(SIG_BLOCK, [PIPE CHLD WINCH], [], 8) = 0 poll([{fd=5, events=POLLIN}, {fd=6, events=POLLIN}], 2, -1) = 1 ([{fd=6, revents=POLLIN}]) read(6, "\5\0\0\0\0\0\0\0", 16) = 8 poll([{fd=5, events=POLLIN}, {fd=6, events=POLLIN}], 2, -1 It gets stuck at this poll(). Note I tested strace on identical new install of ubtuntu 22.04 where virsh connects fine and get identical strace, except after this poll() it continues on with read/write ..etc. I turned on debugging for libvirtd and get no errors while virsh is trying to connect. I am able to get a virsh# shell. The shell only hangs when I try "connect, uri, version". Another method of debugging I tried was: LIBVIRT_DEBUG=error LIBVIRT_LOG_FILTERS="1:* " virsh uri .. .. 2023-06-06 20:51:22.312+0000: 1647: debug : doRemoteOpen:1128 : Trying authentication 2023-06-06 20:51:22.312+0000: 1647: debug : virNetMessageNew:44 : msg=0x55b996539680 tracked=0 2023-06-06 20:51:22.312+0000: 1647: debug : virNetMessageEncodePayload:383 : Encode length as 28 2023-06-06 20:51:22.312+0000: 1647: info : virNetClientSendInternal:2151 : RPC_CLIENT_MSG_TX_QUEUE: client=0x55b996538010 len=28 prog=536903814 vers=1 proc=66 type=0 status=0 serial=0 2023-06-06 20:51:22.312+0000: 1647: debug : virNetClientCallNew:2107 : New call 0x55b996535f80: msg=0x55b996539680, expectReply=1, nonBlock=0 2023-06-06 20:51:22.312+0000: 1647: debug : virNetClientIO:1920 : Outgoing message prog=536903814 version=1 serial=0 proc=66 type=0 length=28 dispatch=(nil) 2023-06-06 20:51:22.312+0000: 1647: debug : virNetClientIO:1978 : We have the buck head=0x55b996535f80 call=0x55b996535f80 2023-06-06 20:51:22.312+0000: 1647: info : virEventGLibHandleUpdate:195 : EVENT_GLIB_UPDATE_HANDLE: watch=1 events=0 2023-06-06 20:51:22.312+0000: 1647: debug : virEventGLibHandleUpdate:206 : Update handle data=0x55b996534d30 watch=1 fd=5 events=0 2023-06-06 20:51:22.312+0000: 1647: debug : virEventGLibHandleUpdate:229 : Removed old handle source=0x55b996534de0 2023-06-06 20:51:22.312+0000: 1648: debug : virEventRunDefaultImpl:341 : running default event implementation Any help would be appreciated. thanks jerry

5 7

site certificate
by Daan Hoogland 13 Jun '23

13 Jun '23

LS, I am sure you have already noticed but I want to report it anyway; When compiling a dependend on "https://libvirt.org/maven2/net/juniper/tungsten/juniper-tungsten-api/2.0/ju…", I get a certificate error. I get the a similar error when accessing https://libvirt.org btw hope you can do something with this information, -- Daan

2 1

Criteria used to allow or not live migration
by Gianluca Cecchi 02 Jun '23

02 Jun '23

Hello, I would like to know what are the criteria that allow or not live migration when source and dest hosts have same CPU type (eg Intel) but different models (eg cascade lake vs ice lake). I imagine it is libvirtd to drive this decision, correct? Does libvirt has a sort of table or list of cpu flags that are mandatory / optional? Or how is it established to prevent or not live migration across different couodels systems? Thanks, Gianluca

1 0

issue about libvirtd: daemon can not start
by 王东亚 30 May '23

30 May '23

hi, I installed kmv on ubuntu-22.04-desktop-amd64, after installing some necessary package (qemu-kvm libvirt-daemon-system libvirt-clients bridge-utils virtinst), the libvirtd can not get start, actually, when I running systemctl start libvirtd.service, it'll run a little while (about 3 sec) and then it stops, or should I say it never start. I checked the status, it says ExecStart=/user/sbin/libvirtd $LIBVIRTD_ARGS (code=dumped, signal=TRAP) I processed journalctl -p err, it says ../../../glib/gmem.c:167 failed to allocate xxxxxxx bytes my laptop has 8G phycial memory any suggestion will be appricate. Best Regards.

2 1