- Users - libvirt List Archives

SR-IOV pool with static MAC address and vlan
by Paul B. Henson 03 Apr '23

03 Apr '23

I'm planning to set up a libvirt/kvm system using a card with SR-IOV support. I'd like to use the vf pool option rather than statically assigning a vf to each vm. However, I'd also like each vm to have a static MAC address and I have multiple VLANs they will be on. I found in the documentation a syntax for specifying a MAC and a vlan when the vf is statically assigned, but I don't see anything in the documentation about doing so when using a vf pool? Did I miss something? Is it possible to do so? If not, is there some other way to handle MAC addresses and vlans with a vf pool, or if you need those are you stuck with static assignment? Thanks much...

2 2

About libvirt domain dump state and persistent state
by Shen, Tao 30 Mar '23

30 Mar '23

Hi all, I use libvirt-go in my agent to attach rbd volumes. I ofen suffer the issue of incosistent of domain dump xml and domain persistent xml file. For example, when I try to attach volume, the the domain by “virConnectListAllDomains” api from libvirt tell me the vdf or 0x0a is empty, but when attach it with the vdf device or 0x0a address, qemu return the error duplicated with vdf or PCI address are double used: 2021-09-28T16:00:03.816682107-07:00 stderr F I0928 23:00:03.816558 1 cephvolume.go:73] attach disk &{XMLName:{Space: Local:} Device:disk RawIO: SGIO: Snapshot: Model: Driver:0xc00073b420 Auth:0xc000f49e40 Source:0xc000159860 BackingStore:<nil> Geometry:<nil> BlockIO:<nil> Mirror:<nil> Target:0xc000a58b40 IOTune:0xc00019b970 ReadOnly:<nil> Shareable:<nil> Transient:<nil> Serial:pvc-33003998-6624-4ac9-a923-d94f9401abdf WWN: Vendor: Product: Encryption:<nil> Boot:<nil> Alias:<nil> Address:0xc001420b40} error: virError(Code=27, Domain=20, Message='XML error: target 'vdf' duplicated for disk sources 'volume-0aab375c-1858-4f09-b276-ea297cd29a3d' and 'volume-63ef92c4-a027-476c-a2de-9fcf501dd4de'') I0330 00:28:55.070331 1 cephvolume.go:73] attach disk &{XMLName:{Space: Local:} Device:disk RawIO: SGIO: Snapshot: Model: Driver:0xc000024380 Auth:0xc006a51600 Source:0xc000640cd0 BackingStore:<nil> Geometry:<nil> BlockIO:<nil> Mirror:<nil> Target:0xc00342db80 IOTune:0xc005071c30 ReadOnly:<nil> Shareable:<nil> Transient:<nil> Serial:pvc-39c80157-0862-433c-a1ec-49475db818cf WWN: Vendor: Product: Encryption:<nil> Boot:<nil> Alias:<nil> Address:0xc000f5e240} error: virError(Code=27, Domain=20, Message='XML error: Attempted double use of PCI Address 0000:00:0a.0') In first case of “target 'vdf' duplicated” , I find the volume is in the dump xml by “virsh dumpxml” but not in the persistent xml at /etc/libvirt/qemu/xxx.xml or “virsh edit”. But the second case of “double use of PCI Address” I found the volume is on the persistent xml but not int the duml xml. I think there is a middle state that qemu try to attach or detach but not finished. But what is the api to get the different domain state except “virConnectListAllDomains”? The reversed case is that when I try to detach volume, the domain tell me the volume is allocated at vde, but I detach the volume with vde, it also return the error “vde not found”: I0330 00:38:54.615254 1 cephvolume.go:227] detach disk &{XMLName:{Space: Local:disk} Device:disk RawIO: SGIO: Snapshot: Model: Driver:0xc000736540 Auth:0xc0027b68a0 Source:0xc000641040 BackingStore:<nil> Geometry:<nil> BlockIO:<nil> Mirror:<nil> Target:0xc004557640 IOTune:0xc0006e4370 ReadOnly:<nil> Shareable:<nil> Transient:<nil> Serial:pvc-febae406-15ad-4d05-9c93-b2d09c197840 WWN: Vendor: Product: Encryption:<nil> Boot:<nil> Alias:<nil> Address:0xc00709cba0} error: virError(Code=9, Domain=10, Message='operation failed: disk vde not found') In this case, I found the volume is not in dump but in the persistent. All my volume api are use persistent operation. So I want to know 1. What is the state return by “virConnectListAllDomains” ? 2. What is the detail of state and how the state transition of qemu/libvirt? 3. Any way in libvirt api to get the different state of domain? Thanks, Tao

1 0

Option Flags
by Simon Fairweather 23 Mar '23

23 Mar '23

Hi Are the flags documented? can this function be used to specify same as virsh undefine --nvram "name of VM" libvirt_domain_undefine_flags($res, $flags) [Since version (null)] Function is used to undefine(with flags) the domain identified by it's resource. *@res [resource]*: libvirt domain resource, e.g. from libvirt_domain_lookup_by_*() *@flags [int]*: optional flags *Returns*: : TRUE for success, FALSE on error

3 3

virsh domifaddr --domain domname --source {lease, arp} not showing results with ipv6
by Natxo Asenjo 21 Mar '23

21 Mar '23

hi, I have configured a routed network on my laptop with a ipv6 subnet and dnsmasq is handing out ipv6 addresses to my vms and it works really wel, but finding out which ips have been used is not as easy as with ipv4. [root@lenovo ~]# virsh domifaddr --domain wec --source lease Name MAC address Protocol Address ------------------------------------------------------------------------------- [root@lenovo ~]# virsh domifaddr --domain wec --source arp Name MAC address Protocol Address ------------------------------------------------------------------------------- When using a ipv4 network, this works: root@lenovo ~]# virsh domifaddr --domain evenng --source arp Name MAC address Protocol Address ------------------------------------------------------------------------------- vnet2 52:54:00:4c:83:98 ipv4 192.168.122.229/0 [root@lenovo ~]# virsh domifaddr --domain evenng --source lease Name MAC address Protocol Address ------------------------------------------------------------------------------- vnet2 52:54:00:4c:83:98 ipv4 192.168.122.229/24 I can obviously look into the leases file and find out the address, but it would be nice to be able to use the virt tooling. This is on a fedora 37 running qemu-kvm-7.0.0-14.fc37.x86_64 and dnsmasq-2.89-1.fc37.x86_64, everything intalled from the fedora repositories. -- -- Groeten, natxo

2 4

Upgrade machine type during migration
by Michael Schwartzkopff 21 Mar '23

21 Mar '23

Hi, I have an old system. The guest there is defined with: <os> <type arch='x86_64' machine='pc-q35-rhel8.2.0'>hvm</type> </os> When I try to migrate this guest to a new system I get the error: error: internal error: unable to execute QEMU command 'blockdev-add': Failed to connect socket: Permission denied On the new host I see the log entries: libvirtd[22411]: Domain id=18 name='test02' uuid=9bad33a8-d18e-4c68-bdbe-dad34142dc22 is tainted: deprecated-config (machine type 'pc-q35-rhel8.2.0') systemd-machined[9980]: New machine qemu-18-test02. systemd[1]: Started Virtual Machine qemu-18-test02. systemd-networkd[3914]: vnet20: Link DOWN systemd-networkd[3914]: vnet20: Lost carrier kernel: br1: port 3(vnet20) entered disabled state kernel: device vnet20 left promiscuous mode kernel: br1: port 3(vnet20) entered disabled state systemd[1]: machine-qemu\x2d18\x2dtest02.scope: Deactivated successfully. systemd-machined[9980]: Machine qemu-18-test02 terminated. libvirtd[22411]: migration successfully aborted It seems there is no possible combination of machine types that is compatible for both hosts. The old host only can start rhel8.2 guests, the new one only rhel9.0. Is there a possibility to change the machine type during a migration? Is such a migration possible? Or do I have so shut down the guest? Michael Schwartzkopff

4 3

virNetSocketReadWire
by Simon Fairweather 07 Mar '23

07 Mar '23

What are the standard reasons for this to fail? virNetSocketReadWire:1791 : End of file while reading data: Input/output error

2 2

Unable to create a VM in a specific network namespace using the Domain XML descriptions and API for libvirt + QEMU over KVM
by Roberto Jacob Da Silva 28 Feb '23

28 Feb '23

I have a system where I spawn a single libvirt daemon process in the default network namespace. Once the daemon is running, I create and start VMs using the virDomainDefineXML API (defines a VM or "domain" but does not boot it) followed by the virDomainCreate API (boot the VM). Now, I am trying to create these VMs in generic network namespaces provided by the user e.g., /var/run/netns/<my-network-namespace>. While searching the libvirt documentation (i.e., https://libvirt.org/formatdomain.html) I couldn't find any configuration options, which would support this network namespace specification via the domain XML APIs. Is there any way to accomplish this with the domain XML APIs? If not, what's the recommended approach to allow a libvirt client to request the libvirt server to create and boot VMs in distinct network namespaces?

1 0

Re: ACLs problem on /dev/kvm
by Michal Prívozník 28 Feb '23

28 Feb '23

[Please keep the list CCed for benefit of the community] On 2/27/23 16:58, Sánta, Márton (ext) wrote: > Dear Michal, > > Thank you for your quick help, this worked for me but I would like to use the latest version if it is possible. Do you know how to upgrade my libvirt version in yocto? I tried to use devtool to upgrade v9.0.0 but there were some issues during the process and I had to do a lot of things manually (downloading the approprieta sources as during the update, the v8.1.0 sources were downloaded etc.) and I do not see what problems can it cause later on. What do you suggest? Hey, unfortunately I have zero experience with yocto. I believe you need to contact whoever maintains libvirt there and point them to the fix I mention in my previous reply. Surely they have a way to backport patches. Michal

1 0

help regarding gsoc 2023
by Kshitiz Mhto 24 Feb '23

24 Feb '23

hello, i am 1st year student with good understanding of C programming along with pythan and java. i would love to contribute to project "libvirt" and interested in gsoc 2023 regardung the project [Metadata support for all object schemas -- Suggested by: Daniel Berrange]. could anyone help on this?

1 0

how to use exec:cat > /dev/null using libvirt
by Jiatong Shen 24 Feb '23

24 Feb '23

Hello community, I am trying to inspect a migration failure using the steps described here ( https://wiki.qemu.org/Features/Migration/Troubleshooting#:~:text=on%20graph….) In the fourth step, it suggests using migrate 'exec:cat > /dev/null' to try dumping vm state on the source node. Since the virtual machine is controlled by libvirt, I suppose I could using the following command, virsh qemu-monitor-command --hmp <instance-id> 'migrate "exec:cat > /dev/nulll" but it failed with 2023-02-24T02:56:07.347307Z qemu-system-x86_64: Unable to write to command: Broken pipe So my question is how to use this command using libvirt? Thank you very much for the help. -- Best Regards, Jiatong Shen

1 0