- Users - libvirt List Archives

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