August 2018 - Users - libvirt List Archives

[libvirt-users] [virtual interface] detach interface during boot succeed with no changes
by Yalan Zhang 08 Sep '22

08 Sep '22

Hi guys, when I detach an interface from vm during boot (vm boot not finished), it always fail. I'm not sure if there is an existing bug. I have confirmed with someone that for disk, there is similar behavior, if this is also acceptable? # virsh destroy rhel7.2; virsh start rhel7.2 ;sleep 2; virsh detach-interface rhel7.2 network 52:54:00:98:c4:a0; sleep 2; virsh dumpxml rhel7.2 |grep /interface -B9 Domain rhel7.2 destroyed Domain rhel7.2 started Interface detached successfully <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </controller> <interface type='network'> <mac address='52:54:00:98:c4:a0'/> <source network='default' bridge='virbr0'/> <target dev='vnet0'/> <model type='rtl8139'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> When I detach after the vm boot, expand the sleep time to 10, it will succeed. # virsh destroy rhel7.2; virsh start rhel7.2 ;sleep 10; virsh detach-interface rhel7.2 network 52:54:00:98:c4:a0; sleep 2; virsh dumpxml rhel7.2 |grep /interface -B9 Domain rhel7.2 destroyed Domain rhel7.2 started Interface detached successfully ------- Best Regards, Yalan Zhang IRC: yalzhang Internal phone: 8389413

3 4

[libvirt-users] Add Virtlyst to the list of libvirt users
by Daniel Nicoletti 23 Sep '20

23 Sep '20

Hi, I've just released v1.0.0 of Virtlyst[1] a web tool to manage VMs using Qt/C++/Cutelyst https://dantti.wordpress.com/2018/04/19/announcing-virtlyst-a-web-interface… Thanks. 1 - https://github.com/cutelyst/Virtlyst -- Daniel Nicoletti KDE Developer - http://dantti.wordpress.com

4 5

[libvirt-users] Question about disabling UFO on guest
by Bao Nguyen 05 Aug '20

05 Aug '20

Hello everyone, I would like to ask a question regarding to disable UFO of virtio vNIC in my guest. I have read the document at https://libvirt.org/formatdomain.html *host* The csum, gso, tso4, tso6, ecn and ufo attributes with possible values on and off can be used to turn off host offloading options. By default, the supported offloads are enabled by QEMU. *Since 1.2.9 (QEMU only)* The mrg_rxbuf attribute can be used to control mergeable rx buffers on the host side. Possible values are on (default) and off. *Since 1.2.13 (QEMU only)* *guest* The csum, tso4, tso6, ecn and ufo attributes with possible values on and off can be used to turn off guest offloading options. By default, the supported offloads are enabl ed by QEMU. *Since 1.2.9 (QEMU only)* Then I disabled UFO on my vNIC on guest as the following configuration <devices> <interface type='network'> <source network='default'/> <target dev='vnet1'/> <model type='virtio'/> <driver name='vhost' txmode='iothread' ioeventfd='on' event_idx='off' queues='5' rx_queue_size='256' tx_queue_size='256'> *<host gso='off' ufo='off' />* *<guest ufo='off'/>* </driver> </interface> </devices> Then I reboot my node to get the change effect and it works. However, can I disable the UFO without touching the host OS? or it always has to disable on both host and guest like that? Thanks, Brs, Natsu

2 1

[libvirt-users] Libvirt access control drivers
by Anastasiya Ruzhanskaya 21 Nov '18

21 Nov '18

Hello! According to the documentation access control drivers are not in really "good condition". There is a polkit, but it can distinguish users only according the pid. However, I have met some articles about more fine-grained control and about selinux drivers for libvirt? So, what is the status now? Should I implement something by myself if I want access based on login, are their instructions how to write these drivers or there is smth already?

3 18

[libvirt-users] live migration via unix socket
by David Vossel 12 Oct '18

12 Oct '18

Hey, Over in KubeVirt we're investigating a use case where we'd like to perform a live migration within a network namespace that does not provide libvirtd with network access. In this scenario we would like to perform a live migration by proxying the migration through a unix socket to a process in another network namespace that does have network access. That external process would live on every node in the cluster and know how to correctly route connections between libvirtds. virsh example of an attempted migration via unix socket. virsh migrate --copy-storage-all --p2p --live --xml domain.xml my-vm qemu+unix:///system?socket=destination-host-proxy-sock In this example, the src libvirtd is able to establish a connection to the destination libvirtd via the unix socket proxy. However, the migration-uri appears to require either tcp or rdma network connection. If I force the migration-uri to be a unix socket, I receive an error [1] indicating that qemu+unix is not a valid transport. Technically with qemu+kvm I believe what we're attempting should be possible (even though it is inefficient). Please correct me if I'm wrong. Is there a way to achieve this migration via unix socket functionality this using Libvirt? Also, is there a reason why the migration uri is limited to tcp/rdma Thanks! - David [1] https://github.com/libvirt/libvirt/blob/master/src/qemu/qemu_migration.c#L2…

4 7

[libvirt-users] Snapshot overlay-file deletion
by Gionatan Danti 31 Aug '18

31 Aug '18

Hi list, issuing the command "virsh blockcommit --delete --pivot" (on a previously created external snapshot/overlay) returns an error regarding an unsupported flag warning stating "error: unsupported flags (0x2)". I need to manually "rm" the affected file after the blockcommit. A similar issue was reported many years ago here [1]. Am I missing something, or is the "--delete" flag not supported? Thanks. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1001475 -- 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

2 2

[libvirt-users] Setting up port forwarding to guests on nat network
by Rhys Ferris 31 Aug '18

31 Aug '18

Hello all, I’m currently trying to figure out how to forward ports to guests that are on a NAT Network. I have followed the directions on https://wiki.libvirt.org/page/Networking under the “Forwarding Incoming Connections” Section and get connection refused when attempting to connect. System: Ubuntu Server 18.04.1 Virsh / LibVirtd Version: 4.0.0 Here’s the contents of /etc/libvirt/hooks/qemu #!/bin/bash # IMPORTANT: Change the "VM NAME" string to match your actual VM Name. # In order to create rules to other VMs, just duplicate the below block and configure # it accordingly. if [ "${1}" = "testy" ]; then # Update the following variables to fit your setup GUEST_IP='10.128.10.100' GUEST_PORT='22' HOST_PORT='2588' if [ "${2}" = "stopped" ] || [ "${2}" = "reconnect" ]; then /sbin/iptables -D FORWARD -o virbr0 -d $GUEST_IP -j ACCEPT /sbin/iptables -t nat -D PREROUTING -p tcp --dport $HOST_PORT -j DNAT --to $GUEST_IP:$GUEST_PORT fi if [ "${2}" = "start" ] || [ "${2}" = "reconnect" ]; then /sbin/iptables -I FORWARD -o virbr0 -d $GUEST_IP -j ACCEPT /sbin/iptables -t nat -I PREROUTING -p tcp --dport $HOST_PORT -j DNAT --to $GUEST_IP:$GUEST_PORT fi fi Here’s my network XML <network> <name>olympus</name> <uuid>3b0d968c-8166-42f7-8109-e5f0317cab42</uuid> <forward mode='nat'> <nat> <port start='1024' end='65535'/> </nat> </forward> <bridge name='virbr1' stp='on' delay='0'/> <mac address='52:54:00:bb:18:6b'/> <ip address='10.128.10.1' netmask='255.255.255.0'> <dhcp> <range start='10.128.10.2' end='10.128.10.254'/> <host mac='52:54:00:8d:f5:0c' name='testy' ip='10.128.10.100'/> </dhcp> </ip> </network> And here’s the results of iptables -L -vt nat: BEFORE VM BOOT: Chain PREROUTING (policy ACCEPT 46615 packets, 6618K bytes) pkts bytes target prot opt in out source destination Chain INPUT (policy ACCEPT 46615 packets, 6618K bytes) pkts bytes target prot opt in out source destination Chain OUTPUT (policy ACCEPT 198K packets, 18M bytes) pkts bytes target prot opt in out source destination Chain POSTROUTING (policy ACCEPT 198K packets, 18M bytes) pkts bytes target prot opt in out source destination 24 1812 RETURN all -- any any 10.128.10.0/24 base-address.mcast.net/24 0 0 RETURN all -- any any 10.128.10.0/24 255.255.255.255 17 1020 MASQUERADE tcp -- any any 10.128.10.0/24 !10.128.10.0/24 masq ports: 1024-65535 15 1700 MASQUERADE udp -- any any 10.128.10.0/24 !10.128.10.0/24 masq ports: 1024-65535 0 0 MASQUERADE all -- any any 10.128.10.0/24 !10.128.10.0/24 22 1666 RETURN all -- any any 192.168.122.0/24 base-address.mcast.net/24 0 0 RETURN all -- any any 192.168.122.0/24 255.255.255.255 0 0 MASQUERADE tcp -- any any 192.168.122.0/24 !192.168.122.0/24 masq ports: 1024-65535 8 1168 MASQUERADE udp -- any any 192.168.122.0/24 !192.168.122.0/24 masq ports: 1024-65535 0 0 MASQUERADE all -- any any 192.168.122.0/24 !192.168.122.0/24 AFTER VM BOOT Chain PREROUTING (policy ACCEPT 2 packets, 120 bytes) pkts bytes target prot opt in out source destination 0 0 DNAT tcp -- any any anywhere anywhere tcp dpt:2588 to:10.128.10.100:22 Chain INPUT (policy ACCEPT 2 packets, 120 bytes) pkts bytes target prot opt in out source destination Chain OUTPUT (policy ACCEPT 18 packets, 1263 bytes) pkts bytes target prot opt in out source destination Chain POSTROUTING (policy ACCEPT 18 packets, 1263 bytes) pkts bytes target prot opt in out source destination 24 1812 RETURN all -- any any 10.128.10.0/24 base-address.mcast.net/24 0 0 RETURN all -- any any 10.128.10.0/24 255.255.255.255 17 1020 MASQUERADE tcp -- any any 10.128.10.0/24 !10.128.10.0/24 masq ports: 1024-65535 15 1700 MASQUERADE udp -- any any 10.128.10.0/24 !10.128.10.0/24 masq ports: 1024-65535 0 0 MASQUERADE all -- any any 10.128.10.0/24 !10.128.10.0/24 22 1666 RETURN all -- any any 192.168.122.0/24 base-address.mcast.net/24 0 0 RETURN all -- any any 192.168.122.0/24 255.255.255.255 0 0 MASQUERADE tcp -- any any 192.168.122.0/24 !192.168.122.0/24 masq ports: 1024-65535 8 1168 MASQUERADE udp -- any any 192.168.122.0/24 !192.168.122.0/24 masq ports: 1024-65535 0 0 MASQUERADE all -- any any 192.168.122.0/24 !192.168.122.0/24 And lastly heres what actually happens on attempt to SSH: rhys@odin:~$ ssh rhys(a)172.16.99.170 -p 2258 ssh: connect to host 172.16.99.170 port 2258: Connection refused rhys@odin:~$ The connection refused is instant, not a timeout. I’ve ensured that ufw is disabled. Any help appreciated. I just can’t figure this out. Sent from Mail for Windows 10

2 3

[libvirt-users] ceph rbd pool and libvirt manageability (virt-install)
by Jelle de Jong 28 Aug '18

28 Aug '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello everybody, I created a rbd pool and activated it, but I can't seem to create volumes in it with virsh or virt-install? # virsh pool-dumpxml myrbdpool <pool type='rbd'> <name>myrbdpool</name> <uuid>2d786f7a-2df3-4d79-ae60-1535bcf1c6b5</uuid> <capacity unit='bytes'>6997998301184</capacity> <allocation unit='bytes'>10309227031</allocation> <available unit='bytes'>6977204658176</available> <source> <host name='ceph01.powercraft.nl' port='6789'/> <host name='ceph02.powercraft.nl' port='6789'/> <host name='ceph03.powercraft.nl' port='6789'/> <name>libvirt-pool</name> <auth type='ceph' username='libvirt'> <secret uuid='029a334e-ed57-4293-bb99-ffafa8867122'/> </auth> </source> </pool> # virt-install --version 1.0.1 # virsh --version 1.2.9 I ended using virsh edit ceph-test.powercraft.nl and making creating the disk manually. <disk type='network' device='disk'> <auth username='libvirt'> <secret type='ceph' uuid='029a334e-ed57-4293-bb99-ffafa8867122'/> </auth> <source protocol='rbd' name='libvirt-pool/kvm01-storage'> <host name='ceph01.powercraft.nl' port='6789'/> <host name='ceph02.powercraft.nl' port='6789'/> <host name='ceph03.powercraft.nl' port='6789'/> </source> <target dev='vdc' bus='virtio'/> </disk> I use virt-install a lot to define, import and undefine domains, how can I use virt-install to manage my rdb disks? Kind regards, Jelle de Jong -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iJwEAQECAAYFAlV1xlQACgkQ1WclBW9j5HkbPQP+PjNrzvlqysslOp2Yk7wH4Mxy 2sh2dn96G0KOAHEeEn3BN6IWlnD1TADZbHdpTtMwkdv48Xwn0sP1s+3QDM4pb3gP n+z+dVxS8FouDIy/eiso3IBCj3g4TWbEX8ZHqs3jKqe0lZgAXBzB9xYSUowcEBrZ ddkPbr8p8ozWyOG+9V8= =lkK7 -----END PGP SIGNATURE-----

2 3

[libvirt-users] OVMF / UEFI boot abnormally
by Allence 28 Aug '18

28 Aug '18

Hey guys, today I use ovmf to start win10 guests, my monitor is not bright But is it normal for me to use seabios? why? The next message is my detailed settings. ovmf: os: <loader readonly='yes' type='pflash'>/root/OVMF_CODE.fd</loader> <nvram>/root/OVMF_VARS.fd</nvram> vga: <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.0,romfile=/root/10de:1b06:19da:1474.dump,multifunction=on'/> bios: os: <loader readonly='yes' type='rom'>/usr/share/qemu/bios.bin</loader> vga: <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.0,romfile=/root/us.dump,multifunction=on,x-vga=on'/> And this is my kvm environment: qemu: 2.12.0 libvirt: 4.14 kernel: 4.17.2 host: Lfs-8.2(as similar as ubuntu)

1 0

[libvirt-users] Download image to libvirt storage pool
by Shashwat shagun 27 Aug '18

27 Aug '18

Is there any function in libvirt (golang SDK) to download image to libvirt storage pool from path?

2 1

[libvirt-users] libvirt and virt-manager - Unable to complete install: 'internal error: unsupported input bus usb'
by Eduardo Lúcio Amorim Costa 23 Aug '18

23 Aug '18

I'm trying create a virtual machine using Xen as hypervisor and virt-manager (libvirt) as the management module. When trying to create the virtual machine I am getting the following error: " Unable to complete install: 'internal error: unsupported input bus usb' " ERROR DETAILS: Unable to complete install: 'internal error: unsupported input bus usb' Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/create.py", line 2276, in _do_async_install guest.start_install(meter=meter) File "/usr/share/virt-manager/virtinst/guest.py", line 461, in start_install doboot, transient) File "/usr/share/virt-manager/virtinst/guest.py", line 397, in _create_guest domain = self.conn.createXML(install_xml or final_xml, 0) File "/usr/lib/python3.7/site-packages/libvirt.py", line 3717, in createXML if ret is None:raise libvirtError('virDomainCreateXML() failed', conn=self) libvirt.libvirtError: internal error: unsupported input bus usb NOTE I: The deploy process follows the instructions here https://www.youtube.com/watch?v=BwkmDM-Gpzc and here https://wiki.centos.org/HowTos/Xen/Xen4QuickStart . NOTE II: Xen Hypervisor uses a CentOS 7 as "domu". MORE INFORMATION ABOUT THE PROBLEM HERE: https://unix.stackexchange.com/q/464186/61742 Thanks! =D

2 3

[libvirt-users] Guest startup delay options ignored
by Inception Hosting 23 Aug '18

23 Aug '18

Hi Folks, been searching around for a while on this and see similar issues reported going back a number of years without solution. The START_DELAY=(number) seems to be completely ignored in /etc/sysconfig/libvirt-guests which is unfortunate as it means everything starts at once without control. This is fine on NVMe based servers however on the older spinning disks the I/O is creating significant issues. Is anyone aware of any other methods to achieve a start up delay for guest virtual machines on boot? Thanks. Anthony.

2 2

[libvirt-users] Efficacy of jitterentropy RNG on qemu-kvm Guests
by procmem 17 Aug '18

17 Aug '18

Hello. I'm a distro maintainer and was wondering about the efficacy of entropy daemons like haveged and jitterentropyd in qemu-kvm. One of the authors of haveged [0] pointed out if the hardware cycles counter is emulated and deterministic, and thus predictible. He therefore does not recommend using HAVEGE on those systems. Is this the case with KVM's counters? PS. I will be setting VM CPU settings to host-passthrough. Bonus: Also if anyone knows the answer to this question about Xen please let me know because its the other main platform we support and they don't have the luxury of virtio-rng in PVH mode. Thanks. [0] https://github.com/BetterCrypto/Applied-Crypto-Hardening/commit/cf7cef7a870…

3 5

[libvirt-users] qemu guest agent
by Cobin Bluth 15 Aug '18

15 Aug '18

Hello Libvirt-Users! I have a quick question about the qemu guest agent. Is it possible to use the guest agent from inside the guest in order to query the name of its own domain? For example, I use a base-image.qcow2 with a baked-in hostname. I would like to include a little tool in my guest image to change the hostname to the name of the domain. Is this sort of thing possible? -Cobin

2 1

[libvirt-users] New Application to add to web site
by Matthew 11 Aug '18

11 Aug '18

Hello, Could you please add the OpenVM Dashboard to the list of applications that use libvirt. Below is the URL and description. Also, to all the developers who put libvirt-php together...THANK YOU! Thanks, Matthew Penning URL: https://openvm.tech <https://openvm.tech/> Description: The OpenVM Dashboard is an open source HTML5 and PHP based web interface for the KVM and QEMU hypervisor. It is designed to be a easy-to-use management platform allowing users to create and manage domains (virtual machines) using the libvirt-php module.

1 0

Re: [libvirt-users] Windows Guest I/O performance issues (already using virtio) (Matt Schumacher)
by Allence 09 Aug '18

09 Aug '18

I think performance is not just about your xml, the host system will have a bigger impact. Maybe you can see this link: Https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/ht… >Date: Wed, 8 Aug 2018 17:35:11 +0000 >From: Matt Schumacher <matt.s(a)aptalaska.com> >To: "libvirt-users(a)redhat.com" <libvirt-users(a)redhat.com> >Subject: [libvirt-users] Windows Guest I/O performance issues (already > using virtio) >Message-ID: <30EE4896-CF82-4E23-82D5-0C56B38F5E09(a)aptalaska.com> >Content-Type: text/plain; charset="utf-8" > >List, > >I have a number of Windows 2016 servers I am deploying, but I?m having some I/O performance issues. I have done all of the obvious things like virtio drivers, but am finding there is more performance to be found with hyper-v extensions, how we virtualize the hardware clock, and iothreads. I?m using ZVOLs to back the VM, and I?m using 4k block sizes, which seems to offer the best 4k random read/write performance (mail and database workloads), but maybe I?m missing something at this layer too. > >Questions: > > > 1. Does my VM config look reasonable for the latest releases of windows? Are there features I should be using that will help performance? > 2. Why does the hypervclock timer make so much performance difference in windows VMs? > 3. Does my virtualized CPU model make sense? I defined Haswell-noTSX-IBRS and libvirt added the features. > 4. Which kernel branch offers the best stability and performance? > 5. Are there performance gains in using UEFI booting the windows guest and defining ?<blockio logical_block_size='4096' physical_block_size='4096'/>?? Perhaps better block size consistency through to the zvol? > > >Here is my setup: > >48 core Haswell CPU >192G Ram >Linux 4.14.61 or 4.9.114 (testing both) >ZFS file system on optane SSD drive or ZFS file system on dumb HBA with 8 spindles of 15k disks (testing both) >4k block size zvol for virtual machines >32G arc cache > >Here is my VM: > ><domain type='kvm' id='12'> > <name>testvm</name> > <memory unit='KiB'>33554432</memory> > <currentMemory unit='KiB'>33554432</currentMemory> > <vcpu placement='static'>12</vcpu> > <iothreads>1</iothreads> > <os> > <type arch='x86_64' machine='pc-i440fx-2.12'>hvm</type> > <boot dev='cdrom'/> > <boot dev='hd'/> > </os> > <features> > <acpi/> > <hyperv> > <relaxed state='on'/> > <vapic state='on'/> > <spinlocks state='on' retries='8191'/> > <vpindex state='on'/> > <runtime state='on'/> > <synic state='on'/> > <reset state='on'/> > <vendor_id state='on' value='KVM Hv'/> > </hyperv> > </features> > <cpu mode='custom' match='exact' check='full'> > <model fallback='forbid'>Haswell-noTSX-IBRS</model> > <topology sockets='1' cores='6' threads='2'/> > <feature policy='require' name='vme'/> > <feature policy='require' name='f16c'/> > <feature policy='require' name='rdrand'/> > <feature policy='require' name='hypervisor'/> > <feature policy='require' name='arat'/> > <feature policy='disable' name='spec-ctrl'/> > <feature policy='require' name='xsaveopt'/> > <feature policy='require' name='abm'/> > </cpu> > <clock offset='localtime'> > <timer name='rtc' tickpolicy='catchup'/> > <timer name='pit' tickpolicy='delay'/> > <timer name='hpet' present='yes'/> > <timer name='hypervclock' present='yes'/> > </clock> > <on_poweroff>destroy</on_poweroff> > <on_reboot>restart</on_reboot> > <on_crash>destroy</on_crash> > <devices> > <emulator>/usr/bin/qemu-system-x86_64</emulator> > <disk type='block' device='disk'> > <driver name='qemu' type='raw' cache='none' io='native' ioeventfd='on' iothread='1'/> > <source dev='/dev/zvol/datastore/vm/testvm-vda'/> > <backingStore/> > <target dev='vda' bus='virtio'/> > <alias name='virtio-disk0'/> > <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> > </disk> > <disk type='file' device='cdrom'> > <driver name='qemu'/> > <target dev='hdc' bus='ide'/> > <readonly/> > <alias name='ide0-1-0'/> > <address type='drive' controller='0' bus='1' target='0' unit='0'/> > </disk> > <controller type='ide' index='0'> > <alias name='ide'/> > <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> > </controller> > <controller type='usb' index='0' model='piix3-uhci'> > <alias name='usb'/> > <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> > </controller> > <controller type='pci' index='0' model='pci-root'> > <alias name='pci.0'/> > </controller> > <controller type='virtio-serial' index='0'> > <alias name='virtio-serial0'/> > <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> > </controller> > <interface type='bridge'> > <source bridge='lan'/> > <target dev='vnet0'/> > <model type='virtio'/> > <alias name='net0'/> > <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> > </interface> > <channel type='unix'> > <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-12-testvm/org.qemu.guest_agent.0'/> > <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/> > <alias name='channel0'/> > <address type='virtio-serial' controller='0' bus='0' port='1'/> > </channel> > <input type='tablet' bus='usb'> > <alias name='input0'/> > <address type='usb' bus='0' port='1'/> > </input> > <input type='mouse' bus='ps2'> > <alias name='input1'/> > </input> > <input type='keyboard' bus='ps2'> > <alias name='input2'/> > </input> > <graphics type='vnc' port='5901' autoport='no' listen='0.0.0.0'> > <listen type='address' address='0.0.0.0'/> > </graphics> > <video> > <model type='cirrus' vram='16384' heads='1' primary='yes'/> > <alias name='video0'/> > <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> > </video> > <memballoon model='none'/> > </devices> > <seclabel type='dynamic' model='dac' relabel='yes'> > <label>+0:+100</label> > <imagelabel>+0:+100</imagelabel> > </seclabel> ></domain>

1 0

[libvirt-users] Mount URL as cdrom/iso KVM/QEMU
by Inception Hosting 09 Aug '18

09 Aug '18

Hi Folks, According to the examples in http://libvirt.org/formatdomain.html#elementsDisks it should be possible to mount an iso /url as a cdrom, the example given is: </disk> <disk type='network' device='cdrom'> <driver name='qemu' type='raw'/> <source protocol="http" name="url_path"> <host name="hostname" port="80"/> </source> <target dev='hde' bus='ide' tray='open'/> <readonly/> </disk> I am unable to get this to work at all and wondered if I am just missing something obvious: Boot failed: Could not read from CDROM (code 0003) Actual XML in use snippet: <disk type='network' device='cdrom'> <driver name='qemu' type='raw'/> <source protocol="http" name="/debian-cd/current/amd64/iso-cd/debian-9.5.0-amd64-netinst.iso"> <host name="mirror.bytemark.co.uk" port="80"/> </source> <target dev='hdb' bus='ide' tray='open'/> <readonly/> </disk> libvirtd (libvirt) 3.9.0 QEMU emulator version 2.10.0 Is anyone able to offer any assistance or tips? I have tried putting the complete path including fqdn in the url_path as well, with and without http:// Many Thanks. Anthony.

3 8

[libvirt-users] Windows Guest I/O performance issues (already using virtio)
by Matt Schumacher 08 Aug '18

08 Aug '18

List, I have a number of Windows 2016 servers I am deploying, but I’m having some I/O performance issues. I have done all of the obvious things like virtio drivers, but am finding there is more performance to be found with hyper-v extensions, how we virtualize the hardware clock, and iothreads. I’m using ZVOLs to back the VM, and I’m using 4k block sizes, which seems to offer the best 4k random read/write performance (mail and database workloads), but maybe I’m missing something at this layer too. Questions: 1. Does my VM config look reasonable for the latest releases of windows? Are there features I should be using that will help performance? 2. Why does the hypervclock timer make so much performance difference in windows VMs? 3. Does my virtualized CPU model make sense? I defined Haswell-noTSX-IBRS and libvirt added the features. 4. Which kernel branch offers the best stability and performance? 5. Are there performance gains in using UEFI booting the windows guest and defining “<blockio logical_block_size='4096' physical_block_size='4096'/>”? Perhaps better block size consistency through to the zvol? Here is my setup: 48 core Haswell CPU 192G Ram Linux 4.14.61 or 4.9.114 (testing both) ZFS file system on optane SSD drive or ZFS file system on dumb HBA with 8 spindles of 15k disks (testing both) 4k block size zvol for virtual machines 32G arc cache Here is my VM: <domain type='kvm' id='12'> <name>testvm</name> <memory unit='KiB'>33554432</memory> <currentMemory unit='KiB'>33554432</currentMemory> <vcpu placement='static'>12</vcpu> <iothreads>1</iothreads> <os> <type arch='x86_64' machine='pc-i440fx-2.12'>hvm</type> <boot dev='cdrom'/> <boot dev='hd'/> </os> <features> <acpi/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vpindex state='on'/> <runtime state='on'/> <synic state='on'/> <reset state='on'/> <vendor_id state='on' value='KVM Hv'/> </hyperv> </features> <cpu mode='custom' match='exact' check='full'> <model fallback='forbid'>Haswell-noTSX-IBRS</model> <topology sockets='1' cores='6' threads='2'/> <feature policy='require' name='vme'/> <feature policy='require' name='f16c'/> <feature policy='require' name='rdrand'/> <feature policy='require' name='hypervisor'/> <feature policy='require' name='arat'/> <feature policy='disable' name='spec-ctrl'/> <feature policy='require' name='xsaveopt'/> <feature policy='require' name='abm'/> </cpu> <clock offset='localtime'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='yes'/> <timer name='hypervclock' present='yes'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='none' io='native' ioeventfd='on' iothread='1'/> <source dev='/dev/zvol/datastore/vm/testvm-vda'/> <backingStore/> <target dev='vda' bus='virtio'/> <alias name='virtio-disk0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu'/> <target dev='hdc' bus='ide'/> <readonly/> <alias name='ide0-1-0'/> <address type='drive' controller='0' bus='1' target='0' unit='0'/> </disk> <controller type='ide' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='usb' index='0' model='piix3-uhci'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <interface type='bridge'> <source bridge='lan'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-12-testvm/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <graphics type='vnc' port='5901' autoport='no' listen='0.0.0.0'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='cirrus' vram='16384' heads='1' primary='yes'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain>

2 1

[libvirt-users] Copy volume from one storage to another
by Shashwat shagun 08 Aug '18

08 Aug '18

Hi, I want to copy a volume from one to pool to another pool through libvirt golang api but I’m unaware of any such functions. Can anybody guide me a little bit here? Best Regards, Shashwat Shagun me(a)shashwat.tech

3 2

[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 07 Aug '18

07 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