- Users - libvirt List Archives

libvirt error - "cannot set CPU affinity"
by Dipanjan Das 01 Feb '23

01 Feb '23

Hello, I am getting the following error message when trying to run a VM with the emulatorpin cpuset set to a value - "cannot set CPU affinity on process 78: Invalid argument". Note that removing the emulatorpin leads to the VM running successfully. The core that I am setting for the emulatorpin cpuset is present on the system and is not in the isolcpus set of the host. Any suggestions on what could be the problem? Any pointers to how to debug the issue would help greatly too. Some further details if they help - I am using kubevirt (KubeVirt.io <http://kubevirt.io/>) which uses libvirt to manage VM instances in a kubernetes environment. The libvirt version being used is 8.0.0. Thanks, Dipanjan Das

2 3

USB Device Redirection | Change Access For Mount
by Stefanie Leisestreichler 16 Jan '23

16 Jan '23

Hi. I am using kvm/qemu to redirect my mobile phone in a Virtual Machine (via virt-viewer). The mount works automatically but unfortunately the permission to access the files (i.e. photos) is limited to the mounting user only. I want to grant access to other users also. How can I archive this? Thanks, Steffi

1 0

Libvirt dnsmasq oddity
by Charles Curley 16 Jan '23

16 Jan '23

I seem to have hit an oddity in how dnsmasq operates for libvirt. I have two host machines each with several guests. One of those is also the local samba server. Guests on the non-samba server can resolve the samba server's host name correctly, so far without fail. Guests on the samba server sometimes get the correct IP address for the samba server, and other times get an IP address for the samba server of 127.0.1.1. That is the IP address provided in the host's /etc/hosts. Similarly for amanda and hosts. I have a workaround of hard coding the IP address in the fstab entry, but that's tacky. Is there a better way to handle this? One possible way: non-virtual machines use a bind9 server. dnsmasq has an option, --no-hosts, to inhibit reading the hostnames in /etc/hosts. How do I feed that to dnsmasq? Thank you. root@hawk:~# cat /etc/debian_version 11.6 root@hawk:~# lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye root@hawk:~# pre libvirt dnsmasq qemu dnsmasq-base 2.85-1 amd64 gir1.2-libvirt-glib-1.0 3.0.0-1 amd64 ipxe-qemu 1.0.0+git-20190125.36a4c85-5.1 all libvirt0 7.0.0-3 amd64 libvirt-clients 7.0.0-3 amd64 libvirt-daemon 7.0.0-3 amd64 libvirt-daemon-config-network 7.0.0-3 all libvirt-daemon-config-nwfilter 7.0.0-3 all libvirt-daemon-driver-lxc 7.0.0-3 amd64 libvirt-daemon-driver-qemu 7.0.0-3 amd64 libvirt-daemon-driver-vbox 7.0.0-3 amd64 libvirt-daemon-driver-xen 7.0.0-3 amd64 libvirt-daemon-system 7.0.0-3 amd64 libvirt-daemon-system-systemd 7.0.0-3 all libvirt-glib-1.0-0 3.0.0-1 amd64 python3-libvirt 7.0.0-2 amd64 qemu 1:5.2+dfsg-11+deb11u2 amd64 qemu-system-common 1:5.2+dfsg-11+deb11u2 amd64 qemu-system-data 1:5.2+dfsg-11+deb11u2 all qemu-system-gui 1:5.2+dfsg-11+deb11u2 amd64 qemu-system-x86 1:5.2+dfsg-11+deb11u2 amd64 qemu-utils 1:5.2+dfsg-11+deb11u2 amd64 root@hawk:~# -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/

1 0

virConnectGetDomainCapabilities
by Simon Fairweather 14 Jan '23

14 Jan '23

Hi Is there a php api version for this? Regards Smon

2 2

question about virtio related options: ats=on and iommu=on
by Yalan Zhang 09 Jan '23

09 Jan '23

Hi, I have a question about the virtio related options, could someone please help to confirm? In my understanding, the ats='on' should depend on the "iommu=on", but I'm not sure about it. Please check the details below. Thank you! Details: 1. set vm with intel iommu device, and enable iommu for virtio filesystem device: # virsh dumpxml rhel --xpath //iommu <iommu model="intel"> <driver intremap="on" caching_mode="on" iotlb="on"/> </iommu> Set iommu="on" ats="on" for virtio filesystem device: # virsh dumpxml rhel --xpath //filesystem <filesystem type="mount" accessmode="passthrough"> <driver type="virtiofs" queue="512" iommu="on" ats="on"/> <binary path="/usr/libexec/virtiofsd" xattr="on"> <cache mode="none"/> </binary> <source dir="/path1"/> <target dir="mount_tag1"/> <address type="pci" domain="0x0000" bus="0x04" slot="0x00" function="0x0"/> </filesystem> 2. failed to start the vm since "iommu_platform=true is not supported by the device" # virsh start rhel error: Failed to start domain 'rhel' error: internal error: qemu unexpectedly closed the monitor: 2023-01-09T03:48:03.198629Z qemu-kvm: -device {"driver":"vhost-user-fs-pci","iommu_platform":true,"ats":true,"id":"fs0","chardev":"chr-vu-fs0","queue-size":512,"tag":"mount_tag1","bus":"pci.4","addr":"0x0"}: iommu_platform=true is not supported by the device 3. update the xml to be with only ats="on", vm can start successfully, which is not expected. # virsh dumpxml rhel --xpath //filesystem <filesystem type="mount" accessmode="passthrough"> <driver type="virtiofs" queue="512" ats="on"/> <binary path="/usr/libexec/virtiofsd" xattr="on"> <cache mode="none"/> </binary> <source dir="/path1"/> <target dir="mount_tag1"/> <alias name="fs0"/> <address type="pci" domain="0x0000" bus="0x04" slot="0x00" function="0x0"/> </filesystem> the qemu cmd line: -chardev socket,id=chr-vu-fs0,path=/var/lib/libvirt/qemu/domain-5-rhel/fs0-fs.sock \ -device '{"driver":"vhost-user-fs-pci","ats":true,"id":"fs0","chardev":"chr-vu-fs0","queue-size":512,"tag":"mount_tag1","bus":"pci.4","addr":"0x0"}' Refer to libvirt.org: QEMU's virtio devices have some attributes related to the virtio transport under the driver element: The iommu attribute enables the use of emulated IOMMU by the device. The attribute ats controls the Address Translation Service support for PCIe devices. This is needed to make use of IOTLB support (see IOMMU devices). Possible values are on or off. In my understanding, the ats='on' should depend on the iommu='on', so if the device does not support iommu, it should not support ats, eigher. I'm not sure if the understanding is correct. Could someone please help to confirm it? Thank you! Yalan

2 1

Public IPv6 Bridges
by André Malm 08 Jan '23

08 Jan '23

I'm having trouble getting IPv6 to work for my KVM/qemu guests. I have two bridges setup, one routed (external, non libvirt) bridge for public dedicated ipv4 + ipv6 which works for both protocols. Then I have a libvirt nat bridge (with the routed bridge as parent) with a nated ipv4 (that works) and I also want a public ipv6. I'm able to transmit udp packets out but I never get any response. Looking at tcpdump there are incoming neighbor solicitations that get unanswered and don't get forwarded to the guest. Do I need to set something special up for this to work? Ubuntu 22.04 / Libvirt 8.0.0 The routed bridge (pubBr) has ipv6 2001:x:x:7d8e:: - My nat bridge config below: <network> <name>natbr</name> <bridge name="natbr" /> <forward mode='nat' dev='pubBr'> <nat> <port start='8000' end='30000'/> </nat> </forward> <ip address="10.1.1.1" netmask="255.255.0.0"> <dhcp> <range start='10.1.1.2' end='10.1.1.255'/> </dhcp> </ip> <ip family="ipv6" address="2001:x:x:7d8e::1" prefix="64"> <dhcp> <host name="test" ip="2001:x:x:7d8e:a01:2ff::"/> </dhcp> </ip> </network> Thanks!

1 0

libvirt_connect_get_nic_models
by Simon Fairweather 02 Jan '23

02 Jan '23

Hi Can you confirm that I source get an array of these when running this api call, currently I just get a return of false root@computenode:/mnt/testpool# qemu -nic model=help Supported NIC models: e1000 e1000-82544gc e1000-82545em e1000e i82550 i82551 i82557a i82557b i82557c i82558a i82558b i82559a i82559b i82559c i82559er i82562 i82801 ne2k_pci pcnet rtl8139 tulip virtio-net-pci virtio-net-pci-non-transitional virtio-net-pci-transitional vmxnet3 function domain_get_nic_models($arch = 'x86_64') { $tmp = libvirt_connect_get_nic_models($this->conn, $arch) ; return ($tmp) ? $tmp : $this->_set_last_error(); }

2 2

Snapshots of EFI VMs
by Simon Fairweather 31 Dec '22

31 Dec '22

Is there a timeline to fully support create/remove and revert for these VMs?

1 0

how to add LD_PRELOAD in the xml
by Marc 31 Dec '22

31 Dec '22

How should I add LD_PRELOAD to domain xml. I guess within: <qemu:commandline> <qemu:arg value='env=LD_PRELOAD=/usr/lib64/libtcmalloc.so'/> </qemu:commandline> but this is generating syntax errors.

2 2

Fwd: Need help
by Gk Gk 22 Dec '22

22 Dec '22

FYI.... ---------- Forwarded message --------- From: Gk Gk <ygk.kmr(a)gmail.com> Date: Wed, Dec 21, 2022 at 9:46 PM Subject: Re: Need help To: Daniel P. Berrangé <berrange(a)redhat.com> I have just created a new vm and rechecked the disk stats. This time around too, they seem to be different as shown below: >From libvirt python library: --- disk_name=sda read_req=10501,read_bytes=263819776,write_req=1933,write_bytes=82269184 --- So the write_bytes from above amounted to 78 MB approx. But from within the vm : --- root@sample2:~# iostat -p sda -h Linux 4.15.0-101-generic (sample2) 12/21/2022 _x86_64_ (1 CPU) avg-cpu: %user %nice %system %iowait %steal %idle 1.9% 0.0% 1.3% 0.4% 0.0% 96.4% Device tps kB_read/s kB_wrtn/s kB_read kB_wrtn sda 40.45 643.6k 21.2M 217.5M 7.2G sda1 40.04 637.6k 21.2M 215.5M 7.2G ---- 7.2 G is far from 78 MB. Am I doing wrong anywhere ? Btw, I did not reboot the new vm this time On Wed, Dec 21, 2022 at 9:30 PM Daniel P. Berrangé <berrange(a)redhat.com> wrote: > On Wed, Dec 21, 2022 at 09:26:14PM +0530, Gk Gk wrote: > > Thanks Daniel for the response. > > > > I am wondering what exactly is the difference in the process for a soft > and > > hard reboot in the context of a kvm guest ? Can you throw some light here > > please ? > > KVM will always do a soft reboot, where QEMU keeps running. > > > 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 :| > >

1 0