- Users - libvirt List Archives

[libvirt-users] Attach libvirt guest to an existing openvswitch port
by Ivan Borodin 21 Nov '16

21 Nov '16

Good day gentlemen. I am building a study project and trying to configure openvswitch vlans outside libvirt by means of openvswitch itself. Somehow with interface types 'bridge' and 'network', libvirt does attach domain to the existing port specified in <target dev=''/>, wiping the exixting settings and always deletes this port upon domain shutdown, thus making me loose ovs configuration. Could you, please, tell me how should I configure an interface or libvirt itself to avoid this libvirt's greedines. libvirt 2.4.0 Thak you. Ivan.

2 1

[libvirt-users] export a cert
by lejeczek 21 Nov '16

21 Nov '16

hi everybody I'm browsing around but probably missing that obvious little thing - exporting certs to pem format with ipa command toolkit - that must be there somewhere, right? thanks, L.

2 1

[libvirt-users] ergodox keyboard not working on USB hostdev passthrough
by Paul Handy 16 Nov '16

16 Nov '16

I'm using a bit of a different keyboard, the infinity ergodox [ https://input.club/devices/infinity-ergodox/] It functions just fine as a keyboard on my host computer, but when I try to bind it to the guest, nothing seems to happen. lsusb gives its ID: Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub *Bus 005 Device 003: ID 1c11:b04d* Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 258a:0001 Bus 001 Device 002: ID 093a:2521 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub So, I made a file, hostdev-1c11:b04d.xml, which contains the following: <hostdev mode='subsystem' type='usb' > <source> <vendor id='0x1c11'/> <product id='0xb04d'/> </source> </hostdev> Note, I have had this same xml inside the domain's xml, but have pulled it out separately so that I could run: virsh attach-device linux-x86_64 hostdev-1c11:b04d.xml It appears to attach the device, as it becomes visible in the domain's lsusb: Bus 001 Device 001: ID 1d6b:0002 Bus 004 Device 001: ID 1d6b:0001 *Bus 003 Device 003: ID 1c11:b04d * Bus 003 Device 001: ID 1d6b:0001 Bus 002 Device 003: ID 093a:2521 Bus 002 Device 002: ID 258a:0001 Bus 002 Device 001: ID 1d6b:0001 The mouse works just fine. I bought a cheap keyboard to test out, and it works just fine. My pet keyboard, however, doesn't work on the guest. Nothing seems to register. Any ideas here what I could do? Drivers? ROM's? I've tried both SeaBIOS and OVMF with no difference in outcome, and while this appears to be a hardware problem, I don't know where to begin. Thanks, Paul

2 1

[libvirt-users] BroadCom NIC not adding as PassThrough device
by Tahir Masood 16 Nov '16

16 Nov '16

Hi Guys, I am trying to add a Broadcom Physical NIC to a virtual Machine as Passthrough device. However I am getting following error. Error starting domain: unsupported configuration: host doesn't support passthrough of host PCI devices Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 88, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 124, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 83, in newfn ret = fn(self, *args, **kwargs) File "/usr/share/virt-manager/virtManager/domain.py", line 1404, in startup self._backend.create() File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1035, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirtError: unsupported configuration: host doesn't support passthrough of host PCI devices libvirt allows to appply the changes to the VM xml configurations, but gives error the moment I try to start the VM. I have tried following approaches. 1- Open Virt-Manager, Shutdown VM, edit VM , add PCI hardware device , locate BroadCom NIC, apply changes. Then I restart the VM. 2- Also tried to add following XML tags one by one using 'virsh edit', but got same error. Tag -1 <hostdev mode='subsystem' type='pci' managed='yes'> <source> <address domain='0x0000' bus='0x02' slot='0x00' function='0x1'/> </source> </hostdev> Tag -2 <interface type='hostdev' managed='yes'> <source> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x1'/> </source> </interface> The detail of the BroadCOm NIC are as follows. 02:00.1 Ethernet controller: Broadcom Limited NetXtreme II BCM5709 Gigabit Ethernet (rev 20) What would it take to add this NIC to VM as Passthrough Device? Regards, Tahir Masood Senior Engineer, xFlow Research Inc. +92-300-9779473 <mailto:tahir.masood@xflowresearch.com> tahir.masood(a)xflowresearch.com <http://www.xflowresearch.com/> www.xflowresearch.com

2 1

[libvirt-users] how to use command 'guest-file-open' for Windows server 2012R2 vm
by 刘梦可 09 Nov '16

09 Nov '16

hello, I am using libvirt 1.2.17 on CentOS 7.2 - kernel 3.10.0-327.13.1.el7.x86_64. The command guest-file-open failed to open with error "this feature or command is not currently supported", the detail is as below: virsh qemu-agent-command instance-00000015 "{\"execute\":\"guest-file-open\", \"arguments\":{\"path\":\"\tmp.txt\",\"mode\":\"r\"}}" error: internal error: unable to execute QEMU agent command 'guest-file-open': this feature or command is not currently supported. The guest instance-00000015 is a Windows server 2012R2, and I installed the qemu-guest-agent by the file qemu-ga-x64.msi from virtio-win-0.1.126. It can be running in guest. Doesn't the qemu-guest-agent in Windows VM support guest-file-* commands? How or when can I use the command guest-file-* command? Thanks very much!! -mkliu28

2 2

[libvirt-users] sttic vnet device for guest
by Anton Gorlov 08 Nov '16

08 Nov '16

Can i assign static vnet* device for some guests?

4 9

[libvirt-users] Guest startup process blocks if a hook's child process is still running (i.e : after forking)
by Nicolas Roy-Renaud 08 Nov '16

08 Nov '16

I've been having issues with KVM lately where I sometimes put my host into sleep while a guest is still running, which prevents it from waking up properly. This is somewhat expected due to my setup, but I have mistakenly done this more than once and could use a workaround to stop this from happening. So I've been trying to setup a libvirt hook to fork an instance of systemd-inhibit when the start hook is called and keep it running until the shutdown hook is called. This seems to work well when I run the hook script in a normal bash shell, but running it through libvirt simply blocks the starting process until systemd-inhibit quits. Here's the script : LOCK_FILE="/tmp/vfio-lock-$OBJECT" if [ "$OPERATION" == "start" ]; then ( touch "$LOCK_FILE"; systemd-inhibit --what="sleep" \ --who="libvirt" \ --mode="block" \ inotifywait -qq -e delete "$LOCK_FILE" ) & disown $! exit fi if [ "$OPERATION" == "shutdown" ]; then rm "$LOCK_FILE" fi Is there some way to make it so libvirt sees the hook script exiting and carries on with the rest of its guest startup process even after a process fork or would that require changes in the internal hook handling functions? - Nicolas

1 1

[libvirt-users] Sharing network namespace between containers
by Harish Vishwanath 08 Nov '16

08 Nov '16

Hello Based on the lxc driver documentation, I am trying to create an xml to share an existing network namespace with another container. I am running libvirt 1.2.15. Here is the xml: <domain type='lxc' xmlns:lxc='http://libvirt.org/schemas/domain/lxc/1.0'> <name>nt</name> <uuid>43c00192-e114-4e29-8ce7-4b5487f60a75</uuid> <memory unit='KiB'>65536</memory> <currentMemory unit='KiB'>65536</currentMemory> <vcpu placement='static'>1</vcpu> <cputune> <shares>2000</shares> </cputune> <resource> <partition>/apphosting.partition</partition> </resource> <os> <type arch='x86_64'>exe</type> <init>/sbin/init</init> </os> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/lib/libvirt/libvirt_lxc</emulator> <filesystem type='mount' accessmode='passthrough'> <source dir='/work/repo-lxc/nt/rootfs_mnt'/> <target dir='/'/> </filesystem> <filesystem type='mount' accessmode='squash'> <driver type='path' wrpolicy='immediate'/> <source dir='/local/local1/core_dir/nt'/> <target dir='/local/local1/core_dir'/> </filesystem>  <console type='pty'> <target type='lxc' port='0'/> </console> </devices> * <lxc:namespace>* * <lxc:sharenet type='netns' value='node'/>* * </lxc:namespace>* </domain> However, the virsh edit is unable to save this file: error: XML document failed to validate against schema: Unable to validate doc against /usr/share/libvirt/schemas/domain.rng Element domain has extra content: namespace Failed. Try again? [y,n,i,f,?]: Is this supported in libvirt 1.2.15 - the document doesnt specify a minimum version of libvirt. Appreciate your help. Regards, Harish

3 4

[libvirt-users] virtual wlan0
by Michael Ströder 07 Nov '16

07 Nov '16

HI! My goal is to run a virtualized access point with hostapd. Is it possible to use the host's WIFI interface in a VM created with libvirt? I can add the interface in bridged mode but it appears just as normal eth1 without wireless extensions. Ciao, Michael.

2 1

[libvirt-users] pci-assign fails with read error on config-space file
by Henning Schild 02 Nov '16

02 Nov '16

Hey, i am running an unusual setup where i assign pci devices behind the back of libvirt. I have two options to do that: 1. a wrapper script for qemu that takes care of suid-root and appends arguments for pci-assign 2. virsh qemu-monitor-command ... 'device_add pci-assign...' I know i should probably not be doing this, it is a workaround to introduce fine-grained pci-assignment in an openstack setup, where vendor and device id are not enough to pick the right device for a vm. In both cases qemu will crash with the following output: > qemu: hardware error: pci read failed, ret = 0 errno = 22 followed by the usual machine state dump. With strace i found it to be a failing read on the config space file of my device. /sys/bus/pci/devices/0000:xx:xx.x/config A few reads out of that file succeeded, as well as accesses on vendor etc. Manually launching a qemu with the pci-assign works without a problem, so i "blame" libvirt and the cgroup environment the qemu ends up in. So i put a bash into the exact same cgroup setup - next to a running qemu, expecting a dd or hexdump on the config-space file to fail. But from that bash i can read the file without a problem. Has anyone seen that problem before? Right now i do not know what i am missing, maybe qemu is hitting some limits configured for the cgroups or whatever. I can not use pci-assign from libvirt, but if i did would it configure cgroups in a different way or relax some limits? What would be a good next step to debug that? Right now i am looking at kernel event traces, but the machine is pretty big and so is the trace. That assignment used to work and i do not know how it broke, i have tried combinations of several kernels, versions of libvirt and qemu. (kernel 3.18 and 4.4, libvirt 1.3.2 and 2.0.0, and qemu 2.2.1 and 2.7) All combinations show the same problem, even the ones that work on other machines. So when it comes to software versions the problem could well be caused by a software update of another component, that i got with the package manager and did not compile myself. It is a debian 8.6 with all recent updates installed. My guess would be that systemd could have an influence on cgroups or limits causing such a problem. regards, Henning

5 7