- Users - libvirt List Archives

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

ACLs problem on /dev/kvm
by Sánta, Márton (ext) 22 Feb '23

22 Feb '23

Dear All, I have started to work with libvirt a few weeks ago, but I have some problem with starting a virtual machine. Currently, I am using an embedded arm64 device with a Linux built with Yocto. I managed to install lbvirt 8.1.0 in the image and I have a qemu user and qemu and kvm groups in the system. I am using KVM hypervisor and I did the configuration in the qemu.conf and libvirtd.conf files, enabled all the sockets and services in the system. The xml based definition of the virtual machine is simple, but when I try to start it I get the error message: Failed to start domain 'XYZ' and Unable to set ACLs on /dev/kvm: Invalid argument. I cannot set ACLs on the /dev/kvm (owner is root, group is kvm but I have also tried to set it root:root) with the setfacl command, but I gave rwx access to user, group and others as well so everybody can use the device. I also uncommented the relevant lines in the qemu.conf file (cgroup_controllers = ... and cgroup_device_acl = ...) and I also found that devices controller is already mounted at /sys/fs/cgroup/devices. Can anybody help me with this issue? Did Anybody have similar problem? I can start a virtual machine with qemu-system-aarch64, but I would like to use the libvirt library to manage the machines. Thank you in advance for an early reply. 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.

2 1

there is no PCIe device after command "virsh nodedev-list"
by Martin Bayern 14 Feb '23

14 Feb '23

Hello, I don't know if this is the right email list for this question, let me try. I experienced a problem when I want to assign PCIe VF to my VMs, I can use "lspci" to list the VF PCIe, even PF PCIe, but the command " virsh nodedev-list" doesn't print any PCIe bus device. I tried using "virsh edit --domain " command and added the PCIe bus to the XML file, but when I start the VM, the error message shows an internal error, there is an invalid link to the device. Meanwhile, I use virt-manager to see if I can add a PCIe host device, but the host device shows "no device available". my system is ARM64 based Nvidia platform, I have enabled IOMMU in the kernel. do you know how can I figure out the root cause? is this the ARM64 kernel issue or something else?? I posted this issue also in Nvidia forum: https://forums.developer.nvidia.com/t/nvidia-orin-pcie-device-there-is-no-p… thanks so much for your suggestions. Martin

1 0