- Users - libvirt List Archives

[libvirt-users] LIBVIRT-4.6.0 can't work with QEMU 3.0.0
by Holger Schranz 08 Aug '18

08 Aug '18

Hello, if I try to use Llibvirt-4.6.0 together with qemu-3.0.0-rc4. I run into an issue. Please see the following Memo. Best regards Holger ================================================================================ Procduce QEMU-3.0.0-RC4 and LIBVIRT-4.6.0: QEMU-3-0-0-RC4: make clean ./configure --enable-libiscsi --enable-libusb --enable-bzip2 --enable-libnfs --enable-spice --enable-user --enable-virtfs --enable-opengl --enable-sdl --enable-gtk --enable-virglrenderer --disable-seccomp --prefix=/usr;make -j$(grep -c ^processor /proc/cpuinfo) su make install LIBVIRT-4.6.0 make clean ./configure -q --with-lxc --with-storage-iscsi --with-storage-scsi --with-interface --with-storage-lvm --with-storage-fs --with-udev --with-vmware --with-storage-mpath --prefix=/usr;make -j$(grep -c ^processor /proc/cpuinfo) su systemctl stop libvirtd.service cd libvirt-4.5.0 make uninstall cd .. cd libvirt-4.6.0 make install systemctl status libvirtd.service -l systemctl daemon-reload systemctl start libvirtd.service systemctl status libvirtd.service -l ? libvirtd.service - Virtualization daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; vendor preset: disabled) Active: active (running) since Wed 2018-08-08 09:05:26 CEST; 3s ago Docs: man:libvirtd(8) https://libvirt.org Main PID: 137948 (libvirtd) Tasks: 19 (limit: 32768) CGroup: /system.slice/libvirtd.service ?? 4725 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt_leaseshelper ?? 4726 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt_leaseshelper ??137948 /usr/sbin/libvirtd Aug 08 09:05:26 etcsvms5 systemd[1]: Starting Virtualization daemon... Aug 08 09:05:26 etcsvms5 systemd[1]: Started Virtualization daemon. Aug 08 09:05:26 etcsvms5 libvirtd[137948]: 2018-08-08 07:05:26.876+0000: 137964: info : libvirt version: 4.6.0 Aug 08 09:05:26 etcsvms5 libvirtd[137948]: 2018-08-08 07:05:26.876+0000: 137964: info : hostname: etcsvms5 Aug 08 09:05:26 etcsvms5 libvirtd[137948]: 2018-08-08 07:05:26.876+0000: 137964: error : virNetworkObjAssignDefLocked:589 : operation failed: network 'default' already exists with uuid 52abe250-4f23-40fe-875e-0808d57ce72d Aug 08 09:05:27 etcsvms5 dnsmasq[4725]: read /etc/hosts - 8 addresses Aug 08 09:05:27 etcsvms5 dnsmasq[4725]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses Aug 08 09:05:27 etcsvms5 dnsmasq-dhcp[4725]: read /var/lib/libvirt/dnsmasq/default.hostsfile Aug 08 09:05:27 etcsvms5 libvirtd[137948]: 2018-08-08 07:05:27.711+0000: 137964: warning : virLXCDriverCapsInit:82 : Failed to get host CPU cache info Aug 08 09:05:27 etcsvms5 libvirtd[137948]: 2018-08-08 07:05:27.719+0000: 137964: warning : umlCapsInit:73 : Failed to get host CPU cache info etcsvms5:/home/shl/Install/libvirt-4.6.0 # ---> test1: Start virt-manager etcsvms5:/home/shl/Install/libvirt-4.6.0 # virsh version Compiled against library: libvirt 4.6.0 Using library: libvirt 4.6.0 Using API: LXC 4.6.0 Running hypervisor: LXC 4.4.140 etcsvms5:/home/shl/Install/libvirt-4.6.0 # Information on virt-manager window: Unable to connect to libvirt qemu:///system. no connection driver available for qemu:///system Libvirt URI is: qemu:///system Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/connection.py", line 1036, in _do_open self._backend.open(self._do_creds_password) File "/usr/share/virt-manager/virtinst/connection.py", line 144, in open open_flags) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 104, in openAuth if ret is None:raise libvirtError('virConnectOpenAuth() failed') libvirtError: no connection driver available for qemu:///system ---> TEst2: Call VM via virsh create etcsvms5:/home/shl/Install/libvirt-4.6.0 # cd /kvm/CS8400/M4 etcsvms5:/kvm/CS8400/M4 # cd VLP0 etcsvms5:/kvm/CS8400/M4/VLP0 # virsh create M4-VLP0.xml error: Failed to create domain from M4-VLP0.xml error: invalid argument: could not find capabilities for arch=x86_64 domaintype=kvm etcsvms5:/kvm/CS8400/M4/VLP0 # ----- switch back to LIBVIRT.4-5-0 and all runs o.k. --- Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft. https://www.avast.com/antivirus

3 6

[libvirt-users] Qemu guest display black after reboot
by Allence 06 Aug '18

06 Aug '18

Hey, every friend. I have a question. My guests are not working, unbelievable. I can use it the first time I use it. But after I close my guest and start over, my guests will not appear. My screen is black. My environment: Guest: windows 10 vm-bios: ovmf host: ubuntu 1604 qemu: 2.12 libvirt: 4.2 kernel: 4.17.2 xml config: gpu: <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=0000:01:00.0,romfile=/root/rom.file,multifunction=on,x-vga=on'/> </qemu:commandline> features: <kvm> <hidden state='on'/> </kvm>

1 0

[libvirt-users] Trouble passing PCI device in isolated IOMMU group
by Quincy Wofford 06 Aug '18

06 Aug '18

I'm attempting PCI-passthrough from host to guest on an HP ProLiant 380P, which has an outdated BIOS (2014), but it does support VT-d. I'm running CentOS 7, kernel 3.10.0-862.9.1.el7.x86_64. I have an Intel 82580 NIC installed with 4 ports. Each of these ports is in its own IOMMU group (I enabled SR-IOV at the BIOS, which might be the reason they show up separately) After detaching and adding a 'hostdev' device with the appropriate pci address, I attempt to start my VM. I get " failed to set iommu for container: Operation not permitted". As recommended here ( http://vfio.blogspot.com/2014/08/vfiovga-faq.html) I parsed dmesg in an attempt to find: ------------------- No interrupt remapping support. Use the module param "allow_unsafe_interrupts" to enable VFIO IOMMU support on this platform ------------------- ...but nothing similar exists in my logs. Since this device is showing up in its own IOMMU group, I assume ACS override won't get me any further. In any case, it is not an option for me to leave ACS override on. I can turn it on for testing, the server is not currently in production. Any idea why this could be failing?

2 2

[libvirt-users] How to set the MTU size of VM interface
by netsurfed 06 Aug '18

06 Aug '18

Dear all: I start a VM with MTU size 1450, and login VM to check the mtu size, but this setting didn't work. The VM xml is like this: <interface type='bridge'> <mac address='52:54:00:54:14:f8'/> <source bridge='ovsbr1'/> <virtualport type='openvswitch'> <parameters interfaceid='a42e5b42-09db-4cfa-b198-d2ce62843378'/> </virtualport> <target dev='vnet0'/> <model type='virtio'/> <mtu size='1450'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> However, the actual mtu size of VM is still 1500, as following: root@ubuntu-zhf:~# ip addr 2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:54:14:f8 brd ff:ff:ff:ff:ff:ff The MTU size of both ovs bridge and vnet are 1450 in my hypervisor: root@ubuntu-191:~# ip addr show ovsbr1 16: ovsbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UNKNOWN group default qlen 1 link/ether 12:01:7b:5b:85:49 brd ff:ff:ff:ff:ff:ff inet6 fe80::1001:7bff:fe5b:8549/64 scope link valid_lft forever preferred_lft forever root@ubuntu-191:~# ip addr show vnet0 22: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc pfifo_fast master ovs-system state UNKNOWN group default qlen 1000 link/ether fe:54:00:54:14:f8 brd ff:ff:ff:ff:ff:ff inet6 fe80::fc54:ff:fe54:14f8/64 scope link valid_lft forever preferred_lft forever I use ovs to create vxlan networks and add VMs to the ovs bridge. Because of the limitations of vxlan, I need to set the mtu of vm to 1450. How to set the MTU of VM? Thanks. Below some information about my hypervisor: root@ubuntu-192:~# virsh -V Virsh command line tool of libvirt 3.4.0 See web site at http://libvirt.org/ Compiled with support for: Hypervisors: QEMU/KVM LXC UML OpenVZ VMware VirtualBox Test Networking: Remote Network Bridging Interface udev Nwfilter VirtualPort Storage: Dir Filesystem SCSI Multipath iSCSI LVM Miscellaneous: Daemon Nodedev SELinux Secrets Debug Modular root@ubuntu-192:~# qemu-x86_64 --version qemu-x86_64 version 2.9.0 Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers root@ubuntu-192:~# uname -a Linux ubuntu-192 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

3 2

[libvirt-users] multiple devices in the same iommu group in L1 guest
by Yalan Zhang 06 Aug '18

06 Aug '18

Hi, I have a guest enabled vIOMMU, but on the guest there are several devices in the same iommu group. Could someone help to check if I missed something? Thank you very much! 1. guest xml: # virsh edit q ... <os> <type arch='x86_64' machine='pc-q35-rhel7.5.0'>hvm</type> <loader readonly='yes' secure='yes' type='pflash'>/usr/share/OVMF/OVMF_CODE.secboot.fd</loader> <nvram>/var/lib/libvirt/qemu/nvram/q_VARS.fd</nvram> </os> ... <features> ... <ioapic driver='qemu'/> </features> <cpu mode='host-passthrough' check='none'> <feature policy='require' name='vmx'/> </cpu> ... <devices> ... <controller type='pci' index='7' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='7' port='0x15'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x5'/> </controller> <interface type='network'> <mac address='52:54:00:b9:ff:90'/> <source network='default'/> <model type='e1000'/> <address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </interface> <iommu model='intel'> <driver intremap='on' caching_mode='on' iotlb='on'/> </iommu> </devices> ... 2. guest has 'intel_iommu=on' enabled in kernel cmdline, then reboot guest 3. log in guest to check: # dmesg | grep -i DMAR [ 0.000000] ACPI: DMAR 000000007d83f000 00050 (v01 BOCHS BXPCDMAR 00000001 BXPC 00000001) [ 0.000000] DMAR: IOMMU enabled [ 0.155178] DMAR: Host address width 39 [ 0.155180] DMAR: DRHD base: 0x000000fed90000 flags: 0x1 [ 0.155221] DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap 12008c22260286 ecap f00f5e [ 0.155228] DMAR: ATSR flags: 0x1 [ 0.155231] DMAR-IR: IOAPIC id 0 under DRHD base 0xfed90000 IOMMU 0 [ 0.155232] DMAR-IR: Queued invalidation will be enabled to support x2apic and Intr-remapping. [ 0.156843] DMAR-IR: Enabled IRQ remapping in x2apic mode [ 2.112369] DMAR: No RMRR found [ 2.112505] DMAR: dmar0: Using Queued invalidation [ 2.112669] DMAR: Setting RMRR: [ 2.112671] DMAR: Prepare 0-16MiB unity mapping for LPC [ 2.112820] DMAR: Setting identity map for device 0000:00:1f.0 [0x0 - 0xffffff] [ 2.211577] DMAR: Intel(R) Virtualization Technology for Directed I/O ===> This is expected # dmesg | grep -i iommu |grep device [ 2.212267] iommu: Adding device 0000:00:00.0 to group 0 [ 2.212287] iommu: Adding device 0000:00:01.0 to group 1 [ 2.212372] iommu: Adding device 0000:00:02.0 to group 2 [ 2.212392] iommu: Adding device 0000:00:02.1 to group 2 [ 2.212411] iommu: Adding device 0000:00:02.2 to group 2 [ 2.212444] iommu: Adding device 0000:00:02.3 to group 2 [ 2.212464] iommu: Adding device 0000:00:02.4 to group 2 [ 2.212482] iommu: Adding device 0000:00:02.5 to group 2 [ 2.212520] iommu: Adding device 0000:00:1d.0 to group 3 [ 2.212533] iommu: Adding device 0000:00:1d.1 to group 3 [ 2.212541] iommu: Adding device 0000:00:1d.2 to group 3 [ 2.212550] iommu: Adding device 0000:00:1d.7 to group 3 [ 2.212567] iommu: Adding device 0000:00:1f.0 to group 4 [ 2.212576] iommu: Adding device 0000:00:1f.2 to group 4 [ 2.212585] iommu: Adding device 0000:00:1f.3 to group 4 [ 2.212599] iommu: Adding device 0000:01:00.0 to group 2 [ 2.212605] iommu: Adding device 0000:02:01.0 to group 2 [ 2.212621] iommu: Adding device 0000:04:00.0 to group 2 [ 2.212634] iommu: Adding device 0000:05:00.0 to group 2 [ 2.212646] iommu: Adding device 0000:06:00.0 to group 2 [ 2.212657] iommu: Adding device 0000:07:00.0 to group 2 ====> several devices in the same iommu group # virsh nodedev-dumpxml pci_0000_07_00_0 <device> <name>pci_0000_07_00_0</name> <path>/sys/devices/pci0000:00/0000:00:02.5/0000:07:00.0</path> <parent>pci_0000_00_02_5</parent> <driver> <name>e1000</name> </driver> <capability type='pci'> <domain>0</domain> <bus>7</bus> <slot>0</slot> <function>0</function> <product id='0x100e'>82540EM Gigabit Ethernet Controller</product> <vendor id='0x8086'>Intel Corporation</vendor> <iommuGroup number='2'> <address domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> <address domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> <address domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> <address domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> <address domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> <address domain='0x0000' bus='0x00' slot='0x02' function='0x5'/> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> <address domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> <address domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> <address domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> <address domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> <address domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </iommuGroup> </capability> </device> Thus, can not attach the device to L2 guest: # cat hostdev.xml <hostdev mode='subsystem' type='pci' managed='yes'> <source> <address domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </source> </hostdev> # virsh attach-device rhel hostdev.xml error: Failed to attach device from hostdev.xml error: internal error: unable to execute QEMU command 'device_add': vfio error: 0000:07:00.0: group 2 is not viable ------- Best Regards, Yalan Zhang IRC: yalzhang Internal phone: 8389413

2 1

[libvirt-users] LXC Memory Limits wont work
by Markus Raps 06 Aug '18

06 Aug '18

Hello, iam currently trying to run LXC Containers with libvirt but the memory limit doesn't want to work in the container i see the full 32GB from the Host OS iam pretty sure that iam missing a configline in the xml lxc-template ~ # free -m total used free shared buff/cache available Mem: 32108 626 31396 249 85 31396 Swap: 0 0 0 lxc-template ~ # the host is running debian 9 with default repos hv1 ~ # dpkg -l | grep virt ii libgovirt-common 0.3.4-2 all GObject-based library to access oVirt REST API (common files) ii libgovirt2:amd64 0.3.4-2 amd64 GObject-based library to access oVirt REST API ii libvirt-clients 3.0.0-4+deb9u3 amd64 Programs for the libvirt library ii libvirt-daemon 3.0.0-4+deb9u3 amd64 Virtualization daemon ii libvirt-daemon-system 3.0.0-4+deb9u3 amd64 Libvirt daemon configuration files ii libvirt-glib-1.0-0:amd64 1.0.0-1 amd64 libvirt GLib and GObject mapping library ii libvirt0 3.0.0-4+deb9u3 amd64 library for interfacing with different virtualization systems ii python-libvirt 3.0.0-2 amd64 libvirt Python bindings ii qemu-kvm 1:2.8+dfsg-6+deb9u4 amd64 QEMU Full virtualization on x86 hardware ii virt-viewer 5.0-1 amd64 Displaying the graphical console of a virtual machine ii virtinst 1:1.4.0-5 all Programs to create and clone virtual machines -- best regards Markus Raps

3 3

[libvirt-users] Adding a VLAN tag to a libvirt SR-IOV VF network using the "virsh net-update" command
by Yegappan Lakshmanan 01 Aug '18

01 Aug '18

Hi all, How do you add a VLAN tag to a libvirt SR-IOV VF network usingthe "virsh net-update" command? I couldn't find the section to passto the "virsh net-update" command to add the VLAN tag. I have the following libvirt network defined for a SR-IOV VF: <network> <name>GE0-0-SRIOV-1</name> <uuid>7bc67166-c78e-4bcf-89ee-377dd9086631</uuid> <forward mode='hostdev' managed='yes'> <driver name='vfio'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x10' function='0x0'/> </forward></network> I am trying to add VLAN 100 to this network. If I use the following command toadd a VLAN tag to this network: virsh net-update GE0-0-SRIOV-1 modify bridge --xml "<vlan trunk='no'><tag id='100'/></vlan>" It fails as the section "bridge" doesn't support adding a VLAN tag. I have triedother section values like domain and all of them fail. I am able to add the VLAN to the portgroup section, but then the VLAN configurationis not propagated to the underlying physical PF interface. If I manually add the VLAN configuration using the "virsh net-edit" command andthen connect a VM to this network, then the VLAN information is correctly propagatedto the underlying physical NIC device. I need a way to automate this configuration. Any pointers? Thanks,Yegappan

2 1

[libvirt-users] USB network adapter nat support
by Robert Searle 01 Aug '18

01 Aug '18

Hi I read wireless nat networks are not supported. What about USB network adapters? Can I setup a nat network on a USB network adapter?

3 2

[libvirt-users] ecryptfs (from centosplus) and libvirt lxc quest on it - quest upon start shoots host in the head
by lejeczek 01 Aug '18

01 Aug '18

hi guys I have a lxc guest on Dell's R815(AMD Opterons) which I just moved to an ecryptfs mounted folder(using centosplus' kernel C7.5) Copying data to that folder seems to work just fine, but I as soon as I start the quest, the host gets shot in the head almost immediately, hard reboot, no dump. I also have another, virtually identical guest but on Intel platform and that one does not do anything but runs okey. Any of you guys has experience such gross abnormality? (maybe a heads-up to redhat if cryptfs was to be ever added) many thanks, L.

1 0

[libvirt-users] libvirt and UEFI/SecureBoot
by Shmuel Melamud 16 Jul '18

16 Jul '18

Hi! I'm working currently on integration of UEFI/SecureBoot support into oVirt. And I have several questions about UEFI/SecureBoot support in libvirt. Can you please help me with them? For UEFI I add the following to the XML: <loader readonly="yes" secure="no" type="pflash"> /usr/share/OVMF/OVMF_CODE.secboot.fd </loader> <nvram template="/usr/share/OVMF/OVMF_VARS.fd"> /var/lib/libvirt/qemu/nvram/VM_UUID.fd </nvram> 1. Are all paths mandatory or there are some defaults? 2. If nvram image file is absent, libvirt creates it? 3. Is nvram image file only read or is it also written? 4. If nvram image file is present, is it used? Or removed and created again? 5. Is nvram image file used only on VM startup, or it must be present all the time the VM is running? Is it used on VM shutdown? 6. What happens if the VM is migrated at the moment when nvram image file is used? Is this file migrated also? 7. Is it enough to set secure="yes" to boot the VM with SecureBoot? Or I need to prepare the nvram somehow (install keys etc.)? 8. How to verify that the VM was indeed booted with UEFI? With SecureBoot? Shmuel

2 1

[libvirt-users] compile error libvirt-python 4.5.0 - error: unknown type name ?virNWFilterBindingPtr?
by Holger Schranz 11 Jul '18

11 Jul '18

Hello, I have tried to upgrade libvirt / libvort-python from 4.4.0 to 4.5.0 1) libvirt configure and install Compile and install of libvirt 4.5.0 complete without problems. Configure: ./configure -q --with-lxc --with-storage-iscsi --with-storage-scsi --with-interface --with-storage-lvm --with-storage-fs --with-udev --with-vmware --with-storage-mpath --prefix=/usr;make -j6 The following installation was successful: ETCSVMS3:~ # virsh version --daemon 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 Running against daemon: 4.5.0 ETCSVMS3:~ # 2) libvirt-python build and install this steps end with a compile error. Protocol: shl@ETCSVMS3:~/Install/libvirt-python-4.5.0> python setup.py build running build /usr/bin/pkg-config --print-errors --atleast-version=0.9.11 libvirt /usr/bin/python generator.py libvirt /usr/share/libvirt/api/libvirt-api.xml Found 446 functions in /usr/share/libvirt/api/libvirt-api.xml Found 0 functions in libvirt-override-api.xml Generated 365 wrapper functions /usr/bin/python generator.py libvirt-qemu /usr/share/libvirt/api/libvirt-qemu-api.xml Found 5 functions in /usr/share/libvirt/api/libvirt-qemu-api.xml Found 0 functions in libvirt-qemu-override-api.xml Generated 3 wrapper functions /usr/bin/pkg-config --atleast-version=1.0.2 libvirt /usr/bin/python generator.py libvirt-lxc /usr/share/libvirt/api/libvirt-lxc-api.xml Found 4 functions in /usr/share/libvirt/api/libvirt-lxc-api.xml Found 0 functions in libvirt-lxc-override-api.xml Generated 2 wrapper functions running build_py creating build/lib.linux-x86_64-2.7 copying build/libvirt.py -> build/lib.linux-x86_64-2.7 copying build/libvirt_qemu.py -> build/lib.linux-x86_64-2.7 copying build/libvirt_lxc.py -> build/lib.linux-x86_64-2.7 running build_ext building 'libvirtmod' extension creating build/temp.linux-x86_64-2.7 creating build/temp.linux-x86_64-2.7/build gcc -pthread -fno-strict-aliasing -fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -g -DNDEBUG -fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -g -DOPENSSL_LOAD_CONF -fwrapv -fPIC -I. -I/usr/include/python2.7 -c libvirt-override.c -o build/temp.linux-x86_64-2.7/libvirt-override.o In file included from libvirt-override.c:24:0: typewrappers.h:114:5: error: unknown type name ?virNWFilterBindingPtr? virNWFilterBindingPtr obj; ^ typewrappers.h:201:46: error: unknown type name ?virNWFilterBindingPtr? PyObject * libvirt_virNWFilterBindingPtrWrap(virNWFilterBindingPtr node); ^ error: command 'gcc' failed with exit status 1 shl@ETCSVMS3:~/Install/libvirt-python-4.5.0> ================================================================================ Best regards Holger --- Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft. https://www.avast.com/antivirus

2 2

[libvirt-users] dmesg shows Intel Virt., lsmod shows kvm_intel; "Host does not [have] virt. options"
by Quincy Wofford 10 Jul '18

10 Jul '18

Hello, I've tried over at IRC and it appears the solution to this problem may not be obvious. I'm working with a Centos7 box on HP ProLiant 380p hardware. The BIOS is a bit outdated, but both Intel Virtualization Options and VT-d are present and enabled in the firmware. Some relevant command outputs below: -bash-4.2$ dmesg | grep Virtualization [ 1.299295] DMAR: Intel(R) Virtualization Technology for Directed I/O -bash-4.2$ lsmod | grep kvm kvm_intel 174841 0 kvm 578518 1 kvm_intel irqbypass 13503 1 kvm sudo virt-install --virt-type kvm --name <my name> --memory 8192 --cdrom <my path>/CentOS-7-x86_64-Everything-1708.iso --disk size=4 --os-variant rhel7 ERROR Host does not support any virtualization options I don't see any options to increase the verbosity of virt-install. Any ideas?

2 2

[libvirt-users] How about giving commit ID in release notes
by Han Han 09 Jul '18

09 Jul '18

Hello developers, Your release notes from libvirt(https://libvirt.org/news.html) are really helpful to our users and QAs. How about giving commit ID of each item in release notes, so that our user can gather more info from release notes. For example,in v4.5.0 release note, add commit ID on each item: capabilities: Provide info about host IOMMU support Capabilities XML now provide information about host IOMMU support. (commit dc34e7) Though we can seach them from git, it is more accurate doing by the authors. -- Best regards, ----------------------------------- Han Han Quality Engineer Redhat. Email: hhan(a)redhat.com Phone: +861065339333

3 2

[libvirt-users] Breaking a virtlockd lock?
by Steve Gaarder 03 Jul '18

03 Jul '18

I have several Qemu/kvm servers running VMs hosted on an NFS share, and am using virtlockd. (lock_manager = "lockd" in qemu.conf) After a power failure, one of the VMs will not start, claiming that it is locked. How do I get out of this? thanks, Steve Gaarder System Administrator, Dept of Mathematics Cornell University, Ithaca, NY, USA gaarder(a)math.cornell.edu

2 1

[libvirt-users] East-west traffic network filter
by Ales Musil 03 Jul '18

03 Jul '18

Hello, I would like to make filter that allows communication only between specified VMs. Those VMs should be specified by their MAC address. The filter should extend clean-traffic but I was not able to get it working with that reference. I have came up with modified clean-traffic which works fine [1]. Is there a way to achieve the same behavior with reference to clean-traffic? Thank you. Best wishes, Ales Musil [1] <filter name='clean-traffic-gateway'>  <filterref filter='no-mac-spoofing'/>  <filterref filter='no-ip-spoofing'/>  <filterref filter='no-arp-spoofing'/>  <rule action='accept' direction='inout' priority='-500'> <mac protocolid='arp'/> </rule>  <rule action='accept' direction='in'> <mac match='yes' srcmacaddr='$GATEWAY_MAC' srcmacmask='$GATEWAY_MAC_MASK' /> </rule>  <rule action='accept' direction='out'> <mac match='yes' dstmacaddr='$GATEWAY_MAC' dstmacmask='$GATEWAY_MAC_MASK' /> </rule>  <filterref filter='no-other-l2-traffic'/>  <filterref filter='qemu-announce-self'/> </filter> -- ALES MUSIL INTERN - rhv network Red Hat EMEA <https://www.redhat.com/> amusil(a)redhat.com IM: amusil <https://red.ht/sig>

3 5

[libvirt-users] Reintroduce "allocate entire disk" checkbox on virt-manager
by Gionatan Danti 28 Jun '18

28 Jun '18

Hi list, on older virt-manager versions (ie: what shipped with RHEL 6), a checkbox called "allocate entire disk" was selectable when configuring a new virtual machine. When checked, it means that the RAW disk image file was entirely allocated, generally issuing a fallocate() call. When unchecked, the disk image was a sparse file, with on-demand space allocation. On new virt-manager versions (ie: what ships with RHEL 7), the checkbox is gone. This means that for creating a sparse allocated file from within the "new vm" wizard, one is forced to use a Qcow2 file (selectable in the global preferences). No sparse RAM images can be created within such wizard. As a heavy consumer of RAW disk files, I would really like to have the checkbox back, especially in RHEL/CentOS 7.x Do you plan to reintroduce it? For RHEL/CentOS, should I open a Bugzilla ticket? Thanks. -- Danti Gionatan Supporto Tecnico Assyoma S.r.l. - www.assyoma.it email: g.danti(a)assyoma.it - info(a)assyoma.it GPG public key ID: FF5F32A8

3 9

[libvirt-users] Virtio-net drivers immune to Nethammer?
by procmem 26 Jun '18

26 Jun '18

Hi I'm a privacy distro maintainer investigating the implications of the newly published nethammer attack [0] on KVM guests particularly the virtio-net drivers. The summary of the paper is that rowhammer can be remotely triggered by feeding susceptible* network driver crafted traffic. This attack can do all kinds of nasty things such as modifying SSL certs on the victim system. * Susceptible drivers are those relying on Intel CAT, uncached memory or the clflush instruction. My question is, do virtio-net drivers do any of these things? *** [0] https://arxiv.org/abs/1805.04956

4 7

[libvirt-users] virsh error: domain is already quiesced
by Jérôme 25 Jun '18

25 Jun '18

Hi all. I'm having issues while creating snapshots. I posted on Stack Exchange [1], but figured I might get more success here. My VM backup script fails while creating the snapshot. virsh snapshot-create-as --domain machine_1 snap --diskspec vda,file=/srv/test/test-snap.qcow2 --disk-only --atomic --no-metadata --quiesce error: Requested operation is not valid: domain is already quiesced Even after a VM reboot, the system is still quiesced and I get the same error. I thought quiesce means FS freeze, but this makes no sense since I can still write to the FS when logged in the faulty VMs. And this would not survive a reboot, right? Could it be a communication issue that makes the host think the GA says the machine is quiesced while it is not? In any case, is there a command to enquire the quiesce state (apart from attempting a snapshot and see if I get an error)? Assuming the faulty VMs went quiesced after a unreproducible error, I could fix that by exiting quiesced state, whatever that means. Is there a virsh command to unquiesce the VM? The whole backup procedure used to work and now it fails on 2 VMs but still works on 2 others and I can't think of any relevant difference between them. Software versions: - Host is Debian Jessie with qemu-kvm 2.8+dfsg-3~bop8+1 from backports. - Guests are Debian Stretch with qemu-guest-agent 2.8+dfsg-6+deb9u4. (For the record, the backup script is on GitHub [2]. Basically, what it does is 1/ create snapshot, 2/ copy, 3/ commit snapshot.) If I remove the `quiesce` option from the snapshot command line, things work smooth. But obviously, this is not ideal. Thanks for any hint. [1] https://serverfault.com/questions/917247/virsh-error-domain-is-already-quie… [2] https://github.com/Nobatek/vmbackup/blob/master/vmbackup -- Jérôme

2 2

[libvirt-users] How libvirt interacts with dhcpd?
by Daniel. 20 Jun '18

20 Jun '18

Hi everybody, I'm using libvirt together with xCAT, on the same host, for testing purposes. xCAT install and manages dhcpd. How libvirt interacts with dhcpd? And if doens't how does the dhcp server of libvirt works, plus where I can find information on how to troubleshot it? Regards, -- “If you're going to try, go all the way. Otherwise, don't even start. ..." Charles Bukowski

2 6

[libvirt-users] Network problem when rebooting Fedora qemu/kvm guest on Gentoo host
by Dan Johansson 17 Jun '18

17 Jun '18

Hello, I have some problem with some of my qemu/kvm guests running Fedora on a Gentoo host where my Gentoo guests works without problem. The problem that I have is that when I reboot (shutdown -r now) the Fedora guest "loses" (ifconfig does not show a IP-address) their network connections. The Gentoo guests reboots without problem. All the guests have same HW-configuration, only Name/DiskImage/MAC- addresses differ. Here some technical details: Host: Distribution Gentoo Kernel 4.9.95-gentoo Qemu app-emulation/qemu-2.11.1-r2 USE="aio bzip2 caps curl fdt filecaps gnutls jpeg lzo ncurses nls pin-upstream-blobs png sdl seccomp vhost-net vnc xattr" QEMU_SOFTMMU_TARGETS="x86_64" QEMU_USER_TARGETS="x86_64" libvirt app-emulation/libvirt-4.3.0 USE="caps dbus libvirtd nls qemu udev" Guest Distribution Fedora 28 Kernel 4.16.15-300.fc28.x86_64 Networkmanager NetworkManager.x86_64 1:1.10.8-1.fc28 Any suggestions? -- Dan Johansson *************************************************** This message is printed on 100% recycled electrons! ***************************************************

1 0

[libvirt-users] Feedback for a new application NIMO using the libvirt API
by Jay Mehta 13 Jun '18

13 Jun '18

Hello folks, A while back I developed VM instance monitoring tool "NIMO", Nova (Openstack's project Nova) Instance Monitor. The need to develop Nimo arise with requirement to monitor VM's boot stages. A VM boot undergoes multiple stages, like creating block device, mounting root filesystem, mounting local filesystem, DHCP lease acquiring, post-install activities, etc., and it could fail or stuck at any of these stages. It would be good to have a monitor in place to identify which stage a VM is in while booting and how much time it takes at each stage. A special need for such tool arise on the cloud space, where end-user do not have access to log on to the hypervisor. It also helps to people who build custom VM images and add a lot of tasks in post install script and would like to know performance of each step. The below is the github link and it has an architecture diagram. https://github.com/jay-g-mehta/nimo I would love to hear all of your response and feel free to use it, extend it. Thanks, Jay

1 0

[libvirt-users] "virsh" list
by Bo YU 13 Jun '18

13 Jun '18

Hello, I installed libvirt from package manager(debian apt) and want to modify feture in it, so i git clone from https://libvirt.org/git/?p=libvirt.git;a=summary But now i have trouble to start virsh. I have traced the email: https://www.redhat.com/archives/libvirt-users/2017-February/msg00074.html Here is output of command below: strace -o libvirt.log -f -s 1000 /usr/sbin/libvirtd https://github.com/yuzibo/linux-programming/blob/master/tmp/libvirt.log Here: sudo gdb -p $(pgrep libvirtd) (gdb) t a a bt [New LWP 14781] [New LWP 14782] [New LWP 14783] [New LWP 14784] [New LWP 14785] [New LWP 14786] [New LWP 14787] [New LWP 14788] [New LWP 14789] [New LWP 14790] [New LWP 14791] [New LWP 14792] [New LWP 14793] [New LWP 14794] [New LWP 14795] [New LWP 14796] [New LWP 14799] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x00007fcf4c75f67d in poll () at ../sysdeps/unix/syscall-template.S:84 84../sysdeps/unix/syscall-template.S: (no such file or directory)没有那个文件或目录. "" Thread 18 (Thread 0x7fcf3a4e8700 (LWP 14799)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007fcf4e17ee36 in virCondWait (c=c@entry=0x7fcf3400cc90, m=m@entry=0x7fcf3400cc50) at util/virthread.c:154 #2 0x00007fcf405498a0 in udevEventHandleThread (opaque=<optimized out>) at node_device/node_device_udev.c:1606 #3 0x00007fcf4e17ec02 in virThreadHelper (data=<optimized out>) at util/virthread.c:206 #4 0x00007fcf4ca26494 in start_thread (arg=0x7fcf3a4e8700) at pthread_create.c:333 #5 0x00007fcf4c768acf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 17 (Thread 0x7fcf3b315700 (LWP 14796)): #0 0x00007fcf4c75f67d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x00007fcf4c77917e in __poll_chk (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>, fdslen=<optimized out>) at poll_chk.c:27 #2 0x00007fcf4e10f281 in poll (__timeout=-1, __nfds=<optimized out>, __fds=0x7fcf3b3143b0) at /usr/include/x86_64-linux-gnu/bits/poll2.h:41 #3 virCommandProcessIO (cmd=cmd@entry=0x7fcf34015d30) --Type <return> to continue, or q <return> to quit--- at util/vircommand.c:2085 #4 0x00007fcf4e1134ea in virCommandRun (cmd=0x7fcf34015d30, exitstatus=exitstatus@entry=0x7fcf3b314924) at util/vircommand.c:2316 #5 0x00007fcf3e239fca in virQEMUCapsInitQMPCommandRun ( cmd=cmd@entry=0x7fcf34015b10, forceTCG=forceTCG@entry=false) at qemu/qemu_capabilities.c:4262 #6 0x00007fcf3e23f4b9 in virQEMUCapsInitQMP (qmperr=0x7fcf3b314970, runGid=<optimized out>, runUid=<optimized out>, libDir=<optimized out>, qemuCaps=0x7fcf340159d0) at qemu/qemu_capabilities.c:4318 #7 virQEMUCapsNewForBinaryInternal (hostArch=VIR_ARCH_X86_64, binary=0x7fcf3403e160 "/usr/local/bin/qemu-system-x86_64", libDir=<optimized out>, runUid=<optimized out>, runGid=<optimized out>, microcodeVersion=166, kernelVersion=0x7fcf3404e120 "4.14.0+ #1 SMP Sun Nov 26 15:17:48 HKT 2017") at qemu/qemu_capabilities.c:4405 #8 0x00007fcf3e23f793 in virQEMUCapsNewData (binary=<optimized out>, privData=<optimized out>) at qemu/qemu_capabilities.c:4447 #9 0x00007fcf4e18ca1e in virFileCacheNewData ( name=0x7fcf3403e160 "/usr/local/bin/qemu-system-x86_64", cache=0x7fcf3404ddf0) at util/virfilecache.c:219 #10 virFileCacheValidate (cache=cache@entry=0x7fcf3404ddf0, name=name@entry=0x7fcf3403e160 "/usr/local/bin/qemu-system-x86_64", data=data@entry=0x7fcf3b314ae0) at util/virfilecache.c:290 ---Type <return> to continue, or q <return> to quit--- #11 0x00007fcf4e18cd77 in virFileCacheLookup ( cache=cache@entry=0x7fcf3404ddf0, name=name@entry=0x7fcf3403e160 "/usr/local/bin/qemu-system-x86_64") at util/virfilecache.c:323 #12 0x00007fcf3e23f9ee in virQEMUCapsCacheLookup ( cache=cache@entry=0x7fcf3404ddf0, binary=0x7fcf3403e160 "/usr/local/bin/qemu-system-x86_64") at qemu/qemu_capabilities.c:4583 #13 0x00007fcf3e23fc94 in virQEMUCapsInitGuest (guestarch=VIR_ARCH_X86_64, hostarch=VIR_ARCH_X86_64, cache=0x7fcf3404ddf0, caps=0x7fcf3404ded0) at qemu/qemu_capabilities.c:736 #14 virQEMUCapsInit (cache=0x7fcf3404ddf0) at qemu/qemu_capabilities.c:971 #15 0x00007fcf3e28d3a0 in virQEMUDriverCreateCapabilities ( driver=driver@entry=0x7fcf3401cbd0) at qemu/qemu_conf.c:1101 #16 0x00007fcf3e2d0be2 in qemuStateInitialize (privileged=true, callback=<optimized out>, opaque=<optimized out>) at qemu/qemu_driver.c:851 #17 0x00007fcf4e2b0bff in virStateInitialize (privileged=<optimized out>, callback=0x564b91ad18a0 <daemonInhibitCallback>, opaque=0x564b933e4540) at libvirt.c:662 #18 0x0000564b91ad18fb in daemonRunStateInit (opaque=0x564b933e4540) at remote/remote_daemon.c:802 #19 0x00007fcf4e17ec02 in virThreadHelper (data=<optimized out>) at util/virthread.c:206 ---Type <return> to continue, or q <return> to quit--- #20 0x00007fcf4ca26494 in start_thread (arg=0x7fcf3b315700) at pthread_create.c:333 #21 0x00007fcf4c768acf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 16 (Thread 0x7fcf3bb16700 (LWP 14795)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007fcf4e17ee36 in virCondWait (c=c@entry=0x564b933f1bc8, m=m@entry=0x564b933f1ba0) at util/virthread.c:154 #2 0x00007fcf4e17f983 in virThreadPoolWorker ( opaque=opaque@entry=0x564b933d6d80) at util/virthreadpool.c:124 #3 0x00007fcf4e17ebd8 in virThreadHelper (data=<optimized out>) at util/virthread.c:206 #4 0x00007fcf4ca26494 in start_thread (arg=0x7fcf3bb16700) at pthread_create.c:333 #5 0x00007fcf4c768acf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 15 (Thread 0x7fcf3c317700 (LWP 14794)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007fcf4e17ee36 in virCondWait (c=c@entry=0x564b933f1bc8, ---Type <return> to continue, or q <return> to quit--- m=m@entry=0x564b933f1ba0) at util/virthread.c:154 #2 0x00007fcf4e17f983 in virThreadPoolWorker ( opaque=opaque@entry=0x564b933d6cc0) at util/virthreadpool.c:124 #3 0x00007fcf4e17ebd8 in virThreadHelper (data=<optimized out>) at util/virthread.c:206 #4 0x00007fcf4ca26494 in start_thread (arg=0x7fcf3c317700) at pthread_create.c:333 #5 0x00007fcf4c768acf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 14 (Thread 0x7fcf3cb18700 (LWP 14793)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007fcf4e17ee36 in virCondWait (c=c@entry=0x564b933f1bc8, m=m@entry=0x564b933f1ba0) at util/virthread.c:154 #2 0x00007fcf4e17f983 in virThreadPoolWorker ( opaque=opaque@entry=0x564b933d6c00) at util/virthreadpool.c:124 #3 0x00007fcf4e17ebd8 in virThreadHelper (data=<optimized out>) at util/virthread.c:206 #4 0x00007fcf4ca26494 in start_thread (arg=0x7fcf3cb18700) at pthread_create.c:333 #5 0x00007fcf4c768acf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 ---Type <return> to continue, or q <return> to quit--- Thread 13 (Thread 0x7fcf3d319700 (LWP 14792)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007fcf4e17ee36 in virCondWait (c=c@entry=0x564b933f1bc8, m=m@entry=0x564b933f1ba0) at util/virthread.c:154 #2 0x00007fcf4e17f983 in virThreadPoolWorker ( opaque=opaque@entry=0x564b933d6b20) at util/virthreadpool.c:124 #3 0x00007fcf4e17ebd8 in virThreadHelper (data=<optimized out>) at util/virthread.c:206 #4 0x00007fcf4ca26494 in start_thread (arg=0x7fcf3d319700) at pthread_create.c:333 #5 0x00007fcf4c768acf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 12 (Thread 0x7fcf3db1a700 (LWP 14791)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007fcf4e17ee36 in virCondWait (c=c@entry=0x564b933f1bc8, m=m@entry=0x564b933f1ba0) at util/virthread.c:154 #2 0x00007fcf4e17f983 in virThreadPoolWorker ( opaque=opaque@entry=0x564b933d6a60) at util/virthreadpool.c:124 #3 0x00007fcf4e17ebd8 in virThreadHelper (data=<optimized out>) ---Type <return> to continue, or q <return> to quit--- at util/virthread.c:206 #4 0x00007fcf4ca26494 in start_thread (arg=0x7fcf3db1a700) at pthread_create.c:333 #5 0x00007fcf4c768acf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 11 (Thread 0x7fcf41df5700 (LWP 14790)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007fcf4e17ee36 in virCondWait (c=c@entry=0x564b933e49b8, m=m@entry=0x564b933e48f0) at util/virthread.c:154 #2 0x00007fcf4e17f944 in virThreadPoolWorker ( opaque=opaque@entry=0x564b933d5ca0) at util/virthreadpool.c:124 #3 0x00007fcf4e17ebd8 in virThreadHelper (data=<optimized out>) at util/virthread.c:206 #4 0x00007fcf4ca26494 in start_thread (arg=0x7fcf41df5700) at pthread_create.c:333 #5 0x00007fcf4c768acf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 10 (Thread 0x7fcf425f6700 (LWP 14789)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 ---Type <return> to continue, or q <return> to quit--- #1 0x00007fcf4e17ee36 in virCondWait (c=c@entry=0x564b933e49b8, m=m@entry=0x564b933e48f0) at util/virthread.c:154 #2 0x00007fcf4e17f944 in virThreadPoolWorker ( opaque=opaque@entry=0x564b933d5b00) at util/virthreadpool.c:124 #3 0x00007fcf4e17ebd8 in virThreadHelper (data=<optimized out>) at util/virthread.c:206 #4 0x00007fcf4ca26494 in start_thread (arg=0x7fcf425f6700) at pthread_create.c:333 #5 0x00007fcf4c768acf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 9 (Thread 0x7fcf42df7700 (LWP 14788)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007fcf4e17ee36 in virCondWait (c=c@entry=0x564b933e49b8, m=m@entry=0x564b933e48f0) at util/virthread.c:154 #2 0x00007fcf4e17f944 in virThreadPoolWorker ( opaque=opaque@entry=0x564b933d5bc0) at util/virthreadpool.c:124 #3 0x00007fcf4e17ebd8 in virThreadHelper (data=<optimized out>) at util/virthread.c:206 #4 0x00007fcf4ca26494 in start_thread (arg=0x7fcf42df7700) at pthread_create.c:333 #5 0x00007fcf4c768acf in clone () ---Type <return> to continue, or q <return> to quit--- at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 8 (Thread 0x7fcf435f8700 (LWP 14787)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007fcf4e17ee36 in virCondWait (c=c@entry=0x564b933e49b8, m=m@entry=0x564b933e48f0) at util/virthread.c:154 #2 0x00007fcf4e17f944 in virThreadPoolWorker ( opaque=opaque@entry=0x564b933d5b00) at util/virthreadpool.c:124 #3 0x00007fcf4e17ebd8 in virThreadHelper (data=<optimized out>) at util/virthread.c:206 #4 0x00007fcf4ca26494 in start_thread (arg=0x7fcf435f8700) at pthread_create.c:333 #5 0x00007fcf4c768acf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 7 (Thread 0x7fcf43df9700 (LWP 14786)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007fcf4e17ee36 in virCondWait (c=c@entry=0x564b933e49b8, m=m@entry=0x564b933e48f0) at util/virthread.c:154 #2 0x00007fcf4e17f944 in virThreadPoolWorker ( opaque=opaque@entry=0x564b933d5d60) at util/virthreadpool.c:124 ---Type <return> to continue, or q <return> to quit--- #3 0x00007fcf4e17ebd8 in virThreadHelper (data=<optimized out>) at util/virthread.c:206 #4 0x00007fcf4ca26494 in start_thread (arg=0x7fcf43df9700) at pthread_create.c:333 #5 0x00007fcf4c768acf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 6 (Thread 0x7fcf445fa700 (LWP 14785)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007fcf4e17ee36 in virCondWait (c=c@entry=0x564b933e4918, m=m@entry=0x564b933e48f0) at util/virthread.c:154 #2 0x00007fcf4e17f983 in virThreadPoolWorker ( opaque=opaque@entry=0x564b933d5b00) at util/virthreadpool.c:124 #3 0x00007fcf4e17ebd8 in virThreadHelper (data=<optimized out>) at util/virthread.c:206 #4 0x00007fcf4ca26494 in start_thread (arg=0x7fcf445fa700) at pthread_create.c:333 #5 0x00007fcf4c768acf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 5 (Thread 0x7fcf44dfb700 (LWP 14784)): #0 pthread_cond_wait@@GLIBC_2.3.2 () ---Type <return> to continue, or q <return> to quit--- at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007fcf4e17ee36 in virCondWait (c=c@entry=0x564b933e4918, m=m@entry=0x564b933e48f0) at util/virthread.c:154 #2 0x00007fcf4e17f983 in virThreadPoolWorker ( opaque=opaque@entry=0x564b933d5bc0) at util/virthreadpool.c:124 #3 0x00007fcf4e17ebd8 in virThreadHelper (data=<optimized out>) at util/virthread.c:206 #4 0x00007fcf4ca26494 in start_thread (arg=0x7fcf44dfb700) at pthread_create.c:333 #5 0x00007fcf4c768acf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 4 (Thread 0x7fcf455fc700 (LWP 14783)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007fcf4e17ee36 in virCondWait (c=c@entry=0x564b933e4918, m=m@entry=0x564b933e48f0) at util/virthread.c:154 #2 0x00007fcf4e17f983 in virThreadPoolWorker ( opaque=opaque@entry=0x564b933d5ca0) at util/virthreadpool.c:124 #3 0x00007fcf4e17ebd8 in virThreadHelper (data=<optimized out>) at util/virthread.c:206 #4 0x00007fcf4ca26494 in start_thread (arg=0x7fcf455fc700) at pthread_create.c:333 ---Type <return> to continue, or q <return> to quit--- #5 0x00007fcf4c768acf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 3 (Thread 0x7fcf45dfd700 (LWP 14782)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007fcf4e17ee36 in virCondWait (c=c@entry=0x564b933e4918, m=m@entry=0x564b933e48f0) at util/virthread.c:154 #2 0x00007fcf4e17f983 in virThreadPoolWorker ( opaque=opaque@entry=0x564b933d5d60) at util/virthreadpool.c:124 #3 0x00007fcf4e17ebd8 in virThreadHelper (data=<optimized out>) at util/virthread.c:206 #4 0x00007fcf4ca26494 in start_thread (arg=0x7fcf45dfd700) at pthread_create.c:333 #5 0x00007fcf4c768acf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 2 (Thread 0x7fcf465fe700 (LWP 14781)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007fcf4e17ee36 in virCondWait (c=c@entry=0x564b933e4918, m=m@entry=0x564b933e48f0) at util/virthread.c:154 #2 0x00007fcf4e17f983 in virThreadPoolWorker ( ---Type <return> to continue, or q <return> to quit--- opaque=opaque@entry=0x564b933d5e20) at util/virthreadpool.c:124 #3 0x00007fcf4e17ebd8 in virThreadHelper (data=<optimized out>) at util/virthread.c:206 #4 0x00007fcf4ca26494 in start_thread (arg=0x7fcf465fe700) at pthread_create.c:333 #5 0x00007fcf4c768acf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 1 (Thread 0x7fcf4eb4dd40 (LWP 14780)): #0 0x00007fcf4c75f67d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x00007fcf4e122684 in poll (__timeout=-1, __nfds=6, __fds=<optimized out>) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46 #2 virEventPollRunOnce () at util/vireventpoll.c:641 #3 0x00007fcf4e121371 in virEventRunDefaultImpl () at util/virevent.c:327 #4 0x00007fcf4e243e4d in virNetDaemonRun (dmn=0x564b933e4540) at rpc/virnetdaemon.c:850 #5 0x0000564b91ad0d5e in main (argc=<optimized out>, argv=<optimized out>) at remote/remote_daemon.c:1460 Thank you in advance!

1 0

[libvirt-users] Amazon s3 as libvirt storage pool
by Shashwat shagun 11 Jun '18

11 Jun '18

Namaste, i want to use Minio (open source amazon S3 compatible object storage) as libvirt storage pool. is such thing possible? i apologize if this is a stupid question. if not then can i write some driver for it? -- Regards, Shashwat Shagun

2 1

[libvirt-users] create a domain failed using virt-install
by lizhuoyao 08 Jun '18

08 Jun '18

hi everyone: Sorry to bother you again! my order: virt-install --virt-type kvm -n centos -r 1024 --disk centos.img,format=qcow2,size=10 --cdrom /home/CentOS-7-aarch64-Everything.iso the failed log: qemu-kvm: -device pcie-root-port,port=0x8,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x1:MSI-X is not supported by interrupt controller. my environment: arm64 platform;centos7.5 for arm; libvirt-3.9.0;qemu-2.10.0;virt-install-1.4.3 Do you have met the issue ever?Any suggestion? -- Have a good day

2 1

[libvirt-users] Are more then one overlay possible without recieving a "Permission denied"?
by Xen Mann 07 Jun '18

07 Jun '18

I've created a backing chain like this. FirstFollr.ovl is an overlay to Base.img and so on. Base.img (ok - Win 10 Installation starting) FirstFloor.ovl (ok - Win 10 Installation starting) SecondFloor.ovl (permission denied -> Base.img) => assumed Bug Roof.ovl (permission denied -> Base.img) => assumed Bug Using virsh / virt-manager, I can only start Base and FirstFloor. Starting Second and Roof are failing. What's wrong? Details are described in: https://bugzilla.redhat.com/show_bug.cgi?id=1588373 System infos: Compiled against library: libvirt 4.0.0 Using library: libvirt 4.0.0 Using API: QEMU 4.0.0 Running hypervisor: QEMU 2.11.1 Ubuntu 18.04 LTS (Dell Precission Tower 3620)

1 0