February 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] 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] ceph rbd pool and libvirt manageability (virt-install)
by Jelle de Jong 29 Aug '18

29 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] virRandomBits - not very random
by Brian Rak 01 Jun '18

01 Jun '18

I just ran into an issue where I had about 30 guests get duplicate mac addresses assigned. These were scattered across 30 different machines. Some debugging revealed that: 1) All the host machines were restarted within a couple seconds of each other 2) All the host machines had fairly similar libvirtd pids (within ~100 PIDs of each other) 3) Libvirt seeds the RNG using 'time(NULL) ^ getpid()' This perfectly explains why I saw so many duplicate mac addresses. Why is the RNG seed such a predictable value? Surely there has to be a better source of a random seed then the timestamp and the pid? The PID seems to me to be a very bad source of any randomness. I just ran a test across 60 of our hosts. 43 of them shared their PID with at least one other machine.

7 13

[libvirt-users] Create qcow2 v3 volumes via libvirt
by Gionatan Danti 25 May '18

25 May '18

Hi all, on a fully patched CentOS 7.4 x86-64, I see the following behavior: - when creating a new volumes using vol-create-as, the resulting file is a qcow2 version 2 (compat=0.10) file. Example: [root@gdanti-lenovo vmimages]# virsh vol-create-as default zzz.qcow2 8589934592 --format=qcow2 --backing-vol /mnt/vmimages/centos6.img Vol zzz.qcow2 created [root@gdanti-lenovo vmimages]# file zzz.qcow2 zzz.qcow2: QEMU QCOW Image (v2), has backing file (path /mnt/vmimages/centos6.img), 8589934592 bytes [root@gdanti-lenovo vmimages]# qemu-img info zzz.qcow2 image: zzz.qcow2 file format: qcow2 virtual size: 8.0G (8589934592 bytes) disk size: 196K cluster_size: 65536 backing file: /mnt/vmimages/centos6.img backing file format: raw Format specific information: compat: 0.10 refcount bits: 16 - when creating a snapshot, the resulting file is a qcow2 version 3 (comapt=1.1) file. Example: [root@gdanti-lenovo vmimages]# virsh snapshot-create-as centos6left --disk-only --no-metadata snap.qcow2 Domain snapshot snap.qcow2 created [root@gdanti-lenovo vmimages]# file centos6left.snap.qcow2 centos6left.snap.qcow2: QEMU QCOW Image (v3), has backing file (path /mnt/vmimages/centos6left.qcow2), 8589934592 bytes [root@gdanti-lenovo vmimages]# qemu-img info centos6left.snap.qcow2 image: centos6left.snap.qcow2 file format: qcow2 virtual size: 8.0G (8589934592 bytes) disk size: 196K cluster_size: 65536 backing file: /mnt/vmimages/centos6left.qcow2 backing file format: qcow2 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false From what I know, this is a deliberate decision: compat=1.1 requires relatively recent qemu version, and creating a new volume play on the "safe side" of compatibility. It is possible to create a new volume using qcow2 version 3 (compat=1.1) format *using libvirt/virsh* (I know I can do that via qemu-img)? Any drawback on using version 3 format? 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

6 17

[libvirt-users] Possible to edit/apply nwfilter at runtime?
by Andre Goree 03 Apr '18

03 Apr '18

I'm trying to determine if it's possible to edit/attach/apply nwfilter rules at runtime? I.e., after a VM is already running, can I apply a nwfilter to the VM and have it work without rebooting the machine? Thus far, I've not come across a way to do so, but I thought I'd ask here before I chase my tail around Google. Thanks! -- Andre Goree -=-=-=-=-=- Email - andre at drenet.net Website - http://blog.drenet.net PGP key - http://www.drenet.net/pubkey.html -=-=-=-=-=-

3 6

[libvirt-users] snapshot of a raw file - how to revert ?
by Lentes, Bernd 29 Mar '18

29 Mar '18

Hi, i have the following system: pc59093:~ # cat /etc/os-release NAME="SLES" VERSION="11.4" VERSION_ID="11.4" PRETTY_NAME="SUSE Linux Enterprise Server 11 SP4" ID="sles" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:suse:sles:11:4" pc59093:~ # uname -a Linux pc59093 3.0.101-84-default #1 SMP Tue Oct 18 10:32:51 UTC 2016 (15251d6) x86_64 x86_64 x86_64 GNU/Linux pc59093:~ # rpm -qa|grep -iE 'libvirt|kvm' libvirt-cim-0.5.12-0.7.16 libvirt-python-1.2.5-1.102 libvirt-client-1.2.5-15.3 kvm-1.4.2-47.1 sles-kvm_en-pdf-11.4-0.33.1 libvirt-1.2.5-15.3 I have several guests running with raw files, which is sufficent for me. Now i'd like to snapshot one guest because i make heavy configuration changes on it. >From what i read in the net is that libvirt supports snapshoting of raw files when the guest is shutdown and the file of the snapshot becomes a qcow2. Right ? I try to avoid converting my raw file to a qcow2 file. I can shutdown the guest for a certain time, that's no problem. I don't need a live snapshot. But how can i revert to my previous state if my configuration changes go wrong ? Can i do this with snapshot-revert or do i have to edit the xml file and point the hd again to the origin raw file ? What i found in the net wasn't complete clear. Thanks. Bernd -- Bernd Lentes Systemadministration Institut für Entwicklungsgenetik Gebäude 35.34 - Raum 208 HelmholtzZentrum münchen [ mailto:bernd.lentes@helmholtz-muenchen.de | bernd.lentes(a)helmholtz-muenchen.de ] phone: +49 89 3187 1241 fax: +49 89 3187 2294 [ http://www.helmholtz-muenchen.de/idg | http://www.helmholtz-muenchen.de/idg ] no backup - no mercy Helmholtz Zentrum München

2 9

[libvirt-users] Fail in virDomainUpdateDeviceFlags (libvirt-4.0.0 + Qemu-kvm 2.9.0 + Ceph 10.2.10)
by Star Guo 06 Mar '18

06 Mar '18

Hello Everyone, My pc run in CentOS 7.4 and install libvirt-4.0.0 + Qemu-kvm 2.9.0 + Ceph 10.2.10 ALL-in-One. I use python-sdk with libvirt and run [self.domain.updateDeviceFlags(xml, libvirt.VIR_DOMAIN_AFFECT_LIVE)] on CDROM (I want to change media path). However, I enable libvirt debug log , the log as below: "2018-02-26 13:09:13.638+0000: 50524: debug : virDomainLookupByName:412 : conn=0x7f7278000aa0, name=6ec499397d594ef2a64fcfc938f38225 2018-02-26 13:09:13.638+0000: 50515: debug : virDomainGetInfo:2431 : dom=0x7f726c000c30, (VM: name=6ec499397d594ef2a64fcfc938f38225, uuid=6ec49939-7d59-4ef2-a64f-cfc938f38225), info=0x7f72b9059b20 2018-02-26 13:09:13.638+0000: 50515: debug : qemuGetProcessInfo:1479 : Got status for 71205/0 user=14674 sys=3627 cpu=5 rss=105105 2018-02-26 13:09:13.644+0000: 50519: debug : virDomainGetXMLDesc:2572 : dom=0x7f7280002f20, (VM: name=6ec499397d594ef2a64fcfc938f38225, uuid=6ec49939-7d59-4ef2-a64f-cfc938f38225), flags=0x0 2018-02-26 13:09:13.653+0000: 50516: debug : virDomainUpdateDeviceFlags:8326 : dom=0x7f7274000b90, (VM: name=6ec499397d594ef2a64fcfc938f38225, uuid=6ec49939-7d59-4ef2-a64f-cfc938f38225), xml=<disk device="cdrom" type="network"><source name="zstack/08085a31f8c43f278ed2f649ee166b1f@08085a31f8c43f278ed2f649ee166b 1f" protocol="rbd"><host name="10.0.229.181" port="6789" /></source><auth username="zstack"><secret type="ceph" uuid="9b06bb70-dc13-4338-88fd-b0c72d5ab9e9" /></auth><target bus="ide" dev="hdc" /><readonly /></disk>, flags=0x1 2018-02-26 13:09:13.653+0000: 50516: debug : qemuDomainObjBeginJobInternal:4778 : Starting job: modify (vm=0x7f7294100af0 name=6ec499397d594ef2a64fcfc938f38225, current job=none async=none) 2018-02-26 13:09:13.653+0000: 50516: debug : qemuDomainObjBeginJobInternal:4819 : Started job: modify (async=none vm=0x7f7294100af0 name=6ec499397d594ef2a64fcfc938f38225) 2018-02-26 13:09:13.660+0000: 50516: debug : virQEMUCapsCacheLookup:5443 : Returning caps 0x7f7294126ac0 for /usr/libexec/qemu-kvm 2018-02-26 13:09:13.664+0000: 50516: debug : virQEMUCapsCacheLookup:5443 : Returning caps 0x7f7294126ac0 for /usr/libexec/qemu-kvm 2018-02-26 13:09:13.667+0000: 50516: debug : qemuSetupImageCgroupInternal:91 : Not updating cgroups for disk path '08085a31f8c43f278ed2f649ee166b1f@08085a31f8c43f278ed2f649ee166b1f', type: network 2018-02-26 13:09:13.667+0000: 50516: debug : qemuDomainObjEnterMonitorInternal:5048 : Entering monitor (mon=0x7f728c07f260 vm=0x7f7294100af0 name=6ec499397d594ef2a64fcfc938f38225) 2018-02-26 13:09:13.667+0000: 50516: debug : qemuMonitorEjectMedia:2487 : dev_name=drive-ide0-1-0 force=0 2018-02-26 13:09:13.667+0000: 50516: debug : qemuMonitorEjectMedia:2489 : mon:0x7f728c07f260 vm:0x7f7294100af0 json:1 fd:24 2018-02-26 13:09:13.667+0000: 50516: debug : qemuMonitorJSONCommandWithFd:301 : Send command '{"execute":"eject","arguments":{"device":"drive-ide0-1-0","force":false},"i d":"libvirt-78"}' for write with FD -1 2018-02-26 13:09:13.667+0000: 50516: info : qemuMonitorSend:1079 : QEMU_MONITOR_SEND_MSG: mon=0x7f728c07f260 msg={"execute":"eject","arguments":{"device":"drive-ide0-1-0","force":false} ,"id":"libvirt-78"} fd=-1 2018-02-26 13:09:13.667+0000: 50514: info : qemuMonitorIOWrite:553 : QEMU_MONITOR_IO_WRITE: mon=0x7f728c07f260 buf={"execute":"eject","arguments":{"device":"drive-ide0-1-0","force":false} ,"id":"libvirt-78"} len=93 ret=93 errno=0 2018-02-26 13:09:13.669+0000: 50514: debug : qemuMonitorJSONIOProcessLine:193 : Line [{"return": {}, "id": "libvirt-78"}] 2018-02-26 13:09:13.669+0000: 50514: info : qemuMonitorJSONIOProcessLine:213 : QEMU_MONITOR_RECV_REPLY: mon=0x7f728c07f260 reply={"return": {}, "id": "libvirt-78"} 2018-02-26 13:09:13.669+0000: 50516: debug : qemuMonitorJSONCommandWithFd:306 : Receive command reply ret=0 rxObject=0x5561b7c6abc0 2018-02-26 13:09:13.669+0000: 50516: debug : qemuDomainObjExitMonitorInternal:5071 : Exited monitor (mon=0x7f728c07f260 vm=0x7f7294100af0 name=6ec499397d594ef2a64fcfc938f38225) 2018-02-26 13:09:13.669+0000: 50516: debug : qemuDomainObjEnterMonitorInternal:5048 : Entering monitor (mon=0x7f728c07f260 vm=0x7f7294100af0 name=6ec499397d594ef2a64fcfc938f38225) 2018-02-26 13:09:13.669+0000: 50516: debug : qemuMonitorEjectMedia:2487 : dev_name=drive-ide0-1-0 force=0 2018-02-26 13:09:13.669+0000: 50516: debug : qemuMonitorEjectMedia:2489 : mon:0x7f728c07f260 vm:0x7f7294100af0 json:1 fd:24 2018-02-26 13:09:13.669+0000: 50516: debug : qemuMonitorJSONCommandWithFd:301 : Send command '{"execute":"eject","arguments":{"device":"drive-ide0-1-0","force":false},"i d":"libvirt-79"}' for write with FD -1 2018-02-26 13:09:13.669+0000: 50516: info : qemuMonitorSend:1079 : QEMU_MONITOR_SEND_MSG: mon=0x7f728c07f260 msg={"execute":"eject","arguments":{"device":"drive-ide0-1-0","force":false} ,"id":"libvirt-79"} fd=-1 2018-02-26 13:09:13.669+0000: 50514: info : qemuMonitorIOWrite:553 : QEMU_MONITOR_IO_WRITE: mon=0x7f728c07f260 buf={"execute":"eject","arguments":{"device":"drive-ide0-1-0","force":false} ,"id":"libvirt-79"} len=93 ret=93 errno=0 2018-02-26 13:09:13.670+0000: 50514: debug : qemuMonitorJSONIOProcessLine:193 : Line [{"return": {}, "id": "libvirt-79"}] 2018-02-26 13:09:13.670+0000: 50514: info : qemuMonitorJSONIOProcessLine:213 : QEMU_MONITOR_RECV_REPLY: mon=0x7f728c07f260 reply={"return": {}, "id": "libvirt-79"} 2018-02-26 13:09:13.670+0000: 50516: debug : qemuMonitorJSONCommandWithFd:306 : Receive command reply ret=0 rxObject=0x5561b7c6a080 2018-02-26 13:09:13.670+0000: 50516: debug : qemuDomainObjExitMonitorInternal:5071 : Exited monitor (mon=0x7f728c07f260 vm=0x7f7294100af0 name=6ec499397d594ef2a64fcfc938f38225) 2018-02-26 13:09:13.670+0000: 50516: debug : qemuDomainObjEnterMonitorInternal:5048 : Entering monitor (mon=0x7f728c07f260 vm=0x7f7294100af0 name=6ec499397d594ef2a64fcfc938f38225) 2018-02-26 13:09:13.670+0000: 50516: debug : qemuMonitorChangeMedia:2504 : dev_name=drive-ide0-1-0 newmedia=rbd:zstack/08085a31f8c43f278ed2f649ee166b1f@08085a31f8c43f278ed2f64 9ee166b1f:auth_supported=none:mon_host=10.0.229.181\:6789 format=raw 2018-02-26 13:09:13.670+0000: 50516: debug : qemuMonitorChangeMedia:2506 : mon:0x7f728c07f260 vm:0x7f7294100af0 json:1 fd:24 2018-02-26 13:09:13.670+0000: 50516: debug : qemuMonitorJSONCommandWithFd:301 : Send command '{"execute":"change","arguments":{"device":"drive-ide0-1-0","target":"rbd:zs tack/08085a31f8c43f278ed2f649ee166b1f@08085a31f8c43f278ed2f649ee166b1f:auth_ supported=none:mon_host=10.0.229.181\\:6789","arg":"raw"},"id":"libvirt-80"} ' for write with FD -1 2018-02-26 13:09:13.670+0000: 50516: info : qemuMonitorSend:1079 : QEMU_MONITOR_SEND_MSG: mon=0x7f728c07f260 msg={"execute":"change","arguments":{"device":"drive-ide0-1-0","target":"rbd :zstack/08085a31f8c43f278ed2f649ee166b1f@08085a31f8c43f278ed2f649ee166b1f:au th_supported=none:mon_host=10.0.229.181\\:6789","arg":"raw"},"id":"libvirt-8 0"} fd=-1 2018-02-26 13:09:13.670+0000: 50514: info : qemuMonitorIOWrite:553 : QEMU_MONITOR_IO_WRITE: mon=0x7f728c07f260 buf={"execute":"change","arguments":{"device":"drive-ide0-1-0","target":"rbd :zstack/08085a31f8c43f278ed2f649ee166b1f@08085a31f8c43f278ed2f649ee166b1f:au th_supported=none:mon_host=10.0.229.181\\:6789","arg":"raw"},"id":"libvirt-8 0"} len=229 ret=229 errno=0 2018-02-26 13:09:13.678+0000: 50514: debug : qemuMonitorJSONIOProcessLine:193 : Line [{"id": "libvirt-80", "error": {"class": "GenericError", "desc": "error connecting: Operation not supported"}}] 2018-02-26 13:09:13.678+0000: 50514: info : qemuMonitorJSONIOProcessLine:213 : QEMU_MONITOR_RECV_REPLY: mon=0x7f728c07f260 reply={"id": "libvirt-80", "error": {"class": "GenericError", "desc": "error connecting: Operation not supported"}} 2018-02-26 13:09:13.678+0000: 50516: debug : qemuMonitorJSONCommandWithFd:306 : Receive command reply ret=0 rxObject=0x5561b7c88f40 2018-02-26 13:09:13.678+0000: 50516: debug : qemuMonitorJSONCheckError:381 : unable to execute QEMU command {"execute":"change","arguments":{"device":"drive-ide0-1-0","target":"rbd:zst ack/08085a31f8c43f278ed2f649ee166b1f@08085a31f8c43f278ed2f649ee166b1f:auth_s upported=none:mon_host=10.0.229.181\\:6789","arg":"raw"},"id":"libvirt-80"}: {"id":"libvirt-80","error":{"class":"GenericError","desc":"error connecting: Operation not supported"}} 2018-02-26 13:09:13.678+0000: 50516: error : qemuMonitorJSONCheckError:392 : internal error: unable to execute QEMU command 'change': error connecting: Operation not supported 2018-02-26 13:09:13.678+0000: 50516: debug : qemuDomainObjExitMonitorInternal:5071 : Exited monitor (mon=0x7f728c07f260 vm=0x7f7294100af0 name=6ec499397d594ef2a64fcfc938f38225) 2018-02-26 13:09:13.678+0000: 50516: debug : qemuTeardownImageCgroup:123 : Not updating cgroups for disk path '08085a31f8c43f278ed2f649ee166b1f@08085a31f8c43f278ed2f649ee166b1f', type: network 2018-02-26 13:09:13.682+0000: 50516: debug : qemuDomainObjEndJob:4979 : Stopping job: modify (async=none vm=0x7f7294100af0 name=6ec499397d594ef2a64fcfc938f38225) 2018-02-26 13:09:13.983+0000: 50520: debug : virDomainLookupByName:412 : conn=0x7f7278000aa0, name=6ec499397d594ef2a64fcfc938f38225 2018-02-26 13:09:13.990+0000: 50518: debug : virDomainGetInfo:2431 : dom=0x7f72700009b0, (VM: name=6ec499397d594ef2a64fcfc938f38225, uuid=6ec49939-7d59-4ef2-a64f-cfc938f38225), info=0x7f72b7856b20 2018-02-26 13:09:13.990+0000: 50518: debug : qemuGetProcessInfo:1479 : Got status for 71205/0 user=14675 sys=3628 cpu=0 rss=105119 2018-02-26 13:09:13.991+0000: 50515: debug : virDomainGetXMLDesc:2572 : dom=0x7f726c000c30, (VM: name=6ec499397d594ef2a64fcfc938f38225, uuid=6ec49939-7d59-4ef2-a64f-cfc938f38225), flags=0x0" I see the flow is virDomainUpdateDeviceFlags -> qemuMonitorChangeMedia, but the cephx auth is drop, so make update error. Anybody meet this error? Best Regards, Star Guo

4 6

[libvirt-users] How can we achieve vga emulation over a serial port in libvirt
by Meina Li 05 Mar '18

05 Mar '18

Hi For the latest seabios version, it said: Support for vga emulation over a serial port in SeaBIOS (sercon). So I want to know how can I find the application of this feature in libvirt? And whether my understanding is correct? There are no related instruction on the website: https://libvirt.org/ My understanding: (1) The feature means: we can set this the IO address of a serial port to "video" element to enable SeaBIOS' VGA adapter emulation on the given serial port. (2) Libvirt XML examples and with this xml the guest can start successfully: <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </controller> <video> <model type='vga' vram='16384' heads='1' primary='yes'/> <address type='virtio-serial' controller='0' bus='0' port='3'/> </video> Thank in advance. Best Regards Meina Li

2 2

[libvirt-users] Libvirt supported qemu-ga commands
by procmem 01 Mar '18

01 Mar '18

Where can I find the full list of libvirt supported qemu-ga commands? The docs [0] imply virDomainQemuAgentCommand bypasses libvirt and is not recommended. I am looking to pass suspend/resume events from the host to the guest and then have the guest act on this internally. Your help is appreciated. [0] https://wiki.libvirt.org/page/Qemu_guest_agent

2 4

[libvirt-users] Reply: Fail in virDomainUpdateDeviceFlags (libvirt-4.0.0 + Qemu-kvm 2.9.0 + Ceph 10.2.10)
by Star Guo 01 Mar '18

01 Mar '18

Dear Michal After I fix the local libvirt master branch follow your patch, and build rpm for CentOS 7.4. virDomainUpdateDeviceFlags as bellow: ================================================ 2018-02-27 09:27:43.782+0000: 16656: debug : virDomainUpdateDeviceFlags:8326 : dom=0x7f2084000c50, (VM: name=6ec499397d594e f2a64fcfc938f38225, uuid=6ec49939-7d59-4ef2-a64f-cfc938f38225), xml=<disk device="cdrom" type="network"><source name="zstac k/08085a31f8c43f278ed2f649ee166b1f@08085a31f8c43f278ed2f649ee166b1f" protocol="rbd"><host name="10.0.229.181" port="6789" / ></source><auth username="zstack"><secret type="ceph" uuid="9b06bb70-dc13-4338-88fd-b0c72d5ab9e9" /></auth><target bus="ide " dev="hdc" /><readonly /></disk>, flags=0x1 ... 2018-02-27 09:27:43.788+0000: 16656: info : virObjectNew:254 : OBJECT_NEW: obj=0x7f2084003cc0 classname=qemuDomainStorageSourcePrivate 2018-02-27 09:27:43.788+0000: 16656: debug : virConnectOpen:1169 : name=secret:///system 2018-02-27 09:27:43.788+0000: 16656: info : virObjectNew:254 : OBJECT_NEW: obj=0x7f20840008c0 classname=virConnect 2018-02-27 09:27:43.788+0000: 16656: debug : virConfLoadConfig:1576 : Loading config file '/etc/libvirt/libvirt.conf' 2018-02-27 09:27:43.788+0000: 16656: debug : virConfReadFile:752 : filename=/etc/libvirt/libvirt.conf 2018-02-27 09:27:43.788+0000: 16656: debug : virFileClose:110 : Closed fd 28 2018-02-27 09:27:43.788+0000: 16656: debug : virConfGetValueStringList:946 : Get value string list (nil) 0 2018-02-27 09:27:43.788+0000: 16656: debug : virConnectOpenInternal:1033 : Split "secret:///system" to URI components: scheme secret server <null> user <null> port 0 path /system .. 2018-02-27 09:27:43.788+0000: 16656: info : virObjectRef:388 : OBJECT_REF: obj=0x563fa24f2360 2018-02-27 09:27:43.788+0000: 16656: info : virObjectUnref:350 : OBJECT_UNREF: obj=0x563fa24f2360 2018-02-27 09:27:43.788+0000: 16656: debug : virConnectOpenInternal:1098 : driver 7 secret returned SUCCESS 2018-02-27 09:27:43.788+0000: 16656: error : qemuDomainGetSecretAESAlias:729 : invalid argument: encrypted secret alias requires valid source alias 2018-02-27 09:27:43.788+0000: 16656: info : virObjectUnref:350 : OBJECT_UNREF: obj=0x7f20840008c0 2018-02-27 09:27:43.788+0000: 16656: info : virObjectUnref:352 : OBJECT_DISPOSE: obj=0x7f20840008c0 2018-02-27 09:27:43.788+0000: 16656: info : virObjectUnref:350 : OBJECT_UNREF: obj=0x7f2030101cb0 2018-02-27 09:27:43.788+0000: 16656: debug : qemuDomainObjEndJob:5594 : Stopping job: modify (async=none vm=0x7f20300fa6e0 name=6ec499397d594ef2a64fcfc938f38225) ====================================================== But it fails. Best Regards, Star Guo -----邮件原件----- 发件人: Michal Privoznik [mailto:mprivozn@redhat.com] 发送时间: 2018年2月27日 16:53 收件人: Star Guo <starg(a)ceph.me>; libvirt-users(a)redhat.com 抄送: John Ferlan <jferlan(a)redhat.com> 主题: Re: [libvirt-users] Fail in virDomainUpdateDeviceFlags (libvirt-4.0.0 + Qemu-kvm 2.9.0 + Ceph 10.2.10) On 02/27/2018 03:06 AM, Star Guo wrote: > Hello Everyone, > > > > My pc run in CentOS 7.4 and install libvirt-4.0.0 + Qemu-kvm 2.9.0 + > Ceph > 10.2.10 ALL-in-One. > > > > I use python-sdk with libvirt and run > [self.domain.updateDeviceFlags(xml, > libvirt.VIR_DOMAIN_AFFECT_LIVE)] on CDROM (I want to change media path). > However, I enable libvirt debug log , the log as below: > > <snip/> > > I see the flow is virDomainUpdateDeviceFlags -> > qemuMonitorChangeMedia, but the cephx auth is drop, so make update error. Anybody meet this error? Yes, this is a libvirt bug. I think this fixes the issue: diff --git i/src/qemu/qemu_driver.c w/src/qemu/qemu_driver.c index 96454c17c..0e5ad9971 100644 --- i/src/qemu/qemu_driver.c +++ w/src/qemu/qemu_driver.c @@ -7842,6 +7842,8 @@ qemuDomainChangeDiskLive(virDomainObjPtr vm, virQEMUDriverPtr driver, bool force) { + virQEMUDriverConfigPtr cfg = virQEMUDriverGetConfig(driver); + qemuDomainObjPrivatePtr priv = vm->privateData; virDomainDiskDefPtr disk = dev->data.disk; virDomainDiskDefPtr orig_disk = NULL; virDomainDeviceDef oldDev = { .type = dev->type }; @@ -7850,6 +7852,9 @@ qemuDomainChangeDiskLive(virDomainObjPtr vm, if (virDomainDiskTranslateSourcePool(disk) < 0) goto cleanup; + if (qemuDomainPrepareDiskSource(disk, priv, cfg) < 0) + goto cleanup; + if (qemuDomainDetermineDiskChain(driver, vm, disk, false, true) < 0) goto cleanup; @@ -7898,6 +7903,7 @@ qemuDomainChangeDiskLive(virDomainObjPtr vm, ret = 0; cleanup: + virObjectUnref(cfg); return ret; } Can you check and confirm? Michal

2 1

[libvirt-users] QEMU guest-agent safety in hostile VM?
by procmem 01 Mar '18

01 Mar '18

Hi. Is it still considered risky to use the QEMU guest agent in an untrusted guest? A warning on these lines was written in the manual a few years back when the feature made its debut. I wanted to know if it was hardened since.

2 1

[libvirt-users] Install of Libvirt-snmp
by Michael Cooper 26 Feb '18

26 Feb '18

Hello Everyone, This is my first time here and I have a question. Where is it installed? I am assuming on the KVM Host itself? I am sorry if this is a stupid question thanks. -- Michael A Cooper Linux Certified Zerto Certified http://www.coopfire.com

2 1

[libvirt-users] "scripts are not supported on interfaces of type vhostuser" error
by Riccardo Ravaioli 24 Feb '18

24 Feb '18

Hi, I'm having trouble starting a VM with vhostuser interfaces. I have a simple configuration where a VM running Debian has 1 vhostuser interface plugged into an OVS switch where a DPDK interface is already plugged in. $ ovs-vsctl show: Bridge "switch1" Port "switch1" Interface "switch1" type: internal Port "1.switch1" Interface "1.switch1" type: dpdk options: {dpdk-devargs="0000:0b:00.0"} Port "0.switch1" Interface "0.vm" type: dpdkvhostuserclient options: {vhost-server-path="/opt/oa/vhost/0.vm.sock"} The relevant excerpt from the XML of my VM is: <?xml version="1.0" ?> <domain type="kvm" xmlns:ns0="http://libvirt.org/schemas/domain/qemu/1.0">  <devices> <emulator>/opt/oa/bin/qemu-system-x86_64</emulator>  <interface type="vhostuser"> <script path="/opt/oa/etc/qemu-ifup"/> <source mode="server" path="/opt/oa/vhost/0.vm.sock" type="unix"/> <mac address="52:54:00:41:37:08"/> <model type="virtio"/> <driver queues="1"> <host csum="off"/> </driver> </interface>  </devices> <ns0:commandline> <ns0:arg value="-object"/> <ns0:arg value="memory-backend-file,id=mem,size=2G,mem-path=/dev/hugepages,share=on"/> <ns0:arg value="-numa"/> <ns0:arg value="node,memdev=mem"/> <ns0:arg value="-mem-prealloc"/> </ns0:commandline> </domain> Now, if I try to start my VM, I get the following error and the VM is not started at all: $ virsh create vm.xml error: Failed to create domain from vm.xml error: unsupported configuration: scripts are not supported on interfaces of type vhostuser The logs from libvirtd.log say: 2018-02-22 09:18:24.982+0000: 2033: warning : qemuProcessStartWarnShmem:4539 : Detected vhost-user interface without any shared memory, the interface might not be operational 2018-02-22 09:18:24.982+0000: 2033: error : qemuBuildHostNetStr:3894 : unsupported configuration: scripts are not supported on interfaces of type vhostuser The logs from qemu simply say: 2018-02-22 09:26:15.857+0000: shutting down, reason=failed And finally, ovs-vswitchd.log: 2018-02-22T09:18:24.715Z|00328|dpdk|INFO|VHOST_CONFIG: vhost-user client: socket created, fd: 51 2018-02-22T09:18:24.716Z|00329|netdev_dpdk|INFO|vHost User device '0.vm' created in 'client' mode, using client socket '/opt/oa/vhost/0.vm.sock' 2018-02-22T09:18:24.718Z|00330|dpdk|WARN|VHOST_CONFIG: failed to connect to /opt/oa/vhost/0.vm.sock: No such file or directory 2018-02-22T09:18:24.718Z|00331|dpdk|INFO|VHOST_CONFIG: /opt/oa/vhost/0.vm.sock: reconnecting... 2018-02-22T09:18:24.718Z|00332|bridge|INFO|bridge switch1: added interface 0.vm on port 5 Am I missing something on the openvswitch or on the libvirt side? It looks like openvswitch can't find /opt/oa/vhost/0.vm.sock, but isn't either openvswitch or libvirt in charge of creating it? Then, I'm not too sure about the error messages in libvirtd.log... My software versions are: libvirt 3.10.0, qemu 2.10.2, openvswitch 2.8.1 and DPDK 17.11. Thanks a lot! Riccardo

3 4

[libvirt-users] How to use rtc_timeoffset (XL toolkit option) in Libvirt and Xen/libxl hypervisor?
by Volo M. 21 Feb '18

21 Feb '18

Hello techs, We used XL toolkit for Xen hypervisor for starting Windows hvm VMs and the option rtc_timeoffset worked perfectly with XL. It helped us to set correct Timezone time/offset for Windows HVM VMs from inside virtual_machine xen config. For example: Below option WORKS perfectly with XL toolkit. [root@hw12xen ~]# cat goillltawdlssq.xl.cfg | grep offset rtc_timeoffset = "7200" # +2 hours to UTC time (or +/-3600=+/-1 hour to UTC time) [root@hw12xen ~]# Now we try to migrate all the Windows hvm VMs to using Libvirt and Xen 4.6.6 (or 4.4). But as we see it's impossible to make VMs using correct time/offset set in XML config like below: below Libvirt option DOESN'T WORK as we expect... [root@hw12xen ~]# cat goillltawdlssq.var.xml | grep offset <clock offset='variable' adjustment='7200' /> [root@hw12xen ~]# Can you please explain if there's something we're doing wrong way or it's just a bug like described here: https://bugzilla.redhat.com/show_bug.cgi?id=1212191 ? Thanks in advance.

2 3

[libvirt-users] ANNOUNCE: ruby-libvirt 0.7.1
by Chris Lalancette 18 Feb '18

18 Feb '18

I'm pleased to release ruby-libvirt 0.7.1. ruby-libvirt is a ruby wrapper around the libvirt API. The changelog between 0.7.0 and 0.7.1 is: * Fix a bad bug in block_resize (Marius Rieder) * Fix up some problems pointed out by clang * Fix up the tests for small semantic differences in how libvirt works Version 0.7.1 is available from http://libvirt.org/ruby: Tarball: http://libvirt.org/ruby/download/ruby-libvirt-0.7.1.tgz Gem: http://libvirt.org/ruby/download/ruby-libvirt-0.7.1.gem It is also available from rubygems.org; to get the latest version, run: $ gem install ruby-libvirt Packages for it are also built for Fedora, and will be released shortly. As usual, if you run into questions, problems, or bugs, please feel free to mail me (clalancette at gmail.com) and the libvirt mailing list. Thanks to those who contributed to this release.

1 0

[libvirt-users] what is the practical limit on snapshot generations?
by W Kern 17 Feb '18

17 Feb '18

I've googled around on this and haven't found much so I'll ask here. I have a client who routinely does live snapshots on snapshot on snapshot ( just keep going recursively) I've told him to roll them up once in a while, but he feels its unnecessary and only plans a rollup during a major maintenance period, where he can take the whole site down and then watch it grind during the commit. Note these are Qcow2 (1.1) images and they are external snaps. Most of the write activity is logging and medium database writes for an ecommerce store. It is certainly NOT heavy write i/o. Isn't there a cost (speed, resources) etc to all those generations. Any safety issues? Is there an optimium # of generations where if you exceed that you get diminishing returns. At one point are you shooting yourself in the foot, or is this really no big deal aside from two hours of downtime while the 'actual' commit occurs. -wk

1 0

[libvirt-users] Ask question
by 李杰 15 Feb '18

15 Feb '18

Dear Recently,I am interested in libvirt,but I found the libvirt does't support revert and delete the external snapshot which the raw disk based guest.My libvirt and qemu release are both 3.2.0.So I have a question,the community how to solve it,if have any plans about it.Can you tell me more about it?Thank you very much. Best Regards Rambo

3 4

[libvirt-users] kvm/libvirt on CentOS7 w/Windows 10 Pro guest
by Benjammin2068 14 Feb '18

14 Feb '18

Hey all, New to list, so I apologize if this has been asked a bunch already... Is there something I'm missing with Windows 10 as a guest that keeps Windows Updates from nuking the boot process? I just did an orderly shutdown and windows updated itself <I forgot to disable in time> only to reboot to the diagnostics screen which couldn't repair. going to command prompt and doing the usual "bootrec /fixmbr, /fixboot and /RebuildBcd" didn't help. This has happened a few times. I can't believe how fragile Win10pro is while running in a VM. (and it's happened on a couple machines I've been experimenting with -- both running same OS, but different hardware.) I just saw the FAQ about the libvirt repo for the virtio drivers for windows.... I need to go read more on it... but in the meantime, is there any other smoking gun I'm not aware of? (after lots of google searching) Thanks, -Ben

4 10

[libvirt-users] Nested KVM: L0 guest produces kernel BUG on wakeup from managed save (while a nested VM is running)
by Florian Haas 13 Feb '18

13 Feb '18

Hi everyone, I hope this is the correct list to discuss this issue; please feel free to redirect me otherwise. I have a nested virtualization setup that looks as follows: - Host: Ubuntu 16.04, kernel 4.4.0 (an OpenStack Nova compute node) - L0 guest: openSUSE Leap 42.3, kernel 4.4.104-39-default - Nested guest: SLES 12, kernel 3.12.28-4-default The nested guest is configured with "<type arch='x86_64' machine='pc-i440fx-1.4'>hvm</type>". This is working just beautifully, except when the L0 guest wakes up from managed save (openstack server resume in OpenStack parlance). Then, in the L0 guest we immediately see this: [Tue Feb 6 07:00:37 2018] ------------[ cut here ]------------ [Tue Feb 6 07:00:37 2018] kernel BUG at ../arch/x86/kvm/x86.c:328! [Tue Feb 6 07:00:37 2018] invalid opcode: 0000 [#1] SMP [Tue Feb 6 07:00:37 2018] Modules linked in: fuse vhost_net vhost macvtap macvlan xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp tun br_netfilter bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables vboxpci(O) vboxnetadp(O) vboxnetflt(O) af_packet iscsi_ibft iscsi_boot_sysfs vboxdrv(O) kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel hid_generic usbhid jitterentropy_rng drbg ansi_cprng ppdev parport_pc floppy parport joydev aesni_intel processor button aes_x86_64 virtio_balloon virtio_net lrw gf128mul glue_helper pcspkr serio_raw ablk_helper cryptd i2c_piix4 ext4 crc16 jbd2 mbcache ata_generic [Tue Feb 6 07:00:37 2018] virtio_blk ata_piix ahci libahci cirrus(O) drm_kms_helper(O) syscopyarea sysfillrect sysimgblt fb_sys_fops ttm(O) drm(O) virtio_pci virtio_ring virtio uhci_hcd ehci_hcd usbcore usb_common libata sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua scsi_mod autofs4 [Tue Feb 6 07:00:37 2018] CPU: 2 PID: 2041 Comm: CPU 0/KVM Tainted: G W O 4.4.104-39-default #1 [Tue Feb 6 07:00:37 2018] Hardware name: OpenStack Foundation OpenStack Nova, BIOS 1.10.1-1ubuntu1~cloud0 04/01/2014 [Tue Feb 6 07:00:37 2018] task: ffff880037108d80 ti: ffff88042e964000 task.ti: ffff88042e964000 [Tue Feb 6 07:00:37 2018] RIP: 0010:[<ffffffffa04f20e5>] [<ffffffffa04f20e5>] kvm_spurious_fault+0x5/0x10 [kvm] [Tue Feb 6 07:00:37 2018] RSP: 0018:ffff88042e967d70 EFLAGS: 00010246 [Tue Feb 6 07:00:37 2018] RAX: 0000000000000000 RBX: ffff88042c4f0040 RCX: 0000000000000000 [Tue Feb 6 07:00:37 2018] RDX: 0000000000006820 RSI: 0000000000000282 RDI: ffff88042c4f0040 [Tue Feb 6 07:00:37 2018] RBP: ffff88042c4f00d8 R08: ffff88042e964000 R09: 0000000000000002 [Tue Feb 6 07:00:37 2018] R10: 0000000000000004 R11: 0000000000000000 R12: 0000000000000001 [Tue Feb 6 07:00:37 2018] R13: 0000021d34fbb21d R14: 0000000000000001 R15: 000055d2157cf840 [Tue Feb 6 07:00:37 2018] FS: 00007f7c52b96700(0000) GS:ffff88043fd00000(0000) knlGS:0000000000000000 [Tue Feb 6 07:00:37 2018] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [Tue Feb 6 07:00:37 2018] CR2: 00007f823b15f000 CR3: 0000000429334000 CR4: 0000000000362670 [Tue Feb 6 07:00:37 2018] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [Tue Feb 6 07:00:37 2018] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [Tue Feb 6 07:00:37 2018] Stack: [Tue Feb 6 07:00:37 2018] ffffffffa07939b1 ffffffffa0787875 ffffffffa0503a60 ffff88042c4f0040 [Tue Feb 6 07:00:37 2018] ffffffffa04e5ede ffff88042c4f0040 ffffffffa04e6f0f ffff880037108d80 [Tue Feb 6 07:00:37 2018] ffff88042c4f00e0 ffff88042c4f00e0 ffff88042c4f0040 ffff88042e968000 [Tue Feb 6 07:00:37 2018] Call Trace: [Tue Feb 6 07:00:37 2018] [<ffffffffa07939b1>] intel_pmu_set_msr+0xfc1/0x2341 [kvm_intel] [Tue Feb 6 07:00:37 2018] DWARF2 unwinder stuck at intel_pmu_set_msr+0xfc1/0x2341 [kvm_intel] [Tue Feb 6 07:00:37 2018] Leftover inexact backtrace: [Tue Feb 6 07:00:37 2018] [<ffffffffa0787875>] ? vmx_interrupt_allowed+0x15/0x30 [kvm_intel] [Tue Feb 6 07:00:37 2018] [<ffffffffa0503a60>] ? kvm_arch_vcpu_runnable+0xa0/0xd0 [kvm] [Tue Feb 6 07:00:37 2018] [<ffffffffa04e5ede>] ? kvm_vcpu_check_block+0xe/0x60 [kvm] [Tue Feb 6 07:00:37 2018] [<ffffffffa04e6f0f>] ? kvm_vcpu_block+0x8f/0x310 [kvm] [Tue Feb 6 07:00:37 2018] [<ffffffffa0503c17>] ? kvm_arch_vcpu_ioctl_run+0x187/0x400 [kvm] [Tue Feb 6 07:00:37 2018] [<ffffffffa04ea6d9>] ? kvm_vcpu_ioctl+0x359/0x680 [kvm] [Tue Feb 6 07:00:37 2018] [<ffffffff81016689>] ? __switch_to+0x1c9/0x460 [Tue Feb 6 07:00:37 2018] [<ffffffff81224f02>] ? do_vfs_ioctl+0x322/0x5d0 [Tue Feb 6 07:00:37 2018] [<ffffffff811362ef>] ? __audit_syscall_entry+0xaf/0x100 [Tue Feb 6 07:00:37 2018] [<ffffffff8100383b>] ? syscall_trace_enter_phase1+0x15b/0x170 [Tue Feb 6 07:00:37 2018] [<ffffffff81225224>] ? SyS_ioctl+0x74/0x80 [Tue Feb 6 07:00:37 2018] [<ffffffff81634a02>] ? entry_SYSCALL_64_fastpath+0x16/0xae [Tue Feb 6 07:00:37 2018] Code: d7 fe ff ff 8b 2d 04 6e 06 00 e9 c2 fe ff ff 48 89 f2 e9 65 ff ff ff 0f 1f 44 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 <0f> 0b 66 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 89 ff 48 89 [Tue Feb 6 07:00:37 2018] RIP [<ffffffffa04f20e5>] kvm_spurious_fault+0x5/0x10 [kvm] [Tue Feb 6 07:00:37 2018] RSP <ffff88042e967d70> [Tue Feb 6 07:00:37 2018] ---[ end trace e15c567f77920049 ]--- We only hit this kernel bug if we have a nested VM running. The exact same setup, sent into managed save after shutting down the nested VM, wakes up just fine. Now I am aware of https://bugzilla.redhat.com/show_bug.cgi?id=1076294, which talks about live migration — but I think the same considerations apply. I am also aware of https://fedoraproject.org/wiki/How_to_enable_nested_virtualization_in_KVM, which strongly suggests to use host-passthrough or host-model. I have tried both, to no avail. The stack trace persists. I have also tried running a 4.15 kernel in the L0 guest, from https://kernel.opensuse.org/packages/stable, but again, the stack trace persists. What does fix things, of course, is to switch from the nested guest from KVM to Qemu — but that also makes things significantly slower. So I'm wondering: is there someone reading this who does run nested KVM and has managed to successfully live-migrate or managed-save? If so, would you be able to share a working host kernel / L0 guest kernel / nested guest kernel combination, or any other hints for tuning the L0 guest to support managed save and live migration? I'd be extraordinarily grateful for any suggestions. Thanks! Cheers, Florian

4 21

[libvirt-users] Method for connecting to CDROM/DVD
by CJ Mills 11 Feb '18

11 Feb '18

Hi everyone, I have a question on connecting to hardware devices. With virt- manager I am attempting to use a hardware cdrom/dvd drive from an Ubuntu 16.04 VM however, i keep getting "'host_cdrom' is not whitelisted" errors when starting the VM. After some searching I checked my processor and realized it does not support VT-d. Is this 1) a requirement for sharing the device with the VM, and 2) the only way of sharing the device?

1 0

[libvirt-users] Virtualization Management Platforms
by TomK 09 Feb '18

09 Feb '18

Hey All, Curious about the best, easy to use virtualization management platform for small labs of 30-40 physical servers. Looking for something that's relatively simple to operate, install and lightweight but with enough maturity to provide monitoring as well as holistic views of the entire physical space etc. Hearing of oVirt, Xen and Eucalyptus to name a few but wondering what other options do I have for a small physical space? -- Cheers, Tom K.

3 2

[libvirt-users] libvirt and NAT on a system that already has a DHCP server
by john＠bluemarble.net 09 Feb '18

09 Feb '18

I'm trying to use virt-manager and qemu/kvm on Arch Linux. The box I'm using is also the router for my house. It runs a kea DHCP server. When I try to start the default NAT network, it can't start dnsmasq because that port is already bound. Is there a way to have it not bind on this interface? I see there is an except-on statement in the dnsmasq.conf, but I can't add lines to that directly, and I didn't see any way to add special options using virsh net-edit default. Thanks.

4 6

[libvirt-users] Libvirt for virtual devices like virtual printers
by Deepti S 09 Feb '18

09 Feb '18

Hi, I have a couple of questions. - I am a new libvirt code user. I have just cloned the repo and I am looking for a suitable debugger/IDE which will help me debug the code. - I work in developing and creating virtual printers with display, with QEMU as the hypervisor (no KVM-only Qemu). Currently we have our own application to manage the virtual printers. Our plan is to migrate to libvirt, and enable our application to use the libvirt APIs. libvirt code currently looks to be specialized in pure OS-specific guests (like PCs), and I hit snags where there are manadatory devices added which a virtual printer does not need. Are there any users who are looking into customized virtual devices? I would like to knowledge share with them. The intention is to provide new libvirt APIs whenever there is such a snag and thus enable libvirt to be used for managing virtual printers. - One issue that we are seeing is with regard to USB Host Controller: We have a customized model of ehci USB Host Controller (named nr52_ehci_usb) in qemu (locally built). When I add the custom value (n552_ehci_usb) of the host controller as the "model" type in my dom xml, virsh define <xml> fails with invalid model type error. I remove the usb controller entry from the xml, and add "-usb" as a "qemucommandline" parameter, but then libvirt adds the device lsi (-device lsi,id=scsi0 -usb), and the virsh create command fails with: "-device lsi,id=scsi0 No PCI bus found for lsi53c895a". The board we have created in QEMU does not have PCI bus implemented. Is there any way I can get my usb host controller to be recognized by libvirt? Is there a way I can prevent lsi device from getting added when I make -usb a qemu command line parameter? Regards, Deepti

2 1

[libvirt-users] failed to update cdrom device with rbd disk
by chao.zhou＠zstack.io 06 Feb '18

06 Feb '18

Hello, I'm trying to using virsh update-device to update the CDROM from type='file' to ceph rbd iso with type='network'. But I always get error: Failed to update device from disk error: internal error: unable to execute QEMU command 'change': error connecting: Operation not supported I'm using libvirt-libs-3.10.0-1.el7.x86_64 with centos7.4 my original cdrom xml: <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <target dev='hdc' bus='ide' tray='open'/> <readonly/> <alias name='ide0-1-0'/> <address type='drive' controller='0' bus='1' target='0' unit='0'/> </disk> my rbd cdrom xml: <disk device="cdrom" type="network"> <driver name='qemu' type='raw'/> <auth username="zstack"> <secret type="ceph" uuid="efd3eb93-014f-4a0f-ba1f-84d7e70c9a89"/> </auth> <source name="ssd/4922ebebd7b52f11bf13b3a482b6ab7e@4922ebebd7b52f11bf13b3a482b6ab7e" protocol="rbd"> <host name="192.168.250.35" port="6789"/> </source> <target bus="ide" dev="hdc"/> <readonly/> </disk> >From the libvirtd.log, I got Send command '{"execute":"change","arguments":{"device":"drive-ide0-1-0","target":"rbd:ss d/4922ebebd7b52f11bf13b3a482b6ab7e@4922ebebd7b52f11bf13b3a482b6ab7e:auth_sup ported=none:mon_host=192.168.250.35\\:6789","arg":"raw"},"id":"libvirt-286"} ' which seems it pass the auth_support=none to the qemu, while I'm using an authentication ceph, it should use auth_support=cephx instead. I also tried to boot the VM with rbd iso and then update-device to another rbd iso, but got no luck with the same error. I have succeeded to update-device with libvirt-1.3.3, I noticed that it depends on the orig_disk->privData->secinfo, and in my environment it will be null which leads to the auth_support=none. So I'm wondering if this is a bug or I did something wrong with my configuration. Thanks in advance, Best Regards, Chao

2 1