December 2022 - Users - libvirt List Archives

Libvirt
by Gk Gk 26 Oct '23

26 Oct '23

Hi All, I am trying to collect memory, disk and network stats for a VM on kvm host. It seems that the statistics are not matching what the OS inside the VM is reporting. Why is this discrepancy ? Is this a known bug of libvirt ? Also I heard that libvirt shows cumulative figures for these measures ever since the VM was created. Also I tested by creating a new vm and comparing the stats without a reboot . Even in this case, the stats dont agree. Can someone help me here please ? Thanks Kumar

2 5

WinServer2016 guest no mouse in VirtManager
by John McInnes 03 Feb '23

03 Feb '23

Hi! I recently converted several Windows Server VMs from HyperV to libvirt/KVM. The host is running openSUSE Leap 15.3. I used virt-v2v and I installed virtio drivers on all of them and it all went well - except for one VM. The mouse does not work for this VM in VirtualMachineManager. There is no cursor and no response. There are no issues showing in Windows Device Manager. The mouse shows up as a PS/2 mouse. Interestingly if I RDP into this VM using Microsoft Remote Desktop the mouse works fine. Any ideas? ---- John McInnes jmcinnes /\T svt.org

1 1

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 30 Dec '22

30 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 30 Dec '22

30 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

Fwd: Need help
by Gk Gk 22 Dec '22

22 Dec '22

For larger reach....... ---------- Forwarded message --------- From: Gk Gk <ygk.kmr(a)gmail.com> Date: Thu, Dec 22, 2022 at 8:35 AM Subject: Re: Need help To: Daniel P. Berrangé <berrange(a)redhat.com> Hi Daniel, Did you get a chance to check this out ? Please let me know.... On Wednesday, December 21, 2022, Gk Gk <ygk.kmr(a)gmail.com> wrote: > 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

Need help
by Gk Gk 21 Dec '22

21 Dec '22

Hi All, I am trying to get guest VM's disk statistics using a libvirt python library as follows: --- raw_xml = domain.XMLDesc(0) for disk in doc.getElementsByTagName('disk'): disk_data = disk.getElementsByTagName('target') --- The above code is yielding the following stats for two disks inside the VM: -- disk_name=sda read_req=34137,read_bytes=445358592,write_req=2405970,write_bytes=24943391744 disk_name=sdb read_req=34357,read_bytes=450754048,write_req=2405984,write_bytes=24943465472 --- The write_bytes divided by 1024 yields 24358853 kB. But when I compare the above statistics from the iostat data shown from inside the VM, I see a stark difference between the two results as shown below: --- root@sample:~# iostat Linux 4.15.0-101-generic (sample) 12/21/2022 _x86_64_ (1 CPU) avg-cpu: %user %nice %system %iowait %steal %idle 0.27 0.00 0.03 0.02 0.01 99.68 Device tps kB_read/s kB_wrtn/s kB_read kB_wrtn sda 0.24 0.04 11.87 400052 121844120 sdb 0.00 0.00 1.19 5269 12223752 ---- Why is there a huge difference in the number of bytes read and written for the two disks as reported by libvirt ? Please explain. Thanks Kumar

2 1

[Question] Which qcow2 options could be inherited to snapshot/blockcopy?
by Meina Li 20 Dec '22

20 Dec '22

Hi, I'm trying to find out which qcow2 options could be inherited to snapshot/blockcopy and then test them. >From https://github.com/qemu/qemu/blob/master/qapi/block-core.json#L4720 we can know all the qcow2 options. As far as I know, size, cluster_size and extended-l2 have already been implemented. So I'm curious that: 1) What are the current status and future plans of other options? Like compat option. 2) Also whether the vol-clone can cover all options? Thank you very much. And please help to correct me if I have something wrong. Best Regards, Meina Li

3 6

Failed to connect socket to '/var/run/libvirt/virtnetworkd-sock': No such file or directory
by 陈新隆 20 Dec '22

20 Dec '22

Hi team, i'm trying to hotplug an interface to guest, after execute the command below I got an error : ``` virsh attach-interface --domain 1 --type network --source net1 --model virtio-non-transitional --target /sys/devices/virtual/net/net1/tap603053 --mac ac:de:48:77:a2:32 --config --live error: Failed to attach interface error: Failed to connect socket to '/var/run/libvirt/virtnetworkd-sock': No such file or directory ``` According to https://libvirt.org/daemons.html there's two arch of daemon which is "monolithic" and "modular" , so I was wondering if I connect to the monolithic daemon (libvirtd) to attach the interface should works. Then I execute the command below : ``` bash-4.4# virsh -c qemu:///system?socket=/var/run/libvirt/libvirt-sock attach-interface --domain 1 --type network --source net1 --model virtio-non-transitional --target /sys/devices/virtual/net/net1/tap603053 --mac ac:de:48:77:a2:32 --config --live Authorization not available. Check if polkit service is running or see debug message for more information. error: Failed to attach interface error: Failed to connect socket to '/var/run/libvirt/virtnetworkd-sock': No such file or directory ``` Still, I got the same error. My question is : 1. How should I hotplug/unplug an interface without virtnetworkd ? 2. Am I right about the guess of "If I use monolithic daemon then I can hotplug/unplug an interface without virtnetworkd ?

1 0

Testing DKIM handling
by dberrange＠yahoo.com 16 Dec '22

16 Dec '22

Testing DKIM handling RH mail servers

4 9

Global option to configure tb-cache size for tcg feature
by Yatin Karel 16 Dec '22

16 Dec '22

Hi Team, In OpenStack Upstream CI as part of testing we have to create multiple guest vms together on a 8GB VM(no nested-virt support) so we have to use qemu emulation. But with Qemu>=5 'tb-cache' size has increased from 32MiB to 1GiB and due to this we cannot run multiple guest vms together as we have limited resources in CI. We tried to use some swap together but that too didn't helped much as it get's too slow. Thanks Libvirt-8.0.0 now allows to configure tcg feature as below in instance domain.xml:- <features> <tcg> <tb-cache unit='KiB'>32768</tb-cache> </tcg> </features> Is there some global option available in libvirt/qemu which we can use instead of changing each and every xml so we can avoid code changes in nova code[1] for just the CI use case? [1] https://bugs.launchpad.net/nova/+bug/1949606 PS: Please keep me in CC for responses as I am not subscribed to the mailing list. Thanks and Regards Yatin Karel

1 0

qemu flags on libvirt attach-device
by Miguel Ping 13 Dec '22

13 Dec '22

Hello, Is it possible to supply additional flags to libvirt attach-device, similar to libvirt qemu passthrough ( https://libvirt.org/kbase/qemu-passthrough-security.html#xml-document-addit… The passthrough appears to work only for domain creation. I'm particularly interested in the "reconnect-delay" param for nbd based disks. Thanks

1 0

Attach NBD device with qemu flags
by Miguel Ping 12 Dec '22

12 Dec '22

Is there a way to attach an nbd device via eg: virsh attach-device, and provide custom qemu flags? I'm particularly interested in the flag "reconnect-delay". I'm fine with using a language binding (eg: C, Java) for this. Thanks

1 0

Re: Predictable and consistent net interface naming in guests
by Julia Suvorova 12 Dec '22

12 Dec '22

On Thu, Nov 3, 2022 at 9:26 AM Amnon Ilan <ailan(a)redhat.com> wrote: > > > > On Thu, Nov 3, 2022 at 12:13 AM Amnon Ilan <ailan(a)redhat.com> wrote: >> >> >> >> On Wed, Nov 2, 2022 at 6:47 PM Laine Stump <laine(a)redhat.com> wrote: >>> >>> On 11/2/22 11:58 AM, Igor Mammedov wrote: >>> > On Wed, 2 Nov 2022 15:20:39 +0000 >>> > Daniel P. Berrangé <berrange(a)redhat.com> wrote: >>> > >>> >> On Wed, Nov 02, 2022 at 04:08:43PM +0100, Igor Mammedov wrote: >>> >>> On Wed, 2 Nov 2022 10:43:10 -0400 >>> >>> Laine Stump <laine(a)redhat.com> wrote: >>> >>> >>> >>>> On 11/1/22 7:46 AM, Igor Mammedov wrote: >>> >>>>> On Mon, 31 Oct 2022 14:48:54 +0000 >>> >>>>> Daniel P. Berrangé <berrange(a)redhat.com> wrote: >>> >>>>> >>> >>>>>> On Mon, Oct 31, 2022 at 04:32:27PM +0200, Edward Haas wrote: >>> >>>>>>> Hi Igor and Laine, >>> >>>>>>> >>> >>>>>>> I would like to revive a 2 years old discussion [1] about consistent network >>> >>>>>>> interfaces in the guest. >>> >>>>>>> >>> >>>>>>> That discussion mentioned that a guest PCI address may change in two cases: >>> >>>>>>> - The PCI topology changes. >>> >>>>>>> - The machine type changes. >>> >>>>>>> >>> >>>>>>> Usually, the machine type is not expected to change, especially if one >>> >>>>>>> wants to allow migrations between nodes. >>> >>>>>>> I would hope to argue this should not be problematic in practice, because >>> >>>>>>> guest images would be made per a specific machine type. >>> >>>>>>> >>> >>>>>>> Regarding the PCI topology, I am not sure I understand what changes >>> >>>>>>> need to occur to the domxml for a defined guest PCI address to change. >>> >>>>>>> The only think that I can think of is a scenario where hotplug/unplug is >>> >>>>>>> used, >>> >>>>>>> but even then I would expect existing devices to preserve their PCI address >>> >>>>>>> and the plug/unplug device to have a reserved address managed by the one >>> >>>>>>> acting on it (the management system). >>> >>>>>>> >>> >>>>>>> Could you please help clarify in which scenarios the PCI topology can cause >>> >>>>>>> a mess to the naming of interfaces in the guest? >>> >>>>>>> >>> >>>>>>> Are there any plans to add the acpi_index support? >>> >>>>>> >>> >>>>>> This was implemented a year & a half ago >>> >>>>>> >>> >>>>>> https://libvirt.org/formatdomain.html#network-interfaces >>> >>>>>> >>> >>>>>> though due to QEMU limitations this only works for the old >>> >>>>>> i440fx chipset, not Q35 yet. >>> >>>>> >>> >>>>> Q35 should work partially too. In its case acpi-index support >>> >>>>> is limited to hotplug enabled root-ports and PCIe-PCI bridges. >>> >>>>> One also has to enable ACPI PCI hotplug (it's enled by default >>> >>>>> on recent machine types) for it to work (i.e.it's not supported >>> >>>>> in native PCIe hotplug mode). >>> >>>>> >>> >>>>> So if mgmt can put nics on root-ports/bridges, then acpi-index >>> >>>>> should just work on Q35 as well. >>> >>>> >>> >>>> With only a few exceptions (e.g. the first ich9 audio device, which is >>> >>>> placed directly on the root bus at 00:1B.0 because that is where the >>> >>>> ich9 audio device is located on actual Q35 hardware), libvirt will >>> >>>> automatically put all PCI devices (including network interfaces) on a >>> >>>> pcie-root-port. >>> >>>> >>> >>>> After seeing reports that "acpi index doesn't work with Q35 >>> >>>> machinetypes" I just assumed that was correct and didn't try it. But >>> >>>> after seeing the "should work partially" statement above, I tried it >>> >>>> just now and an <interface> of a Q35 guest that had its PCI address >>> >>>> auto-assigned by libvirt (and so was placed on a pcie-root-port)m and >>> >>>> had <acpi index='4'/> was given the name "eno4". So what exactly is it >>> >>>> that *doesn't* work? >>> >>> >>> >>> From QEMU side: >>> >>> acpi-index requires: >>> >>> 1. acpi pci hotplug enabled (which is default on relatively new q35 machine types) >>> >>> 2. hotpluggble pci bus (root-port, various pci bridges) >>> >>> 3. NIC can be cold or hotplugged, guest should pick up acpi-index of the device >>> >>> currently plugged into slot >>> >>> what doesn't work: >>> >>> 1. device attached to host-bridge directly (work in progress) >>> >>> (q35) >>> >>> 2. devices attached to any PXB port and any hierarchy hanging of it (there are not plans to make it work) >>> >>> (q35, pc) >>> >> >>> >> I'd say this is still a relatively important, as the PXBs are needed >>> >> to create a NUMA placement aware topology for guests, and I'd say it >>> >> is undesirable to loose acpi-index if a guest is updated to be NUMA >>> >> aware, or if a guest image can be deployed in either normal or NUMA >>> >> aware setups. >>> > >>> > it's not only Q35 but also PC. >>> > We basically do not generate ACPI hierarchy for PXBs at all, >>> > so neither ACPI hotplug nor depended acpi-index would work. >>> > It's been so for many years and no one have asked to enable >>> > ACPI hotplug on them so far. >>> >>> I'm guessing (based on absolutely 0 information :-)) that there would be >>> more demand for acpi-index (and the resulting predictable interface >>> names) than for acpi hotplug for NUMA-aware setup. >> >> >> My guess is similar, but it is still desirable to have both (i.e. support ACPI-indexing/hotplug with Numa-aware) >> Adding @Peter Xu to check if our setups for SAP require NUMA-aware topology >> >> How big of a project would it be to enable ACPI-indexing/hotplug with PXB? Why would you need to add acpi hotplug on pxb? > Adding +Julia Suvorova and +Tsirkin, Michael to help answer this question > > Thanks, > Amnon > >> >> Since native PCI was improved, we can still compromise on switching to native-PCI-hotplug when PXB is required (and no fixed indexing) Native hotplug works on pxb as is, without disabling acpi hotplug. >> Thanks, >> Amnon >> >> >>> >>> >>> Anyway, it sounds like (*within the confines of how libvirt constructs >>> the PCI topology*) we actually have functional parity of acpi-index >>> between 440fx and Q35. >>>

4 3

libvirt_connect_get_machine_types
by Simon Fairweather 07 Dec '22

07 Dec '22

Using the following php: version 8.1.13 php-libvirt: version 0.5.6 (build 2) libvirt 8.7.0 QEMU 7.1.0 virsh capabilities works fine. <os_type>hvm</os_type> <arch name='x86_64'> <wordsize>64</wordsize> <emulator>/usr/bin/qemu-system-x86_64</emulator> <machine maxCpus='255'>pc-i440fx-7.1</machine> <machine canonical='pc-i440fx-7.1' maxCpus='255'>pc</machine> <machine maxCpus='288'>pc-q35-5.2</machine> <machine maxCpus='255'>pc-i440fx-2.12</machine> <machine maxCpus='255'>pc-i440fx-2.0</machine> <machine maxCpus='255'>pc-i440fx-6.2</machine> <machine maxCpus='288'>pc-q35-4.2</machine> <machine maxCpus='255'>pc-i440fx-2.5</machine> <machine maxCpus='255'>pc-i440fx-4.2</machine> <machine maxCpus='255'>pc-i440fx-5.2</machine> <machine maxCpus='255' deprecated='yes'>pc-i440fx-1.5</machine> <machine maxCpus='255'>pc-q35-2.7</machine> <machine maxCpus='288'>pc-q35-7.1</machine> <machine canonical='pc-q35-7.1' maxCpus='288'>q35</machine> <machine maxCpus='255'>pc-i440fx-2.2</machine> <machine maxCpus='255'>pc-i440fx-2.7</machine> <machine maxCpus='288'>pc-q35-6.1</machine> <machine maxCpus='255'>pc-q35-2.4</machine> <machine maxCpus='288'>pc-q35-2.10</machine> <machine maxCpus='1'>x-remote</machine> <machine maxCpus='288'>pc-q35-5.1</machine> <machine maxCpus='255' deprecated='yes'>pc-i440fx-1.7</machine> <machine maxCpus='288'>pc-q35-2.9</machine> <machine maxCpus='255'>pc-i440fx-2.11</machine> <machine maxCpus='288'>pc-q35-3.1</machine> <machine maxCpus='255'>pc-i440fx-6.1</machine> <machine maxCpus='288'>pc-q35-4.1</machine> <machine maxCpus='255'>pc-i440fx-2.4</machine> <machine maxCpus='255'>pc-i440fx-4.1</machine> <machine maxCpus='255'>pc-i440fx-5.1</machine> <machine maxCpus='255'>pc-i440fx-2.9</machine> <machine maxCpus='1'>isapc</machine> <machine maxCpus='255' deprecated='yes'>pc-i440fx-1.4</machine> <machine maxCpus='255'>pc-q35-2.6</machine> <machine maxCpus='255'>pc-i440fx-3.1</machine> <machine maxCpus='288'>pc-q35-2.12</machine> <machine maxCpus='288'>pc-q35-7.0</machine> <machine maxCpus='255'>pc-i440fx-2.1</machine> <machine maxCpus='288'>pc-q35-6.0</machine> <machine maxCpus='255'>pc-i440fx-2.6</machine> <machine maxCpus='288'>pc-q35-4.0.1</machine> <machine maxCpus='255'>pc-i440fx-7.0</machine> <machine maxCpus='255' deprecated='yes'>pc-i440fx-1.6</machine> <machine maxCpus='288'>pc-q35-5.0</machine> <machine maxCpus='288'>pc-q35-2.8</machine> <machine maxCpus='255'>pc-i440fx-2.10</machine> <machine maxCpus='288'>pc-q35-3.0</machine> <machine maxCpus='255'>pc-i440fx-6.0</machine> <machine maxCpus='288'>pc-q35-4.0</machine> <machine maxCpus='288'>microvm</machine> <machine maxCpus='255'>pc-i440fx-2.3</machine> <machine maxCpus='255'>pc-i440fx-4.0</machine> <machine maxCpus='255'>pc-i440fx-5.0</machine> <machine maxCpus='255'>pc-i440fx-2.8</machine> <machine maxCpus='288'>pc-q35-6.2</machine> <machine maxCpus='255'>pc-q35-2.5</machine> <machine maxCpus='255'>pc-i440fx-3.0</machine> <machine maxCpus='288'>pc-q35-2.11</machine> <domain type='qemu'/> <domain type='kvm'/> </arch> Any known issues with php 8 for this function, others seem to be working fine.

3 13

Need help
by Gk Gk 02 Dec '22

02 Dec '22

Hi, We have an openstack platform and we are trying to get the network details of the guest vm on the hypervisors using the python libvirt library (domain.interfaceStats) . But in cases of SR-IOV vms, the interface is not being reported by the above tool. The interface in this case is "hostdev" in the guest xml definition. Can anyone let me know how to find out the sr-iov network interface details of the guest vm ? Thanks Kumar

2 1