- Users - libvirt List Archives

why libvirtd can not list the running domain?
by 崔涛的个人邮箱 30 Apr '20

30 Apr '20

1. I run a user domain like this: [root@kvm1 ~]# qemu-system-x86_64 -enable-kvm -m 1G -smp 4 /images/test1.img WARNING: Image format was not specified for '/images/test1.img' and probing guessed raw. Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted. Specify the 'raw' format explicitly to remove the restrictions. VNC server running on ::1:5900 2. Then, I install and using my user domain. 3. Then, I login to libvirtd on my hosts,but can not get the user domain using list command. [root@kvm1 ~]# virsh -c qemu:///system Welcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # virsh # virsh # list Id Name State ---------------------------------------------------- virsh #

2 2

"failed to setup INTx fd: Operation not permitted" error when using PCI passthrough
by Riccardo Ravaioli 30 Apr '20

30 Apr '20

Hi, I'm on a Dell VEP 1405 running Debian 9.11 and I'm running a few tests with various interfaces given in PCI passthrough to a qemu/KVM Virtual Machine also running Debian 9.11. I noticed that only one of the four I350 network controllers can be used in PCI passthrough. The available interfaces are: *# dpdk-devbind.py --status Network devices using kernel driver ==============================* *===== 0000:02:00.0 'I350 Gigabit Network Connection 1521' if=eth2 drv=igb unused=igb_uio,vfio-pci,uio_* *pci_generic 0000:02:00.1 'I350 Gigabit Network Connection 1521' if=eth3 drv=igb unused=igb_uio,vfio-pci,uio_* *pci_generic 0000:02:00.2 'I350 Gigabit Network Connection 1521' if=eth0 drv=igb unused=igb_uio,vfio-pci,uio_* *pci_generic 0000:02:00.3 'I350 Gigabit Network Connection 1521' if=eth1 drv=igb unused=igb_uio,vfio-pci,uio_* *pci_generic 0000:04:00.0 'QCA986x/988x 802.11ac Wireless Network Adapter 003c' if= drv=ath10k_pci unused=igb_uio,vfio-pci,uio_* *pci_generic 0000:05:00.0 'Device 15c4' if=eth7 drv=ixgbe unused=igb_uio,vfio-pci,uio_* *pci_generic 0000:05:00.1 'Device 15c4' if=eth6 drv=ixgbe unused=igb_uio,vfio-pci,uio_* *pci_generic 0000:07:00.0 'Device 15e5' if=eth5 drv=ixgbe unused=igb_uio,vfio-pci,uio_* *pci_generic 0000:07:00.1 'Device 15e5' if=eth4 drv=ixgbe unused=igb_uio,vfio-pci,uio_**pci_generic* If I try PCI passthrough on 02:00.2 (eth0), it works fine. With any of the remaining three interfaces, libvirt fails with this error: *# virsh create vnf.xml error: Failed to create domain from vnf.xml error: internal error: process exited while connecting to monitor: 2020-04-06T16:08:47.048266Z qemu-system-x86_64: -device vfio-pci,host=02:00.1,id=**hostdev0,bus=pci.0,addr=0x5: vfio 0000:02:00.1: failed to setup INTx fd: Operation not permitted* The contents of vnf.xml are available here: https://pastebin.com/rT3RmAi5 This is what happened in *dmesg* when I tried to start the VM: *[ 7305.371730] igb 0000:02:00.1: removed PHC on eth3 [ 7307.085618] ACPI Warning: \_SB.PCI0.PEX2._PRT: Return Package has no elements (empty) (20160831/nsprepkg-130) [ 7307.085717] pcieport 0000:00:0b.0: can't derive routing for PCI INT B [ 7307.085719] vfio-pci 0000:02:00.1: PCI INT B: no GSI [ 7307.369611] igb 0000:02:00.1: enabling device (0400 -> 0402) [ 7307.369668] ACPI Warning: \_SB.PCI0.PEX2._PRT: Return Package has no elements (empty) (20160831/nsprepkg-130) [ 7307.369764] pcieport 0000:00:0b.0: can't derive routing for PCI INT B [ 7307.369766] igb 0000:02:00.1: PCI INT B: no GSI [ 7307.426266] igb 0000:02:00.1: added PHC on eth3 [ 7307.426269] igb 0000:02:00.1: Intel(R) Gigabit Ethernet Network Connection [ 7307.426271] igb 0000:02:00.1: eth3: (PCIe:5.0Gb/s:Width x2) 50:9a:4c:ee:9f:b1 [ 7307.426350] igb 0000:02:00.1: eth3: PBA No: 106300-000 [ 7307.426352] igb 0000:02:00.1: Using MSI-X interrupts. 4 rx queue(s), 4 tx queue(s)* These are all the messages related to that device in dmesg before I tried to start the VM: *# dmesg | grep 02:00.1 [ 0.185301] pci 0000:02:00.1: [8086:1521] type 00 class 0x020000 [ 0.185317] pci 0000:02:00.1: reg 0x10: [mem 0xdfd40000-0xdfd5ffff] [ 0.185334] pci 0000:02:00.1: reg 0x18: [io 0xd040-0xd05f] [ 0.185343] pci 0000:02:00.1: reg 0x1c: [mem 0xdfd88000-0xdfd8bfff] [ 0.185434] pci 0000:02:00.1: PME# supported from D0 D3hot D3cold [ 0.185464] pci 0000:02:00.1: reg 0x184: [mem 0xdeea0000-0xdeea3fff 64bit pref] [ 0.185467] pci 0000:02:00.1: VF(n) BAR0 space: [mem 0xdeea0000-0xdeebffff 64bit pref] (contains BAR0 for 8 VFs) [ 0.185486] pci 0000:02:00.1: reg 0x190: [mem 0xdee80000-0xdee83fff 64bit pref] [ 0.185488] pci 0000:02:00.1: VF(n) BAR3 space: [mem 0xdee80000-0xdee9ffff 64bit pref] (contains BAR3 for 8 VFs) [ 0.334021] DMAR: Hardware identity mapping for device 0000:02:00.1 [ 0.334463] iommu: Adding device 0000:02:00.1 to group 16 [ 0.398809] pci 0000:02:00.1: Signaling PME through PCIe PME interrupt [ 2.588049] igb 0000:02:00.1: PCI INT B: not connected [ 2.643900] igb 0000:02:00.1: added PHC on eth1 [ 2.643903] igb 0000:02:00.1: Intel(R) Gigabit Ethernet Network Connection [ 2.643905] igb 0000:02:00.1: eth1: (PCIe:5.0Gb/s:Width x2) 50:9a:4c:ee:9f:b1 [ 2.643984] igb 0000:02:00.1: eth1: PBA No: 106300-000 [ 2.643986] igb 0000:02:00.1: Using MSI-X interrupts. 4 rx queue(s), 4 tx queue(s) [ 2.873544] igb 0000:02:00.1 rename3: renamed from eth1 [ 2.939352] igb 0000:02:00.1 eth3: renamed from rename3* In particular this looks suspicious: *igb 0000:02:00.1: PCI INT B: not connected* The full dmesg is available here: https://pastebin.com/kPbUAKCi This is the PCI bus structure: *# lspci -tv -[0000:00]-+-00.0 Intel Corporation Device 1980 +-04.0 Intel Corporation Device 19a1 +-05.0 Intel Corporation Device 19a2 +-06.0-[01]----00.0 Intel Corporation Device 19e2 +-0b.0-[02-03]--+-00.0 Intel Corporation I350 Gigabit Network Connection | +-00.1 Intel Corporation I350 Gigabit Network Connection | +-00.2 Intel Corporation I350 Gigabit Network Connection | \-00.3 Intel Corporation I350 Gigabit Network Connection +-0f.0-[04]----00.0 Qualcomm Atheros QCA986x/988x 802.11ac Wireless Network Adapter +-12.0 Intel Corporation DNV SMBus Contoller - Host +-13.0 Intel Corporation DNV SATA Controller 0 +-15.0 Intel Corporation Device 19d0 +-16.0-[05-06]--+-00.0 Intel Corporation Device 15c4 | \-00.1 Intel Corporation Device 15c4 +-17.0-[07-08]--+-00.0 Intel Corporation Device 15e5 | \-00.1 Intel Corporation Device 15e5 +-18.0 Intel Corporation Device 19d3 +-1c.0 Intel Corporation Device 19db +-1f.0 Intel Corporation DNV LPC or eSPI +-1f.2 Intel Corporation Device 19de +-1f.4 Intel Corporation DNV SMBus controller \-1f.5 Intel Corporation DNV SPI Controller* By looking at lspci -v, there's something going on with the IRQ field exactly in three devices I can't use in PCI passthrough ("IRQ -2147483648"): *# lspci -v|grep -A1 I350 02:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01) Flags: bus master, fast devsel, latency 0, IRQ -2147483648 -- 02:00.1 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01) Flags: bus master, fast devsel, latency 0, IRQ -2147483648 -- 02:00.2 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01) Flags: bus master, fast devsel, latency 0, IRQ 18 -- 02:00.3 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01) Flags: bus master, fast devsel, latency 0, IRQ -2147483648* Finally, every i350 interface has its own IOMMU group in /sys/kernel/iommu_groups/. The kernel I'm using in the host machine is 4.9.189 and my libvirt version is 4.3.0. Any thoughts on this? Is there something I should enable in the BIOS or in the kernel to make this work? Thanks! Regards, Riccardo Ravaioli

1 1

Attaching DVD-writer
by Andreas Thörn 27 Apr '20

27 Apr '20

I want to add my dvd and be able to burn dvd’s. I’ve tried every solution I could find, but nothing works. In my xml i have: <disk type='block' device='cdrom'> <driver name='qemu' type='raw'/> <source dev='/dev/sr0'/> <target dev='sdb' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> In my guest (windows 10) it’s shown as "QEMU QEMU DVD-ROM” .. which of course means I can’t burn. If anyone has a solution it would be this mailing list Thanks Andreas

4 5

domain: how long is new xml in saved file
by Vincent Wu 27 Apr '20

27 Apr '20

Hi administrator, I am a cloud compute developer. I need some help from you about libvirt. I have a work to modify a image file which is saved by virDomainSave() or virDomainSaveFlags(). So virDomainSaveImageGetXMLDesc() and virDomainSaveImageDefineXML() are APIs I choosed to do. Because I found a sentence: A save file can be inspected or modified slightly with virDomainSaveImageGetXMLDesc() and virDomainSaveImageDefineXML(). But an error is happened when I do like that.  libvirt: QEMU Driver error: operation failed: new xml too large to fit in file. I found that if I increase strlen(xml_old) to strlen(xml_new). if (strlen(xml_new) - strlen(xml_old) <= 29) { this is right; } but if (strlen(xml_new) - strlen(xml_old) >= 50) { this is error; } But I don't choose to find an accurate number.  I think this value will be affected by some factors. For example: memory alignment, range safety or other rules. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +                                                           strlen(xml_old)                                                  +  free space  + ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +                                                             strlen(xml_new)                                                                     + ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ I really want to know how long free space I can use. Can you convert slightly to a precise number? Thank you for taking so long to read my Email. Looking forward to your reply. ps: OS: CentOS7.4 libvirt: 4.5.0 hypervisor: KVM Sincerely,  Vincent Wu

5 5

Not able to add pcie card to guest: Operation not permitted
by Mauricio Tavares 25 Apr '20

25 Apr '20

Let's say I have libvirt [root@vmhost2 ~]# virsh version Compiled against library: libvirt 4.5.0 Using library: libvirt 4.5.0 Using API: QEMU 4.5.0 Running hypervisor: QEMU 2.12.0 [root@vmhost2 ~]# running on centos 8 and then I have this card [root@vmhost2 ~]# virsh nodedev-dumpxml pci_0000_01_00_0 <device> <name>pci_0000_01_00_0</name> <path>/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0</path> <parent>pci_0000_00_01_0</parent> <driver> <name>mlx4_core</name> </driver> <capability type='pci'> <domain>0</domain> <bus>1</bus> <slot>0</slot> <function>0</function> <product id='0x1003'>MT27500 Family [ConnectX-3]</product> <vendor id='0x15b3'>Mellanox Technologies</vendor> <iommuGroup number='1'> <address domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </iommuGroup> <pci-express> <link validity='cap' port='8' speed='8' width='8'/> <link validity='sta' speed='5' width='8'/> </pci-express> </capability> </device> which I added to the guest (arch='x86_64' machine='pc-q35-rhel7.6.0') as <hostdev mode='subsystem' type='pci' managed='yes'> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x08' slot='0x00' function='0x0'/> </hostdev> When I try to start the guest I get the following error message: [root@vmhost2 ~]# virsh start testfedora error: Failed to start domain testfedora error: internal error: qemu unexpectedly closed the monitor: 2020-04-24T20:01:35.341020Z qemu-kvm: -device vfio-pci,host=01:00.0,id=hostdev0,bus=pci.8,addr=0x0: vfio error: 0000:01:00.0: failed to setup INTx fd: Operation not permitted [root@vmhost2 ~]# Why is it telling me that is not permitted?

2 3

Virsh migrate and paused vm
by Paras Pradhan 24 Apr '20

24 Apr '20

Hello I have a question regarding virsh migrate. I see this when I migrate a vm using the command --- virsh --connect=xen:///system migrate --live --verbose vm1 xen+ssh://node2/system --- I see the vm keeps running on node1 and on node2 its paused. Libvirt version is 5.1.0-8.11.6.x86_64 and hypervisor is Xen 4.12. No issues when running --- xl migrate vm1 node2 --- Any help is appreciated. Thanks P

2 1

php libvirt show active snapshot
by Todd Lewis 21 Apr '20

21 Apr '20

Is php libvirt able to list the active snapshot for the vm? I can easily take snapshots and restore snapshots, but I can't figure out how to display the currently active snapshot using php libvirt. -- Todd Lewis Grizzly Star (469) 363-2907 Cell www.grizzlystar.com

3 7

My VMs don't get IP with libvirt and dnsmasq
by Computers Issues 17 Apr '20

17 Apr '20

Hello there, I wanted to share a problem I'm having with libvirt, for the case someone here could know how to solve it. I'm using an Ubuntu 18.04 LTS, I have libvirtd already installed and I think I got all the dependencies installed. So, I'm using virsh net-create to create this network: <network> <name>pepito</name> <forward mode='nat'/> <bridge name='virbr2' stp='on' delay='0'/> <ip address='192.168.150.1' netmask='255.255.255.0'> <dhcp> <range start='192.168.150.2' end='192.168.150.254'/> </dhcp> </ip> </network> And then I create a domain with this xml: <domain type='qemu' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>ARM</name> <memory unit='KiB'>262144</memory> <currentMemory unit='KiB'>262144</currentMemory> <os> <type arch='armv7l' machine='virt-2.9'>hvm</type> <kernel>~/zImage</kernel> <cmdline>console=ttyAMA0 root=/dev/vda</cmdline> <boot dev='hd'/> </os> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/bin/qemu-system-aarch64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2'/> <source file=' ~/rootfs.qcow2'/> <target dev='hda' bus='virtio'/> </disk> <controller type='virtio-serial' index='0'> <address type='virtio-mmio'/> </controller> <interface type='network'> <mac address='52:54:00:09:a4:37'/> <model type='virtio'/> <source network='pepito'/> <address type='virtio-mmio'/> </interface> </devices> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='virtio-net-pci'/> <qemu:arg value='-netdev'/> <qemu:arg value='user,id=net1'/> </qemu:commandline> </domain> They both work as I created them in a different computer and everything works. But I'm trying it on my other Ubuntu machine, and once virsh creates the network and the domain, my VM never get an IP from that DHCP range. This is libvirtd log: abr 17 00:48:11 usuario-System-Product-Name dnsmasq-dhcp[13741]: DHCP, IP range 192.168.150.2 -- 192.168.150.254, lease time 1h abr 17 00:48:11 usuario-System-Product-Name dnsmasq-dhcp[13741]: DHCP, sockets bound exclusively to interface virbr2 abr 17 00:48:11 usuario-System-Product-Name dnsmasq[13741]: reading /etc/resolv.conf abr 17 00:48:11 usuario-System-Product-Name dnsmasq[13741]: using nameserver 127.0.0.53#53 abr 17 00:48:11 usuario-System-Product-Name dnsmasq[13741]: read /etc/hosts - 7 addresses abr 17 00:48:11 usuario-System-Product-Name dnsmasq[13741]: read /var/lib/libvirt/dnsmasq/pepito.addnhosts - 0 addresses abr 17 00:48:11 usuario-System-Product-Name dnsmasq-dhcp[13741]: read /var/lib/libvirt/dnsmasq/pepito.hostsfile Does anybody know why it could be that the VM never gets an IP from the range I defined? As I said, exactly the same configuration worked in a different machine, I don't know why it does not work here. Thank you so much!! <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Libre de virus. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

3 8

Ovs error when starting vm: ovs-vsctl: 'del-port' command requires at least 1 arguments
by Thomas Pircher 16 Apr '20

16 Apr '20

Hi, my system got updated to libvirt 6.0.0 (from 5.6.0) this morning, and now I'm having problems starting VMs that make use of openvswitch portgroups. When I start a VM, I get this error message on virsh: > virsh # start testvm > error: Failed to start domain testvm > error: An error occurred, but the cause is unknown The system log contains: > Mar 30 09:45:39 tplinux ovs-vsctl[2763]: ovs|00001|db_ctl_base|ERR|'del-port' command requires at least 1 arguments > Mar 30 09:45:39 tplinux libvirtd[735]: internal error: Child process (ovs-vsctl --timeout=5 -- --if-exists del-port) unexpected exit status 1: ovs-vsctl: 'del-port' command requires at least 1 arguments > Mar 30 09:45:39 tplinux libvirtd[735]: internal error: Unable to delete port (null) from OVS My network "test-net" looks like: > <network> > <name>test-net</name> > <forward mode='bridge'/> > <bridge name='test-net'/> > <virtualport type='openvswitch'/> > <portgroup name='fabric' default='yes'> > <vlan trunk='yes'> > <tag id='10' nativeMode='untagged'/> > <tag id='20'/> > <tag id='30'/> > <tag id='40'/> > <tag id='50'/> > <tag id='60'/> > <tag id='70'/> > </vlan> > </portgroup> > </network> And the network in the domain xml file is: > <interface type='network'> > <mac address='01:23:45:67:89:ab'/> > <source network='test-net' portgroup='fabric'/> > <model type='e1000'/> > <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> > </interface> I didn't see any change in the changelog related to ovs or portgroups. Is there something I need to change in my VM definition? Thanks, Thomas

2 3

FYI: upstream bug reporting now using https://gitlab.com/libvirt
by Daniel P. Berrangé 16 Apr '20

16 Apr '20

In keeping with our general aim to consolidate libvirt project infrastructure services on GitLab, we now wish to have issues for upstream libvirt projects reported on the appropriate https://gitlab.com/libvirt/ repository issue tracker. For further details see: https://libvirt.org/bugs.html Bugs against OS distro provided binary packages should continue to be filed against the OS distros' own bug trackers unless the problem is known to also affect current upstream libvirt versions. Note that as part of this change, the "Virtualization Tools" component on bugzilla.redhat.com has been updated to remove the ability to file new bugs against libvirt related components. Existing bugs there still exist in bugzilla, but new bugs can only be filed against gitlab.com. Over time we hope to triage old bugs and close those that are either invalid, or those not likely to be addressed given current maintainer resources available. 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