- Users - libvirt List Archives

assigning VM to a VLAN on a trunk bridge that exists on LACP bond - how to
by hakan_duran＠hotmail.com 16 Dec '23

16 Dec '23

Dear list, I am trying to create an access port on a VM to connect to VLAN (20 in my case). I am pretty sure my router and switch are setup correctly. I can assign my host machine (hypervisor) an IP address on either VLAN1 or VLAN20 by changing the configuration; in other words, it is connected to the switch via a trunk port. The host machine runs on Debian 12, has ifupdown2 installed, 8021q module is loaded at boot and its /etc/network/interfaces file reads as follows: auto lo iface lo inet loopback # bond interface auto bond0 iface bond0 inet manual bond-slaves enp5s0 enp6s0 bond-mode 802.3ad bond-xmit-hash-policy layer2+3 bond-miimon 100 bond-lacp-rate 1 bond-vlan-aware yes bond-vids 2-500 # vlan 1 auto bridge0.1 iface bridge0.1 inet static address 192.168.1.130/24 gateway 192.168.1.1 # bridge interface auto bridge0 iface bridge0 inet manual bridge-ports bond0 bridge_stp on bridge_fd 2 bridge_maxwait 0 bridge-vlan-aware yes bridge-vids 2-500 source-directory /etc/network/interfaces.d EOF The host gets an IP address of 192.168.1.130 from VLAN1, as intended, by these settings. VM1 (also Debian 12) is connected to bridge0, which is designed as a trunk bridge, and CAN get an IP address in the 192.168.1.0/24 network (aka VLAN1), but CANNOT get an IP address in the 192.168.20.0/24 network 9aka VLAN20). VMs network interface is named as enp1s0 and I tried creating an interface named enp1s0.20 in its own /etc/network/interfaces file without any change in behavior. It just does not connect to VLAN20, no matter what I tried. What am I missing? I am very thankful for the pointers, and will be happy to provide further information, try recommended settings and report back. Best!

1 1

re: assigning VM to a VLAN on a trunk bridge that exists on LACP bond - how to
by Hakan E. Duran 16 Dec '23

16 Dec '23

I was able to achieve what I wanted to do by the /etc/network/interfaces file posted below on the host. KVM/QEMU does not accept the bridge notation with dots in it, such as bridge0.20. Instead, one needs to create a separate vlan definition and a bridge on top of that vlan. This would create an access port for the VMs that use that bridge. What I was trying to do was to create a trunk port on a bridge, and by the static IP chosen for VMs, let each VM claim their VLANs. In this working version, the access ports claim the VLAN that the VM would belong to instead. I hope that this would help people avoid the suffering I endured during the last week to achieve this, lol! [code] auto lo iface lo inet loopback # bond interface auto bond0 iface bond0 inet manual bond-slaves enp5s0 enp6s0 bond-mode 802.3ad bond-xmit-hash-policy layer2+3 bond-miimon 100 bond-lacp-rate 1 # vlan 20 auto vlan20 iface vlan20 inet manual vlan-id 20 vlan-raw-device bridge0 auto bridge20 iface bridge20 inet manual bridge-ports vlan20 # bridge interface auto bridge0 iface bridge0 inet manual bridge-ports bond0 bridge_stp on bridge_fd 2 bridge_maxwait 0 bridge-vlan-aware yes bridge-vids 1-500 auto bridge0.1 iface bridge0.1 inet static address 192.168.1.130/24 gateway 192.168.1.1 [/code]

1 0

How can I have a list of interfaces in virt-manager network config
by Marc Haber 12 Dec '23

12 Dec '23

Hi, I have a standalone VM host running Debian bookworm, which features libvirt 9.0.0 and qemu 7.2. My users mostly have Debian unstable on their notebooks, which currently comes with virt manager 4.1.0. The host has a 802.1Q VLAN trunk to the network with contains a number of VLANs. Each VLAN has a bridge host-side, for example VLAN 188: [3/114]mh@spiral:~ $ ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host noprefixroute valid_lft forever preferred_lft forever 2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 4c:52:62:b4:53:12 brd ff:ff:ff:ff:ff:ff altname enp2s0 inet6 fe80::4e52:62ff:feb4:5312/64 scope link valid_lft forever preferred_lft forever 5: int188: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 96:f3:9b:c6:7f:db brd ff:ff:ff:ff:ff:ff inet6 fe80::94f3:9bff:fec6:7fdb/64 scope link valid_lft forever preferred_lft forever 21: vlan188@eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master int188 state UP group default qlen 1000 link/ether 4c:52:62:b4:53:12 brd ff:ff:ff:ff:ff:ff This is configured with systemd-networkd: ==> /etc/systemd/network/10-eno1.network <== [Match] Name=eno1 [Network] Description=eno1 VLAN 1xx DHCP=no IPForward=no IPv6AcceptRA=no IPv6SendRA=no DHCPv6PrefixDelegation=no [Network] VLAN=vlan188 /etc/systemd/network/int188.netdev <== [NetDev] Name=int188 Kind=bridge ==> /etc/systemd/network/int188.network <== [Match] Name=int188 [Network] Description=int188 Labor DHCP=no IPForward=no IPv6AcceptRA=no IPv6SendRA=no DHCPv6PrefixDelegation=no ==> /etc/systemd/network/vlan188.netdev <== [NetDev] Name=vlan188 Kind=vlan [VLAN] Id=188 ==> /etc/systemd/network/vlan188.network <== [Match] Name=vlan188 [Network] Description=vlan188 Labor Bridge=int188 DHCP=no IPForward=no IPv6AcceptRA=no IPv6SendRA=no DHCPv6PrefixDelegation=no I can attach a VM to that vlan in virt-manager by selecting the virtual NIC, network source: bridge device, device name: int188. This works and results in the following XML snippet: <interface type="bridge"> <mac address="52:54:00:af:fd:f8"/> <source bridge="int188"/> <model type="virtio"/> <address type="pci" domain="0x0000" bus="0x01" slot="0x00" function="0x0"/> </interface> Network configuration host-wise looks like this: 1 [13/119]mh@spiral:~ $ virsh net-list Name State Autostart Persistent ---------------------------------------- [14/120]mh@spiral:~ $ virsh iface-list Name State MAC Address -------------------------------------- eno1 active 4c:52:62:b4:53:12 int188 active 96:f3:9b:c6:7f:db [15/120]mh@spiral:~ $ virsh iface-dumpxml int188 <interface type='bridge' name='int188'> <mtu size='1500'/> <bridge stp='off' delay='1500'> <interface type='vlan' name='vlan188'> <link speed='1000' state='up'/> <vlan tag='188'> <interface name='eno1'/> </vlan> </interface> </bridge> </interface> [16/121]mh@spiral:~ $ So far so good, this is useable. However, I need to document a list of available interfaces since the interface name "int188" needs to be entered in a text area in virt-manager. The dialog in virt-manager also has a list box that is pre-filled with "Virtual Network 'default'", "Bridge Device..." and "Macvtap device...", and the text area for the bridge device name shows up once "Bridge device" is selected. Can I configure somewhere (may it be in libvirt, may it be in virt-manager) a list of network interfaces, so that this list box has like "Bridge Device int181", "Bridge Device int188" etc in addition to the three entries that are already present, to give my users a hint about which interfaces might be available? You can also point me towards documentation if I might have missed something. Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany | lose things." Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421

3 5

Can't connect to libvirt
by list-libvirt-users＠aliases.systohc.net 12 Dec '23

12 Dec '23

Hi folks! I'm trying to connect to a self-compiled libvirt 9.10.0 from python, but get the following error: Python 3.12.0 (main, Oct 3 2023, 19:47:47) [GCC 11.4.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import libvirt as lv >>> conn = lv.openReadOnly(None) libvirt: DBus Utils error : error from service: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.libvirt.unix.monitor is not registered Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/home/user/sw/python3/lib/python3.12/site-packages/libvirt.py", line 349, in openReadOnly raise libvirtError('virConnectOpenReadOnly() failed') libvirt.libvirtError: error from service: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.libvirt.unix.monitor is not registered What is the issue here? Also, I've grepped the error in any source but found nothing! Greetings, Fabiano

2 1

Re: Shared memory usage
by Martin Kletzander 11 Dec '23

11 Dec '23

On Fri, Dec 08, 2023 at 09:45:23AM +0000, Sánta, Márton (ext) via Users wrote: >Dear Users, > >I tried out shared memory using libvirt. When I configure it in the XML >(ivshmem-plain), I have to provide a name for it and after starting the >VM I can see the appropriate file on the host in the /dev/shm/ >directory. My problem is that I could not find any official >documentation about the usage of that shared memory. On the guest side, >I have found the PCI device related to it, but I do not know how to use >it. Is there any available command line tool to read from or write to >this memory or is it only possible with a user application? Could you >provide my what is the most common solution for this? > Hi, ivshmem is something you probably want to use only if you have a specific need. Maybe looking at other solutions would be more suitable. In any case you can check out the documentation from QEMU here: https://www.qemu.org/docs/master/specs/ivshmem-spec.html >Thank you in advance for your reply and help! > >Best regards, > >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. >_______________________________________________ >Users mailing list -- users(a)lists.libvirt.org >To unsubscribe send an email to users-leave(a)lists.libvirt.org

1 0

search docs on www.libvirt.org
by Wolfgang Rohdewald 09 Dec '23

09 Dec '23

Hi, your website allows to search Docs. This automatically uses Google. IMHO it is very unfriendly not to warn people that an external data harvester is involved in your local search. Please consider adding a warning. BTW your website massively violates EU data privacy rights. You have no Impressum and no info about your privacy policy. Your website does not even have a contact address. -- mit freundlichen Grüssen Wolfgang Rohdewald

5 9

Shared memory usage
by Sánta, Márton (ext) 08 Dec '23

08 Dec '23

Dear Users, I tried out shared memory using libvirt. When I configure it in the XML (ivshmem-plain), I have to provide a name for it and after starting the VM I can see the appropriate file on the host in the /dev/shm/ directory. My problem is that I could not find any official documentation about the usage of that shared memory. On the guest side, I have found the PCI device related to it, but I do not know how to use it. Is there any available command line tool to read from or write to this memory or is it only possible with a user application? Could you provide my what is the most common solution for this? Thank you in advance for your reply and help! Best regards, 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.

1 0

a VM with secure boot does not survive a reset
by lejeczek 03 Dec '23

03 Dec '23

Hi guys. A VM created with: -> $ virt-install --boot uefi --name=client-efi-secureboot --os-variant centos-stream9 --memory $((4*1024)) --graphics=vnc,listen=0.0.0.0 --accelerate --cpuset 2 --cpu host-model --pxe --disk=/00-VMsy/client-efi-secureboot.qcow2 --network network=10_3_1,,model=virtio when *virsh reset* while running will power off, instead of *restart*. Whereas: -> $ virt-install --boot uefi,firmware.feature0.name=secure-boot,firmware.feature0.enabled=no --name=client-efi-no-secureboot --os-variant centos-stream9 --memory $((4*1024)) --graphics=vnc,listen=0.0.0.0 --accelerate --cpuset 2 --cpu host-model --pxe --disk=/00-VMsy/client-efi-no-secureboot.qcow2 --network network=10_3_1,,model=virtio does behave as expected when *reset*. libvirt-libs-9.5.0-6.el9.x86_64 BTW. Where should bug reports go to theses days - I'm trying Redhat's Jira but cannot file a BZ in _RHEL_ category. I get no errors nor warnings but Jira won't let me file anything there, but I can in Centos category. thanks, L.

1 0

Re: Libvirt and Ceph: libvirtd tries to open random RBD images
by Daniel P. Berrangé 02 Dec '23

02 Dec '23

On Mon, Nov 20, 2023 at 01:21:24PM +0000, Jayanth Reddy wrote: > Hello Daniel, > > Thank you for the response. Please also let me know why libvirtd says "No such file or directory" even though the block images exist and are healthy. I don't know the cause - all we're seeing is that the API call if ((ret = rbd_open_read_only(ptr->ioctx, vol->name, &image, NULL)) < 0) { is failing. Maybe RBD has permission denying access on this host ? Or is RBD preventing this host access the volume, becuase another VM has it in use With regards, Daniel -- |: 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 :|

2 4

pxe efi boot - bdsdxe boot0002 access denied
by lejeczek 01 Dec '23

01 Dec '23

Hi guys I have VMs which fail to boot with error as per the subject. I suspect this is due to: <os firmware='efi'> <type arch='x86_64' machine='pc-q35-rhel9.2.0'>hvm</type> <firmware> <feature enabled='yes' name='enrolled-keys'/> <--- HERE <feature enabled='yes' name='secure-boot'/> <---- HERE ? </firmware> <loader readonly='yes' secure='yes' type='pflash'>/usr/share/edk2/ovmf/OVMF_CODE.secboot.fd</loader> <nvram template='/usr/share/edk2/ovmf/OVMF_VARS.secboot.fd'>/var/lib/libvirt/qemu/nvram/centos-efi_VARS.fd</nvram> <boot dev='network'/> <boot dev='hd'/> </os> Would you have any thoughts on how to fix, to work around it? many thanks, L.

2 1

Internal Error: libxenlight failed to create new domain "FreeBSD-13.2"
by marietto2008＠gmail.com 29 Nov '23

29 Nov '23

Hello to everyone. I'm trying to use xen as a hypervisor instead of kvm to boot FreeBSD on my ARM Chromebook where I have installed Devuan 5. A developer said that it can work. In fact he said : "That might work. libvirt + virt-manager with the xen accelerator might work on the ARM Chromebook. That's because as far as I know Xen integration in libvirt is done via linking to libxl directly and libxl is supported and working on ARM" Unfortunately something is not working properly. What I did has been to reboot the machine in xen,enable libvirtd & and virtlogd & and virt-manager &,but this is what happened : root@devuan-bunsen:/Dati/virt-manager-4.1.0# ./virt-manager & [3] 2507 root@devuan-bunsen:/Dati/virt-manager-4.1.0# info : libvirt version: 9.7.0 info : hostname: devuan-bunsen error : virConnectGetAllDomainStats:12595 : this function is not supported by the connection driver: virConnectGetAllDomainStats error : virDomainListAllSnapshots:519 : this function is not supported by the connection driver: virDomainListAllSnapshots [3]+ Completed ./virt-manager root@devuan-bunsen:/mnt/zroot2/zroot2# error : libxlDomainStartPerform:1256 : internal error: libxenlight failed to create new domain 'FreeBSD-13.2 Traceback (most recent call last): File "/Dati/virt-manager-4.1.0/./virtManager/asyncjob.py", line 72, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/Dati/virt-manager-4.1.0/./virtManager/createvm.py", line 2008, in _do_async_install installer.start_install(guest, meter=meter) File "/Dati/virt-manager-4.1.0/./virtinst/install/installer.py", line 695, in start_install domain = self._create_guest( ^^^^^^^^^^^^^^^^^^^ File "/Dati/virt-manager-4.1.0/./virtinst/install/installer.py", line 637, in _create_guest domain = self.conn.createXML(initial_xml or final_xml, 0) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/libvirt.py", line 4481, in createXML raise libvirtError('virDomainCreateXML() failed') libvirt.libvirtError: internal error: libxenlight failed to create new domain 'FreeBSD-13.2' you may also be interested to give a look at this picture : https://ibb.co/Lh0xkfy ...between the running processes I see this : # ps ax | grep qemu 1507 ? Sl 0:00 /usr/libexec/xen-qemu-system-i386 -xen-domid 0 -xen-attach -name dom0 -no graphic -M xenpv -daemonize -monitor none -serial none -parallel none -pidfile /run/qemu-dom0.pid The interesting point is that it is using xen-qemu-system-i386. Is it supposed to work on an ARM architecture ? What's the problem that I may have now ?

3 4

Libvirt/KVM/VLANs/teamed interfaces
by Ken D'Ambrosio 29 Nov '23

29 Nov '23

Hey, all. So, we've got some OpenStack controllers that I'm virtualizing, and it's going really well... until the most recent host I was dooing, the fifth of eight. Everything looked like it largely should, except that there was zero traffic on the VLANs on the VM. Sniffing physical ports showed it hitting the machine, but nothing made it into VLAN/namespace land on the VMs. After banging my head against the wall a lot, I realized that, for some reason, the interface team (which is hot/cold) was using the secondary interface, not the primary. I turned that interface down, the primary came up, and everything started working great. (It only became apparent that something like that might be the case when I compared the broken machine's output from "brctl listmacs br0", vs. that of a working machine.) Any idea what's _really_ not working, deep down on the stack? Is there a way around it? Thanks! -Ken

1 0

Permission Denied error when I try to open the image file stored on the ZFS disk accessed through sshfs from another machine...
by marietto2008＠gmail.com 29 Nov '23

29 Nov '23

Hello to everyone. I would like to boot the FreeBSD 13.2 image file using Libvirt + virt-manager. I have stored the image on the external hard drive,"formatted" with ZFS while I'm using Devuan 5 installed on my ARM (32 bit) Chromebook,where I have access to the ZFS disk using sshfs using this command : sshfs -o Compression=no -o allow_root -o transform_symlinks -o password_stdin root@192.168.1.2:/mnt/zroot2/zroot2 /mnt/zroot2/zroot2 <<< 'pass' This is the error I get when I try to boot the image file using virt-manager : error : qemuProcessReportLogError:1990 : internal error: process exited while connecting to monitor: 2023-11-28T20:53:46.882586Z qemu-system-arm: -blockdev {"driver":"file","filename":"/mnt/zroot2/zroot2/OS/Chromebook/FreeBSD-guestOS/freebsd-kvm/FreeBSD-13.2-RELEASE-armv7.img","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}: Could not open '/mnt/zroot2/zroot2/OS/Chromebook/FreeBSD-guestOS/freebsd-kvm/FreeBSD-13.2-RELEASE-armv7.img': Permission denied According with this post : https://forum.manjaro.org/t/virt-manager-doesnt-work-permission-denied/1081… I tried to do the following : root@devuan-bunsen:/mnt/zroot2/zroot2/OS/Chromebook/FreeBSD-guestOS/freebsd-kvm# getfacl /mnt/zroot2/zroot2/OS/Chromebook/FreeBSD-guestOS/freebsd-kvm/ getfacl: Removing leading '/' from absolute path names # file: mnt/zroot2/zroot2/OS/Chromebook/FreeBSD-guestOS/freebsd-kvm/ # owner: root # group: root user::rwx group::rwx other::rwx root@devuan-bunsen:/mnt/zroot2/zroot2/OS/Chromebook/FreeBSD-guestOS/freebsd-kvm# setfacl -m user:libvirt-qemu:--x /mnt/zroot2/zroot2/OS/Chromebook/FreeBSD-guestOS/freebsd-kvm/ setfacl: /mnt/zroot2/zroot2/OS/Chromebook/FreeBSD-guestOS/freebsd-kvm/: Operation not supported Can someone help me to understand where the error is and how to fix it ? thanks.

3 4

Mentor moja global at CodePeak 2023!
by gautam.sharma＠iitg.ac.in 28 Nov '23

28 Nov '23

1 0

Enabling libiscsi with libvirt on Rocky 9
by will.gorman＠joyent.com 23 Nov '23

23 Nov '23

I am running into a problem attaching an iscsi disk to a VM in libvirt using "virsh attach-device" on Rocky 9 with the following error: "unable to execute QEMU command 'blockdev-add': Unknown driver 'iscsi'". I've found some indications that libiscsi is being removed from RHEL 9, like https://bugzilla.redhat.com/show_bug.cgi?id=1967133 but it's not clear to me what alternatives might be available for libvirt users that depend on the libiscsi-based block device driver. Are there alternate packages that can be installed to re-enable the iscsi block device driver for qemu on RHEL 9 based systems? Or would it be necessary to rebuild libvirt/qemu to get this block device driver to work again? Thanks, Will Gorman

3 2

Enabling libiscsi with libvirt on Rocky 9
by Will Gorman 20 Nov '23

20 Nov '23

I am running into a problem attaching an iscsi disk to a VM in libvirt using "virsh attach-device" on Rocky 9 with the following error: "unable to execute QEMU command 'blockdev-add': Unknown driver 'iscsi'". I've found some indications that libiscsi is being removed from RHEL 9, like https://bugzilla.redhat.com/show_bug.cgi?id=1967133 but it's not clear to me what alternatives might be available for libvirt users that depend on the libiscsi-based block device driver. Are there alternate packages that can be installed to re-enable the iscsi block device driver for qemu on RHEL 9 based systems? Or would it be necessary to rebuild libvirt/qemu to get this block device driver to work again? Thanks, Will Gorman

1 0

Libvirt and Ceph: libvirtd tries to open random RBD images
by Jayanth Reddy 20 Nov '23

20 Nov '23

Hello Users, We're using libvirt with KVM and the orchestrator is Cloudstack. I raised the issue already at Cloudstack at https://github.com/apache/cloudstack/issues/8211 but appears to be at libvirtd. Below is our environment & issue description: It appears that one of our Cloudstack KVM clusters having 8 hosts is having the issue. We have HCI on these 8 hosts and there are approximately 700+ VMs running. But strange enough, there are these logs like below on hosts. Oct 25 13:38:11 hv-01 libvirtd[9464]: failed to open the RBD image '087bb114-448a-41d2-9f5d-6865b62eed15': No such file or directory Oct 25 20:35:22 hv-01 libvirtd[9464]: failed to open the RBD image 'ccc1168a-5ffa-4b6d-a953-8e0ac788ebc5': No such file or directory Oct 26 09:48:33 hv-01 libvirtd[9464]: failed to open the RBD image 'a3fe82f8-afc9-4604-b55e-91b676514a18': No such file or directory Oct 26 10:38:17 hv-01 libvirtd[9464]: End of file while reading data: Input/output error We've got DNS servers on which there is an`A` record resolving to all the IPv4 Addresses of 8 monitors and there have not been any issues with the DNS resolution. But the issue of "failed to open the RBD image 'ccc1168a-5ffa-4b6d-a953-8e0ac788ebc5': No such file or directory" gets more weird because the VM that is making use of that RBD image lets say "087bb114-448a-41d2-9f5d-6865b62eed15" is running on altogether different host like "hv-06". On further inspection of that specific Virtual Machine, it has been running on that host "hv-06" for more than 4 months or so (looked at "Last updated" field). Fortunately, the Virtual Machine has no issues and has been running since then. Thanks, Jayanth

2 2

Problem setting up SGX domain
by Wojtek Porczyk 16 Nov '23

16 Nov '23

Hi, users@, I'm attempting to set up domain with SGX EPC memory. When starting it, I get this error: # virsh start astoria-test-1 error: Failed to start domain 'astoria-test-1' error: internal error: process exited while connecting to monitor: libnuma: Warning: /sys not mounted or invalid. Assuming one node: Permission denied 2023-11-16T14:04:26.919285Z qemu-system-x86_64: The nodes select no CPUs When removing <memory model='sgx-epc'> node from XML, the domain starts fine. I've attached is domain.xml for it, with the section commented. Also there are logs from happy and sad case. The libnuma error seems to stem from this place: https://github.com/numactl/numactl/blob/fc999282e6663d6844773e6065bbee3270f… This makes no sense to me, because the file is there and available: # sudo -u libvirt-qemu cat /sys/devices/system/node/node0/cpumap fff I also don't understand why qemu says "The nodes select no CPUs" (https://gitlab.com/qemu-project/qemu/-/blob/34a5cb6d8434303c170230644b2a7c1…) DDG has failed me in all cases. I've also tried to follow the recommendation from https://libvirt.org/formatdomaincaps.html#sgx-capabilities: For more details on the SGX feature, please follow resources in the SGX developer's document store. ...and the only think that I've found relevant to libvirt was this document: https://www.intel.com/content/www/us/en/developer/articles/technical/virtua… which suggests to play with <qemu:commandline> instead. host: Debian 12, libvirt 9.0.0, QEMU 7.2, virtinst 4.1 (see dpkg-l attachment) guest: Ubuntu 22.04 (jammy) cloud image The domain in quesion was defined using virt-install with cloud-init, then I was editing XML with `virsh edit`. Relevant snippet from `virsh domcapabilities`: <sgx supported='yes'> <flc>yes</flc> <sgx1>yes</sgx1> <sgx2>no</sgx2> <section_size unit='KiB'>95744</section_size> <sections> <section node='0' size='95744' unit='KiB'/> </sections> </sgx> System-wide logs do not contain anything relevant. I'm happy to provide additional info if needed. Anyone can point me to a solution? -- pozdrawiam / best regards Wojtek Porczyk Gramine / Invisible Things Lab I do not fear computers, I fear lack of them. -- Isaac Asimov

1 0

windows install fails with error 0x80070001
by daggs 09 Nov '23

09 Nov '23

Greetings, following an issue with my windows install, I've had to reinstall windows 11 on kvm. I start the vm and the install starts, the install process starts, I add the virtio scsi controller and the hdd gets detected. next I start the install and get the same error as see here: https://howfix.net/computer/0x80070001/ on when getting to the "Getting files ready for installation" stage. I suspect that there is a bug with the windows scsi virtio driver when using hdd pass-through this is the vm's xml: https://bpa.st/63RA my host system is based on qemu-8.1.2, libvirt-9.8.0, virtiofsd-1.8.0, virtio-win-0.1.229.1 and kernel-6.6.0. what can I do?

1 1

unsubscribe
by Miguel Ping 08 Nov '23

08 Nov '23

1 0

[FOSDEM] Call for participation: Virtualization and Cloud infrastructure Room at FOSDEM 2024
by Piotr Kliczewski 08 Nov '23

08 Nov '23

We are excited to announce that the call for proposals is now open for the Virtualization and Cloud infrastructure devroom at the upcoming FOSDEM 2024, to be hosted on February 3rd 2024. This devroom is a collaborative effort, and is organized by dedicated folks from projects such as OpenStack, Xen Project, KubeVirt, QEMU, KVM, and Foreman. We would like to invite all those who are involved in these fields to submit your proposals by December 8th, 2023. About the Devroom The Virtualization & IaaS devroom will feature session topics such as open source hypervisors or virtual machine managers such as Xen Project, KVM, bhyve and VirtualBox as well as Infrastructure-as-a-Service projects such as KubeVirt, Apache CloudStack, OpenStack, QEMU and OpenNebula. This devroom will host presentations that focus on topics of shared interest, such as KVM; libvirt; shared storage; virtualized networking; cloud security; clustering and high availability; interfacing with multiple hypervisors; hyperconverged deployments; and scaling across hundreds or thousands of servers. Presentations in this devroom will be aimed at developers working on these platforms who are looking to collaborate and improve shared infrastructure or solve common problems. We seek topics that encourage dialog between projects and continued work post-FOSDEM. Important Dates Submission deadline: 8th December 2023 Acceptance notifications: 10th December 2023 Final schedule announcement: 15th December 2023 Devroom: 3rd February 2024 Submit Your Proposal All submissions must be made via the Pretalx event planning site[1]. It is a new submission system so you will need to create an account. If you submitted proposals for FOSDEM in previous years, you won’t be able to use your existing account. During submission please make sure to select Virtualization and Cloud infrastructure from the Track list. Please fill out all the required fields, and provide a meaningful abstract and description of your proposed session. Submission Guidelines We expect more proposals than we can possibly accept, so it is vitally important that you submit your proposal on or before the deadline. Late submissions are unlikely to be considered. All presentation slots are 30 minutes, with 20 minutes planned for presentations, and 10 minutes for Q&A. All presentations will be recorded and made available under Creative Commons licenses. In the Submission notes field, please indicate that you agree that your presentation will be licensed under the CC-By-SA-4.0 or CC-By-4.0 license and that you agree to have your presentation recorded. For example: "If my presentation is accepted for FOSDEM, I hereby agree to license all recordings, slides, and other associated materials under the Creative Commons Attribution Share-Alike 4.0 International License. Sincerely, <NAME>." In the Submission notes field, please also confirm that if your talk is accepted, you will be able to attend FOSDEM and deliver your presentation. We will not consider proposals from prospective speakers who are unsure whether they will be able to secure funds for travel and lodging to attend FOSDEM. (Sadly, we are not able to offer travel funding for prospective speakers.) Code of Conduct Following the release of the updated code of conduct for FOSDEM, we'd like to remind all speakers and attendees that all of the presentations and discussions in our devroom are held under the guidelines set in the CoC and we expect attendees, speakers, and volunteers to follow the CoC at all times. If you submit a proposal and it is accepted, you will be required to confirm that you accept the FOSDEM CoC. If you have any questions about the CoC or wish to have one of the devroom organizers review your presentation slides or any other content for CoC compliance, please email us and we will do our best to assist you. Questions? If you have any questions about this devroom, please send your questions to our devroom mailing list. You can also subscribe to the list to receive updates about important dates, session announcements, and to connect with other attendees. See you all at FOSDEM! [1] <https://penta.fosdem.org/submission/FOSDEM17> https://pretalx.fosdem.org/fosdem-2024/cfp [2] virtualization-devroom-manager at fosdem.org

1 0

Passing through a YubiKey to a Windows VM for physical touch activation
by Michael Kjörling 06 Nov '23

06 Nov '23

I have a need to pass through a YubiKey to a Windows (10) VM guest such that Windows in the guest will let me use it with physical touch activation for 2FA. For those times, I am physically at the VM host, so I don't need _remote_ redirection into the guest, and I'm fine with plugging and unplugging the YubiKey physically on an as-needed basis. If I simply redirect the USB device through the virt-manager GUI, my experience is that it has at best worked very much unreliably, and often not at all. Searching the web hasn't helped. Does anyone have a recipe for that to work _reliably_? -- Michael Kjörling 🔗 https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”

3 4

Clocks and Timers
by Simon Fairweather 05 Nov '23

05 Nov '23

Hi, If I have the following XML section does this imply that presence is default of on for rtc and pit? <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> Are there any other reference guides to best setup of timers apart from the XML document for different OS types? Regards Simon.

1 0

Re: hdd kills vm
by daggs 04 Nov '23

04 Nov '23

> Sent: Thursday, October 26, 2023 at 9:50 AM > From: "Martin Kletzander" <mkletzan(a)redhat.com> > To: "daggs" <daggs(a)gmx.com> > Cc: libvir-list(a)redhat.com > Subject: Re: hdd kills vm > > On Wed, Oct 25, 2023 at 03:06:55PM +0200, daggs wrote: > >> Sent: Tuesday, October 24, 2023 at 5:28 PM > >> From: "Martin Kletzander" <mkletzan(a)redhat.com> > >> To: "daggs" <daggs(a)gmx.com> > >> Cc: libvir-list(a)redhat.com > >> Subject: Re: hdd kills vm > >> > >> On Mon, Oct 23, 2023 at 04:59:08PM +0200, daggs wrote: > >> >Greetings Martin, > >> > > >> >> Sent: Sunday, October 22, 2023 at 12:37 PM > >> >> From: "Martin Kletzander" <mkletzan(a)redhat.com> > >> >> To: "daggs" <daggs(a)gmx.com> > >> >> Cc: libvir-list(a)redhat.com > >> >> Subject: Re: hdd kills vm > >> >> > >> >> On Fri, Oct 20, 2023 at 02:42:38PM +0200, daggs wrote: > >> >> >Greetings, > >> >> > > >> >> >I have a windows 11 vm running on my Gentoo using libvirt (9.8.0) + qemu (8.1.2), I'm passing almost all available resources to the vm > >> >> >(all 16 cpus, 31 out of 32 GB, nVidia gpu is pt), but the performance is not good, system lags, takes long time to boot. > >> >> > >> >> There are couple of things that stand out to me in your setup and I'll > >> >> assume the host has one NUMA node with 8 cores, each with 2 threads as, > >> >> just like you set it up in the guest XML. > >> >thats correct, see: > >> >$ lscpu | grep -i numa > >> >NUMA node(s): 1 > >> >NUMA node0 CPU(s): 0-15 > >> > > >> >however: > >> >$ dmesg | grep -i numa > >> >[ 0.003783] No NUMA configuration found > >> > > >> >can that be the reason? > >> > > >> > >> no, this is fine, 1 NUMA node is not a NUMA, technically, so that's > >> perfectly fine. > >thanks for clarifying it for me > > > >> > >> >> > >> >> * When you give the guest all the CPUs the host has there is nothing > >> >> left to run the host tasks. You might think that there "isn't > >> >> anything running", but there is, if only your init system, the kernel > >> >> and the QEMU which is emulating the guest. This is definitely one of > >> >> the bottlenecks. > >> >I've tried with 12 out of 16, same behavior. > >> > > >> >> > >> >> * The pinning of vCPUs to CPUs is half-suspicious. If you are trying to > >> >> make vCPU 0 and 1 be threads on the same core and on the host the > >> >> threads are represented as CPUs 0 and 8, then that's fine. If that is > >> >> just copy-pasted from somewhere, then it might not reflect the current > >> >> situation and can be source of many scheduling issues (even once the > >> >> above is dealt with). > >> >I found a site that does it for you, if it is wrong, can you point me to a place I can read about it? > >> > > >> > >> Just check what the topology is on the host and try to match it with the > >> guest one. If in doubt, then try it without the pinning. > >I can try to play with it, what I don't know is what should be the mapping logic? > > > > Threads on the same core in the guest should map to threads on the same > core in the host. Since there is no NUMA that should be enough to get > the best performance. But even misconfiguration of this will not > introduce lags in the system if it has 8 CPUs. So that's definitely not > the root cause of the main problem, it just might be suboptimal. > > >> > >> >> > >> >> * I also seem to recall that Windows had some issues with systems that > >> >> have too many cores. I'm not sure whether that was an issue with an > >> >> edition difference or just with some older versions, or if it just did > >> >> not show up in the task manager, but there was something that was > >> >> fixed by using either more sockets or cores in the topology. This is > >> >> probably not the issue for you though. > >> >> > >> >> >after trying a few ways to fix it, I've concluded that the issue might be related to the why the hdd is defined at the vm level. > >> >> >here is the xml: https://bpa.st/MYTA > >> >> >I assume that the hdd sits on the sata ctrl causing the issue but I'm not sure what is the proper way to fix it, any ideas? > >> >> > > >> >> > >> >> It looks like your disk is on SATA, but I don't see why that would be an > >> >> issue. Passing the block device to QEMU as VirtIO shouldn't cause that > >> >> much of a difference. Try measuring the speed of the disk on the host > >> >> and then in the VM maybe. Is that SSD or NVMe? I presume that's not > >> >> spinning rust, is it. > >> >as seen, I have 3 drives, 2 cdroms as sata and one hdd pt as virtio, I read somewhere that if the controller of the virtio > >> >device is sata, than it doesn't uses the virtio optimally. > >> > >> Well it _might_ be slightly more beneficial to use virtio-scsi or even > >> <disk type='block' device='lun'>, but I can't imagine that would make > >> the system lag. I'm not that familiar with the details. > >configure virtio-scsi and sata-scai at the same time? > > > > Yes, forgot that, sorry. Try virtio-scsi. You could also go farther > and pass through the LUN or the whole HBA (if you don't need to access > any other disk on it) to the VM. Try the information presented here: > > https://libvirt.org/formatdomain.html#usb-pci-scsi-devices > > >> > >> >it is a spindle, nvmes are too expensive where I live, frankly, I don't need lightning fast boot, the other BM machines running windows on spindle > >> >run it quite fast and they aren't half as fast as this server > >> > > >> > >> That might actually be related. The guest might think it is a different > >> type of disk and use completely suboptimal scheduling. This might > >> actually be solved by passing it as <disk device='lun'..., but at this > >> point I'm just guessing. > >I'll look into that, thanks. so bottom line, you suggest the following: 1. remove the manual cpu pin, let qemu sort that out. 2. add a virtio scsi controller and connect the os hdd to it 3. pass the hss via scsi pt and not dev node 4. if I able to do #3, no need to add device='lun' as it won't use the disk option Dagg.

2 9

ANNOUNCE: Mailing list move complete
by Daniel P. Berrangé 01 Nov '23

01 Nov '23

This is an announcement to the effect that the mailing list move is now complete. TL;DR the new list addresses are: * announce(a)lists.libvirt.org (formerly libvirt-announce(a)redhat.com) Low volume, announcements of releases and other important info * users(a)lists.libvirt.org (formerly libvirt-users(a)redhat.com) End user questions and discussions and collaboration * devel(a)lists.libvirt.org (formerly libvir-list(a)redhat.com) Patch submission for development of main project * security(a)lists.libvirt.org (formerly libvir-security(a)redhat.com) Submission of security sensitive bug reports The online archive and membership mgmt interface is https://lists.libvirt.org In my original announcement[1] I mentioned that people would need to manually re-subscribe. Due to a mixup in communications, our IT admins went ahead and migrated across the existing entire subscriber base for all lists. Thus there is NO need to re-subscribe to any of the lists. If you were doing filtering of mail, you may need to update filters for the new list ID matches. With the new list server, HyperKitty is providing the web interface. Thus if you wish to interact with the lists entire via the browser this is now possible. Note that it requires you to register for an account and set a password, even if you are already a list subscriber. If you mistakenly send to the old lists you should receive an auto-reply about the moved destinations. Note, we had some technical issues on Thursday/Friday, so if you sent mails on those two days they probably will not have reached any lists, and so you may wish to re-send them. With regards, Daniel [1] https://listman.redhat.com/archives/libvirt-announce/2023-October/000650.ht… -- |: 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 :|

3 4