- Users - libvirt List Archives

[libvirt-users] query regarding domstats option with virsh
by Jain, Manish (HP Software) 18 Feb '16

18 Feb '16

Hi, I am looking for the information w.r.t domstats command line option of virsh tool. 1> This command line option is available with which version of libvirt. 2> How to get Guest's disk related information in case storage pool does not exist on host. Thanks and Regards, Manish

2 2

[libvirt-users] bug in Libvirt(-python)?
by Dennis Jacobfeuerborn 17 Feb '16

17 Feb '16

Hi, I've noticed that the capacity of the disk in one of my VMs is completely wrongly reported by the python api. The image was transfered using scp but the transfer was aborted and now the api show a strange value: [root@virt83 ~]# du -h /var/lib/libvirt/images/test-disk1 706M /var/lib/libvirt/images/test-disk1 [root@virt83 ~]# ls -lh /var/lib/libvirt/images/test-disk1 -rw-r--r--. 1 root root 706M 3. Nov 20:03 /var/lib/libvirt/images/test-disk1 [root@virt83 ~]# qemu-img info /var/lib/libvirt/images/test-disk1 image: /var/lib/libvirt/images/test-disk1 file format: raw virtual size: 705M (739573760 bytes) disk size: 705M Notice how that raw image is seen with a size of 705M by ls, du and qemu-img however when I get a blockinfo using libvirt-python using the blockInfo() call I get this: {'source': '/var/lib/libvirt/images/test-disk1', 'target': 'vda'} [2423276348619671841L, 739577856L, 739577856L] Obviously the first value (capacity) is way too large to be correct. Any ideas if this is a bug or if there is something else going on? This is a CentOS 7 system with the following versions: [root@virt83 ~]# cat /etc/redhat-release CentOS Linux release 7.1.1503 (Core) [root@virt83 ~]# rpm -q libvirt libvirt-1.2.8-16.el7_1.4.x86_64 [root@virt83 ~]# rpm -q libvirt-python libvirt-python-1.2.8-7.el7_1.1.x86_64 Regards, Dennis

2 1

[libvirt-users] glib2 head file error when build libvirt with wireshark support
by Han Han 17 Feb '16

17 Feb '16

I compile the latest libvirt from fedora rawhide, but failed. The version of my software: wireshark-devel-2.0.1-2.fc24.x86_64 glib2-2.47.5-2.fc24.x86_64 gcc-5.1.1-4.fc23.x86_64 binutils-2.26-10.fc24.x86_64 The error as following: # ./autogen.sh --prefix=/usr && make ..... wireshark/src/plugin.c:5:21: fatal error: gmodule.h: No such file or directory compilation terminated. Makefile:2442: recipe for target 'wireshark/src/wireshark_src_libvirt_la-plugin.lo' failed make[3]: *** [wireshark/src/wireshark_src_libvirt_la-plugin.lo] Error 1 make[3]: *** Waiting for unfinished jobs.... In file included from wireshark/src/packet-libvirt.c:27:0: /usr/include/wireshark/epan/proto.h:40:18: fatal error: glib.h: No such file or directory compilation terminated. Makefile:2435: recipe for target 'wireshark/src/wireshark_src_libvirt_la-packet-libvirt.lo' failed make[3]: *** [wireshark/src/wireshark_src_libvirt_la-packet-libvirt.lo] Error 1 make[3]: Leaving directory '/root/libvirt/tools' Makefile:2104: recipe for target 'all' failed make[2]: *** [all] Error 2 make[2]: Leaving directory '/root/libvirt/tools' Makefile:2002: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/root/libvirt' Makefile:1897: recipe for target 'all' failed make: *** [all] Error 2 When I disable wireshark support, make successfully. # ./configure --without-wireshark-dissector && make But the file gmodule.h and glib.h exist on my system: # locate gmodule.h /usr/include/glib-2.0/gmodule.h # locate glib.h /usr/include/glib-2.0/glib.h /usr/share/gtk-doc/html/glib/glib.html /usr/src/kernels/4.5.0-0.rc0.git1.1.fc24.x86_64/include/config/blk/dev/bsglib.h /usr/src/kernels/4.5.0-0.rc3.git3.1.fc24.x86_64/include/config/blk/dev/bsglib.h

4 5

[libvirt-users] [issue] Accessing SMBIOSTable in FreeBSD Kernel
by sundareswaram pv 16 Feb '16

16 Feb '16

1 0

[libvirt-users] Configure QCow2 L2 Cache through virt domain XML
by Stefano Bonicatti 15 Feb '16

15 Feb '16

Hello, i was wondering if it is possible to configure the l2 cache of a qcow2 image through the domain xml. I cannot find any documentation about it... the only thing i've found is that i can pass custom options to qemu command line through the <qemu:commandline> tag, but, to my understanding, that would mean entirely remove the <disk> tag for the image and rewrite it as a list of args for the command line. Isn't there an easier way? An example of what i'm speaking about is: file=hd.qcow2,l2-cache-size=4194304,refcount-cache-size=262144

1 0

[libvirt-users] Getting "unknown device type" when attaching NPIV (vHBA) to vm
by Vaknin, Rami 13 Feb '16

13 Feb '16

Hi, I'm trying to attach a host FC HBA to VM (NPIV). Running ovirt 3.5 on CentOS 6.7, libvirt-0.10.2-46.el6_6.6.x86_64, I created vHBA using nodedev-create command - see below HBA and vHBA. I wrote a vdsm hook which appends the vHBA xml stanza to the devices xml element but the vm start starts without the vHBA device. Also, when trying to attach the device manually as a live device - I get: 2016-02-01 21:30:24.216+0000: 129764: debug : qemuDomainObjBeginJobInternal:847 : Starting job: modify (async=none) 2016-02-01 21:30:24.216+0000: 129764: error : virDomainDeviceDefParse:8136 : XML error: unknown device type Could you please help? virsh # nodedev-dumpxml scsi_host6 <device> <name>scsi_host6</name> <parent>pci_0000_08_00_0</parent> <capability type='scsi_host'> <host>6</host> <capability type='fc_host'> <wwnn>20000024ff57d848</wwnn> <wwpn>21000024ff57d848</wwpn> <fabric_wwn>20018c604f101321</fabric_wwn> </capability> <capability type='vport_ops' /> </capability> </device> virsh # nodedev-dumpxml scsi_host15 <device> <name>scsi_host15</name> <parent>scsi_host6</parent> <capability type='scsi_host'> <host>15</host> <capability type='fc_host'> <wwnn>5001a4a84992572a</wwnn> <wwpn>5001a4a76965d7b8</wwpn> <fabric_wwn>20018c604f101321</fabric_wwn> </capability> </capability> </device> The xml I appends: <devices> ... <device> <name>scsi_host16</name> <parent>scsi_host7</parent> <capability type="scsi_host"> <host>16</host> <capability type="fc_host"> <wwnn>5001a4a8cd978a73</wwnn> <wwpn>5001a4afa86a7378</wwpn> <fabric_wwn>20018c604f101411</fabric_wwn> </capability> </capability> </device> <device> <name>scsi_host15</name> <parent>scsi_host6</parent> <capability type="scsi_host"> <host>15</host> <capability type="fc_host"> <wwnn>5001a4a84992572a</wwnn> <wwpn>5001a4a76965d7b8</wwpn> <fabric_wwn>20018c604f101321</fabric_wwn> </capability> </capability> </device> </devices> Thanks, Rami.

3 4

[libvirt-users] Domain cannot talk to itself unless virbr0 is in promiscuous mode
by David Raison 12 Feb '16

12 Feb '16

Hi We have the following situation: A hypervisor using KVM-Qemu/libvirt with a single VM. The VM has the internal IP 192.168.122.151 on the default network pool using virbr0 on the hypervisor. We've set up netfilter rules to DNAT requests on one IP of the hypervisor to the VM. So, first of all, forwarding to the internal IP range is allowed: > $IPTABLES -I FORWARD -m state -d 192.168.122.0/24 --state > NEW,RELATED,ESTABLISHED -j ACCEPT Then we're forwarding a few ports from the hypervisor's public IP to the VM, imaps being one of them: > Chain PREROUTING (policy ACCEPT 2606 packets, 169K bytes) pkts bytes > target prot opt in out source destination 142 8048 DNAT tcp -- * * > 0.0.0.0/0 a.b.c.145 tcp dpt:993 to:192.168.122.151 Since the VM is also doing SMTP, we need it to send out mail via a dedicated IPv4, which we achieve through the following SNAT rule: > Chain POSTROUTING (policy ACCEPT 1121 packets, 77556 bytes) pkts > bytes target prot opt in out source destination 81 6262 SNAT all -- * > * 192.168.122.151 0.0.0.0/0 to:a.b.c.145 Now, on this mailserver, we're also running a roundcube instance. For authentication, roundcube connects to the imaps port of the local dovecot instance. In order for the SSL certificate check to succeed, it needs to do so using the actual domain name, and cannot use "localhost" or the loopback IP address. The problem is that, given the above iptables rules, connecting from inside the VM to itself via the hypervisor's external interface doesn't work. The connection simply times out, logging reveals they're not getting forwarded. We've added logging to iptables and testing in promisc mode vs. not-promisc: This is what gets logged when virbr0 is not in promisc mode: > Feb 11 19:12:31 hyper kernel: [199815.004207] prerouting imaps: > IN=virbr0 OUT= PHYSIN=vnet0 > MAC=fe:54:00:17:c8:2a:52:54:00:17:c8:2a:08:00 SRC=192.168.122.151 > DST=a.b.c.d.145 LEN=60 TOS=0x10 PREC=0x00 TTL=64 ID=40689 DF > PROTO=TCP SPT=43460 DPT=993 WINDOW=29200 RES=0x00 SYN URGP=0 And this when the device is in promisc mode: > Feb 11 19:14:33 hyper kernel: [199937.674189] prerouting imaps: > IN=virbr0 OUT= PHYSIN=vnet0 > MAC=fe:54:00:17:c8:2a:52:54:00:17:c8:2a:08:00 SRC=192.168.122.151 > DST=a.b.c.d.145 LEN=60 TOS=0x10 PREC=0x00 TTL=64 ID=2244 DF PROTO=TCP > SPT=43461 DPT=993 WINDOW=29200 RES=0x00 SYN URGP=0 > Feb 11 19:14:33 hyper kernel: [199937.674221] forwarded imaps: IN=virbr0 > OUT=virbr0 PHYSIN=vnet0 MAC=52:54:00:17:c8:2a:52:54:00:17:c8:2a:08:00 > SRC=192.168.122.151 DST=192.168.122.151 LEN=60 TOS=0x10 PREC=0x00 TTL=63 > ID=2244 DF PROTO=TCP SPT=43461 DPT=993 WINDOW=29200 RES=0x00 SYN URGP=0 > Feb 11 19:14:33 hyper kernel: [199937.674766] forwarded imaps: IN=virbr0 > OUT=virbr0 PHYSIN=vnet0 MAC=52:54:00:17:c8:2a:52:54:00:17:c8:2a:08:00 > SRC=192.168.122.151 DST=192.168.122.151 LEN=52 TOS=0x10 PREC=0x00 TTL=63 > ID=2245 DF PROTO=TCP SPT=43461 DPT=993 WINDOW=229 RES=0x00 ACK URGP=0 Another workaround we found is to disable iptables on the bridge interface. > root@hyper:~# echo 0 > /proc/sys/net/bridge/bridge-nf-call-iptables But I do not consider this a solution, merely a workaround. I do not understand why the forward rule mentioned above does not apply to the situation where IN and OUT are both virbr0? Thank you for any advice, David -- TenTwentyFour S.à r.l. W: www.tentwentyfour.lu T: +352 20 211 1024 F: +352 20 211 1023 9, avenue des Hauts-Fourneaux L-4362 Esch/Alzette

1 0

[libvirt-users] Unable to create raw volume on netfs storage (Operation not permitted)
by Benjamin Weik 11 Feb '16

11 Feb '16

Hello, we are trying to create a new setup with a centralized storage server. Currently we are running multiple "All-in-One" hosts using raw volumes stored on the local disk of the server. I tried it first with samba but it did not work so currently I have configured it as NFS. This is my current setup: For Storage: OS: Ubuntu 16.04 beta (to match vHost version), IP: 123.123.123.2 NFS: v1.2.8 Samba: v4.3.3 For vHost: OS: Ubuntu 16.04 beta (as the Package in Ubuntu 14.04 has still a bug that prevents mounting of samba shares) IP: 123.123.123.3 Libvirt: v2.21 Qemu: 2.5 Both are simply connected via switched network for testing. So on the Storage server I created a user and a group called vstorage (uid:1000,gid:500) Then created a folder /pool owned by this user, permission 777 And exported it via nfs in /etc/exports: /pool 123.123.123.3(rw,async,no_subtree_check,all_squash,anonuid=1000,anongid=500) On the vHost I defined the pool via XML: <pool type='netfs'> <name>pool</name> <source> <host name='123.123.123.2'/> <dir path='pool'/> <format type='nfs'/> </source> <target> <path>/var/lib/virt/images</path> </target> </pool> When I try to define a volume in the pool, it will always fail if raw format (default) is used. virsh vol-create-as --pool pool --name test --capacity 512M error: Failed to create vol test error: Failed to create file '/var/lib/virt/images/test': Operation not permitted In /var/log/syslog I can find the following libvirtd[889]: cannot chown '/var/lib/virt/images/test' to (0, 0): Operation not permitted libvirtd[889]: Failed to create file '/var/lib/virt/images/test': Operation not permitted When I try it with a different format, like qcow2 it is working fine: virsh vol-create-as --pool pool --name test --capacity 512M --format qcow2 Vol test created I am unable to find the reason for this problem, it also took me quite a while find out that this is a format issue as the error message is actually not really helpful. I found a small guide on setting up KVM from IBM and they are using NFS with raw images, so I'm not sure where the error is https://www.ibm.com/developerworks/library/l-using-kvm/ Maybe someone could shed some light on this? The same error message happens btw. with Samba. Best regards, Benjamin Weik

2 1

[libvirt-users] Networking with qemu/kvm+libvirt
by Andre Goree 10 Feb '16

10 Feb '16

I have some questions regarding the way that networking is handled via qemu/kvm+libvirt -- my apologies in advance if this is not the proper mailing list for such a question. I am trying to determine how exactly I can manipulate traffic from a _guest's_ NIC using iptables on the _host_. On the host, there is a bridged virtual NIC that corresponds to the guest's NIC. That interface does not have an IP setup on it on the host, however within the vm itself the IP is configured and everything works as expected. During my testing, I've seemingly determined that traffic from the vm does NOT traverse iptables on the host, but I _can_ in fact see the traffic via tcpdump on the host. This seems odd to me, unless the traffic is passed on during interaction with the kernel, and thus never actually reaches iptables. I've gone as far as trying to log via iptables any and all traffic traversing the guest's interface on the host, but to no avail (iptables does not see any traffic from the guest's NIC on the host). Is this the way it's supposed to work? And if so, is there any way I can do IP/port redirection silently on the _host_? Thanks in advance for any insight that anyone can share :) -- Andre Goree -=-=-=-=-=- Email - andre at drenet.net Website - http://www.drenet.net PGP key - http://www.drenet.net/pubkey.txt -=-=-=-=-=-

2 5

[libvirt-users] GPU passthrough - MSI R9 380 4GB, works only ONCE
by David Hlacik 09 Feb '16

09 Feb '16

Hello guys, I have a problem when using my MSI R9 380 4G graphic card as GPU passthrough with KVM. At the first linux boot (Fedora 23) I am able to successfully start virtual machine and it works! However if i will shut down virtual machine and start it again - the screen will stay blank! So far I have been able to find on the internet that some graphic cards just can not reinitialize itself when there is no power off/on, which could be the case of mine as well. Also I am very much surprised that this graphic card has no UEFI rom! Any help would be appreciated [root@brutus-coreos ~]# virsh start winos1 Domain winos1 started dmesg output after second boot of the virtual machine winos1 [ 338.346776] input: Microsoft Microsoft® Nano Transceiver v2.0 as /devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.0/0003:045E:0800.0007/input/input23 [ 338.397715] hid-generic 0003:045E:0800.0007: input,hidraw0: USB HID v1.11 Keyboard [Microsoft Microsoft® Nano Transceiver v2.0] on usb-0000:00:14.0-10/input0 [ 338.402847] input: Microsoft Microsoft® Nano Transceiver v2.0 as /devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.1/0003:045E:0800.0008/input/input24 [ 338.403605] hid-generic 0003:045E:0800.0008: input,hidraw1: USB HID v1.11 Mouse [Microsoft Microsoft® Nano Transceiver v2.0] on usb-0000:00:14.0-10/input1 [ 338.419310] input: Microsoft Microsoft® Nano Transceiver v2.0 as /devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.2/0003:045E:0800.0009/input/input25 [ 338.470855] hid-generic 0003:045E:0800.0009: input,hiddev0,hidraw2: USB HID v1.11 Device [Microsoft Microsoft® Nano Transceiver v2.0] on usb-0000:00:14.0-10/input2 [ 754.055255] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=io+mem:owns=none [ 754.087966] xhci_hcd 0000:00:14.0: remove, state 4 [ 754.087982] usb usb2: USB disconnect, device number 1 [ 754.090201] xhci_hcd 0000:00:14.0: USB bus 2 deregistered [ 754.090399] xhci_hcd 0000:00:14.0: remove, state 1 [ 754.090409] usb usb1: USB disconnect, device number 1 [ 754.090413] usb 1-2: USB disconnect, device number 2 [ 754.090964] usb 1-8: USB disconnect, device number 3 [ 754.091904] usb 1-10: USB disconnect, device number 4 [ 754.222281] xhci_hcd 0000:00:14.0: USB bus 1 deregistered [ 755.359725] vfio_ecap_init: 0000:01:00.0 hiding ecap 0x19@0x270 [ 755.359733] vfio_ecap_init: 0000:01:00.0 hiding ecap 0x1b@0x2d0 [ 755.384598] vfio-pci 0000:03:00.0: enabling device (0000 -> 0002) [ 755.485743] vfio_ecap_init: 0000:03:00.0 hiding ecap 0x1e@0x154 screen is blank - I have to reboot my Linux machine in order to be able to start this virtual machine once again David Hlacik +420-777-307-745 | david(a)hlacik.cz [image: View David Hlacik's profile on LinkedIn] <http://cz.linkedin.com/in/hlacik>

2 2