December 2023 - Users - Libvirt List Archives

How to monitor domains in regards steal time and other important metrics (VIR_DOMAIN_STATS_VCPU) ?

by Christian Rohmann

Hey libvirt-users, first allow me to give a little background. We monitor performance metrics of OpenStack Nova VMs using libvirt as hypervisor. We used to run the libvirt prometheus exporter written by zhangjianweibj [1]. This exporter, compared to the one from kumina / tinkoff ([2]) makes use of the DigitalOcean go-libvirt [3], but that should not make much of a difference for my questions. Since the development of that exporter seems to have stalled and we wanted to rework and contribute new features to it, we created a fork [4]. After working trough the various ideas we had and applying them to the code, we proposed the prometheus-community to adopt the exporter [5] to ensure it is maintained and to serve as a reference exporter even. Now to my actual question ... Libvirt exposes per VCPU stats for domains via [6]. I'd like to be able to export those via the exporter. One important metric to me would be things like the steal time (vcpu.<num>.delay), to determine is domains are starting to get cut short or even starve on cpu time. Apparently those metrics are / cannot be expose anymore since the switch to CGroupsV2? Reading [7] or [8] others seem to have run into this. Is this actually still the case, even for more recent kernels? If so, I am wondering if there is an issue being tracked to implement this functionality? How is the steal time reported to the guest if the hypervisor is unable to export this info? Then there are other approaches like vmtop by Digital Ocean [9], which does use info and metrics available via /proc to determine steal time and other vcpu based metrics. So it seems the required data is somewhat available from the kernel? Last but not least I'd like your opinion on what other key metrics are important to monitoring on hypervisors and their guests? Regards Christian [1] https://github.com/zhangjianweibj/prometheus-libvirt-exporter [2] https://github.com/Tinkoff/libvirt-exporter [3] https://github.com/digitalocean/go-libvirt [4] https://github.com/inovex/prometheus-libvirt-exporter [5] https://github.com/prometheus-community/community/issues/50 [6] https://libvirt.org/html/libvirt-libvirt-domain.html#VIR_DOMAIN_STATS_VCPU [7] https://bugzilla.redhat.com/show_bug.cgi?id=2015763 [8] https://bugzilla.redhat.com/show_bug.cgi?id=1796543 [9] https://github.com/digitalocean/vmtop/

11 months, 3 weeks

3
7
0 / 0

Host cpu model from "virsh capabilities" command not matching host physical model

by xtec＠trimaso.com.mx

The host cpu here is intel i5 1135g7 (this is a laptop). Using libvirt 9.0.0 Using "virsh capabilities" command, the //host/cpu/model part reads Broadwell-noTSX-IBRS But there are also the Skylake cpus available, which are newer than broadwell, and thus should better match an intel core 11th generation Why is libvirt outputting an "older processor"?

1 year

2
1
0 / 0

Libvirt permissions using facl instead of groups

by Stephen Lauck

Is there a way to use facl to specifically grant permission to all the files/dirs that libvirt needs instead of using groups? I am automating the install of libvirt and would like to be able to use it without sudo or having to logout/login. I have done a similar thing on a docker install using setfacl but was wondering if someone can point me to the specific kvm/libvirt places I need to grant and the privileges. Thank you for any help! -Stephen

1 year

2
1
0 / 0

Issue with egl-headless on headless server and EGL context not found error

by andrea3000＠gmail.com

Hi, I have a headless server (without a window server running) and I’m trying to create a VM with Intel GVT-g support, where the mediated GPU device is the only graphics device presented to the guest. When I try to launch the VM I get the following error: qemu-system-x86_64: ../src/dispatch_common.c:872: epoxy_get_proc_address: Assertion `0 && "Couldn't find current GLX or EGL context.\n"' failed. Do you know why there is no EGL context? Am I missing some necessary parameter? You can find the domain XML below: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>MacOS Monterey</name> <uuid>91b82c42-f5a2-424f-b45f-714ed7c190de</uuid> <description>MacOS Monterey</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="default.png" os="osx"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-7.2'>hvm</type> <loader readonly='yes' type='pflash'>/mnt/user/system/custom_ovmf/Macinabox_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/91b82c42-f5a2-424f-b45f-714ed7c190de_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='2' threads='1'/> <cache mode='passthrough'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Macinabox Monterey/macos_disk.img'/> <target dev='hdc' bus='sata'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x10'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:7d:24:fd'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <graphics type='egl-headless'> <gl rendernode='/dev/dri/by-path/pci-0000:00:02.0-render'/> </graphics> <audio id='1' type='none'/> <video> <model type='none'/> </video> <hostdev mode='subsystem' type='mdev' managed='no' model='vfio-pci' display='on'> <source> <address uuid='42a87f64-e629-4d69-9672-6bef7162d042'/> </source> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </memballoon> </devices> <qemu:commandline> <qemu:arg value='-usb'/> <qemu:arg value='-device'/> <qemu:arg value='usb-kbd,bus=usb-bus.0'/> <qemu:arg value='-device'/> <qemu:arg value='isa-applesmc,osk=ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc'/> <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> <qemu:arg value='-cpu'/> <qemu:arg value='Penryn,kvm=on,vendor=GenuineIntel,+kvm_pv_unhalt,+kvm_pv_eoi,+hypervisor,+invtsc,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+avx2,+aes,+fma,+bmi1,+bmi2,+xsave,+xsaveopt,+rdrand,check'/> </qemu:commandline> <qemu:override> <qemu:device alias='hostdev0'> <qemu:frontend> <qemu:property name='x-igd-opregion' type='bool' value='true'/> <qemu:property name='romfile' type='string' value='/mnt/user/data/i915dev/i915ovmf.rom'/> <qemu:property name='driver' type='string' value='vfio-pci-nohotplug'/> <qemu:property name='ramfb' type='bool' value='true'/> </qemu:frontend> </qemu:device> </qemu:override> </domain> And the full log output below: 2023-12-27 16:02:06.759+0000: starting up libvirt version: 8.7.0, qemu version: 7.2.0, kernel: 6.1.64-Unraid, hostname: Jarvis LC_ALL=C \ PATH=/bin:/sbin:/usr/bin:/usr/sbin \ HOME='/var/lib/libvirt/qemu/domain-13-MacOS Monterey' \ XDG_DATA_HOME='/var/lib/libvirt/qemu/domain-13-MacOS Monterey/.local/share' \ XDG_CACHE_HOME='/var/lib/libvirt/qemu/domain-13-MacOS Monterey/.cache' \ XDG_CONFIG_HOME='/var/lib/libvirt/qemu/domain-13-MacOS Monterey/.config' \ /usr/local/sbin/qemu \ -name 'guest=MacOS Monterey,debug-threads=on' \ -S \ -object '{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-13-MacOS Monterey/master-key.aes"}' \ -blockdev '{"driver":"file","filename":"/mnt/user/system/custom_ovmf/Macinabox_CODE-pure-efi.fd","node-name":"libvirt-pflash0-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-pflash0-format","read-only":true,"driver":"raw","file":"libvirt-pflash0-storage"}' \ -blockdev '{"driver":"file","filename":"/etc/libvirt/qemu/nvram/91b82c42-f5a2-424f-b45f-714ed7c190de_VARS-pure-efi.fd","node-name":"libvirt-pflash1-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-pflash1-format","read-only":false,"driver":"raw","file":"libvirt-pflash1-storage"}' \ -machine pc-q35-7.2,usb=off,dump-guest-core=off,mem-merge=off,memory-backend=pc.ram,pflash0=libvirt-pflash0-format,pflash1=libvirt-pflash1-format \ -accel kvm \ -cpu host,migratable=on,host-cache-info=on,l3-cache=off \ -m 8192 \ -object '{"qom-type":"memory-backend-ram","id":"pc.ram","size":8589934592}' \ -overcommit mem-lock=off \ -smp 2,sockets=1,dies=1,cores=2,threads=1 \ -uuid 91b82c42-f5a2-424f-b45f-714ed7c190de \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=35,server=on,wait=off \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=utc,driftfix=slew \ -global kvm-pit.lost_tick_policy=delay \ -no-hpet \ -no-shutdown \ -boot strict=on \ -device '{"driver":"pcie-root-port","port":16,"chassis":1,"id":"pci.1","bus":"pcie.0","multifunction":true,"addr":"0x2"}' \ -device '{"driver":"pcie-root-port","port":17,"chassis":2,"id":"pci.2","bus":"pcie.0","addr":"0x2.0x1"}' \ -device '{"driver":"pcie-root-port","port":18,"chassis":3,"id":"pci.3","bus":"pcie.0","addr":"0x2.0x2"}' \ -device '{"driver":"pcie-root-port","port":19,"chassis":4,"id":"pci.4","bus":"pcie.0","addr":"0x2.0x3"}' \ -device '{"driver":"ich9-usb-ehci1","id":"usb","bus":"pcie.0","addr":"0x7.0x7"}' \ -device '{"driver":"ich9-usb-uhci1","masterbus":"usb.0","firstport":0,"bus":"pcie.0","multifunction":true,"addr":"0x7"}' \ -device '{"driver":"ich9-usb-uhci2","masterbus":"usb.0","firstport":2,"bus":"pcie.0","multifunction":true,"addr":"0x7.0x1"}' \ -device '{"driver":"ich9-usb-uhci3","masterbus":"usb.0","firstport":4,"bus":"pcie.0","addr":"0x7.0x2"}' \ -device '{"driver":"virtio-serial-pci","id":"virtio-serial0","bus":"pci.2","addr":"0x0"}' \ -blockdev '{"driver":"file","filename":"/mnt/user/domains/Macinabox Monterey/macos_disk.img","node-name":"libvirt-1-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-1-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-1-storage"}' \ -device '{"driver":"ide-hd","bus":"ide.2","drive":"libvirt-1-format","id":"sata0-0-2","bootindex":1,"write-cache":"on"}' \ -netdev tap,fd=36,id=hostnet0 \ -device '{"driver":"virtio-net","netdev":"hostnet0","id":"net0","mac":"52:54:00:7d:24:fd","bus":"pci.1","addr":"0x0"}' \ -chardev pty,id=charserial0 \ -device '{"driver":"isa-serial","chardev":"charserial0","id":"serial0","index":0}' \ -chardev socket,id=charchannel0,fd=34,server=on,wait=off \ -device '{"driver":"virtserialport","bus":"virtio-serial0.0","nr":1,"chardev":"charchannel0","id":"channel0","name":"org.qemu.guest_agent.0"}' \ -device '{"driver":"usb-tablet","id":"input0","bus":"usb.0","port":"1"}' \ -audiodev '{"id":"audio1","driver":"none"}' \ -vnc 0.0.0.0:0,websocket=5700,audiodev=audio1 \ -k en-us \ -display egl-headless,rendernode=/dev/dri/by-path/pci-0000:00:02.0-render \ -device '{"id":"hostdev0","sysfsdev":"/sys/bus/mdev/devices/42a87f64-e629-4d69-9672-6bef7162d042","display":"on","bus":"pci.4","addr":"0x0","x-igd-opregion":true,"romfile":"/mnt/user/data/i915dev/i915ovmf.rom","driver":"vfio-pci-nohotplug","ramfb":true}' \ -device '{"driver":"virtio-balloon-pci","id":"balloon0","bus":"pci.3","addr":"0x0"}' \ -usb \ -device usb-kbd,bus=usb-bus.0 \ -device 'isa-applesmc,osk=ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc' \ -smbios type=2 \ -cpu Penryn,kvm=on,vendor=GenuineIntel,+kvm_pv_unhalt,+kvm_pv_eoi,+hypervisor,+invtsc,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+avx2,+aes,+fma,+bmi1,+bmi2,+xsave,+xsaveopt,+rdrand,check \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on char device redirected to /dev/pts/0 (label charserial0) qemu-system-x86_64: ../src/dispatch_common.c:872: epoxy_get_proc_address: Assertion `0 && "Couldn't find current GLX or EGL context.\n"' failed. 2023-12-27 16:02:23.109+0000: shutting down, reason=crashed Thank you Regards, Andrea

1 year, 1 month

1
0
0 / 0

Status of Microsoft Hyper-V driver

by Mateusz Loskot

Hi, This is my first post to this forum, hello everyone! I come here with zero experience with libvirt which I have just started learning [1] and my current interest is about the Hyper-V support and the driver [2] status. Could anyone point me where to look in order to learn about the currently available Hyper-V capabilities in libvirt? Are there any libvirt API usage examples targeting Hyper-V? The table at the bottom of the driver page [2] lists Windows Server 2012, 2016 and 2019 only. What Windows Server 2022, is this just an omission in the docs or it specifically is not supported? [1] https://gist.github.com/mloskot/63f4535e5850e74cef542121dfd2dca2 [2] https://libvirt.org/drvhyperv.html Best regards, -- Mateusz Loskot, http://mateusz.loskot.net

1 year, 2 months

2
2
0 / 0

assigning VM to a VLAN on a trunk bridge that exists on LACP bond - how to

by hakan_duran＠hotmail.com

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 year, 2 months

1
1
0 / 0

re: assigning VM to a VLAN on a trunk bridge that exists on LACP bond - how to

by Hakan E. Duran

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 year, 2 months

1
0
0 / 0

How can I have a list of interfaces in virt-manager network config

by Marc Haber

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

1 year, 2 months

3
5
0 / 0

Can't connect to libvirt

by list-libvirt-users＠aliases.systohc.net

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

1 year, 2 months

2
1
0 / 0

Re: Shared memory usage

by Martin Kletzander

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 year, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Users December 2023