March 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 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] 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] User name / session idin logs
by Anastasiya Ruzhanskaya 07 May '18

07 May '18

Hello everyone, I have a question about logging. I need to find out whether it is possible to see user id/session id inside logs or somewhere else. It is not passed in structured across the network, so where should I look to find out, which user (which session) is currently performing the actions?

2 3

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

02 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] Using alias under disk in XML
by Andre Goree 31 Mar '18

31 Mar '18

I've been trying to follow the information found here [1] in order to provide an alias for RBD disks I'm defining, however it does not appear to be working and I wanted to see if I was doing something wrong. I define the alias like so (using 'virsh edit'): <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='writeback' error_policy='stop' discard='unmap'/> ...truncated... <alias name='ua-test'/> </disk> However, when I then 'virsh dumpxml {guest}', the alias is not there. There is no error given after my edits are made and saved. It just seems that libvirt is completely ignoring or removing my changes, without reason. Can anyone give any insight on why this might be happening, and/or help me with the proper way of defining the alias? 1 - https://libvirt.org/formatdomain.html -- Andre Goree -=-=-=-=-=- Email - andre at drenet.net Website - http://blog.drenet.net PGP key - http://www.drenet.net/pubkey.html -=-=-=-=-=-

2 2

[libvirt-users] Unable to libvirt wireshark dissector
by Han Han 31 Mar '18

31 Mar '18

Hi guys, I am trying to analyze libvirt rpc protocol by wireshark. But I found wireshark doesn't dissect libvirt packets. Here are my environments operations: 1. Environments: My system: Debian GNU/Linux buster/sid with *kernel-4.15.0-1-amd64* Packages installed: *libvirt0-4.1.0-2-amd64 libvirt-wireshark-4.1.0-2-amd64 wireshark-2.4.5-1-amd64* 2. Libvirt configurations */etc/libvirt/libvirtd.conf*: *listen_tls = 0listen_tcp = 1tcp_port = "16509"auth_tcp = "none"* Libvirtd started with options *--listen* 3. Check wireshark libvirt plugin: Open menu: *Help* --> *About* *wireshark* --> *Plugins*. Libvirt plugin is found: *libvirt.so 4.1.0 dissector /usr/lib/x86_64-linux-gnu/w…rk/plugins/2.4.5/libvirt.so* 4. Set wireshark listening on *lo* interface and filter as 'tcp.port==16509'. Execute virsh command via tcp protocol: $ virsh -c qemu+tcp://localhost/system list In wireshark, packets are parsed as TCP protocol. And I cannot find Libvirt protocol in 'Decode as..' protocols list. And libvirt protocol is also not found in *Edit* --> *Preference* --> *Protocols*. So it seems libvirt packets are not dissected as libvirt protocol in wireshark. How can I use the wireshark libvirt plugin? -- Best regards, ----------------------------------- Han Han Quality Engineer Redhat. Email: hhan(a)redhat.com Phone: +861065339333 <+86%2010%206533%209333>

2 1

[libvirt-users] nwfilter multiple IPs
by Andre Goree 30 Mar '18

30 Mar '18

I'm trying to apply a nwfilter rule for two networks on the same guest interface, like so: ~ # virsh nwfilter-dumpxml 1081532-private-both <filter name='1081532-private-both' chain='root'> <uuid>16004b94-2b62-4568-9467-169908eb4040</uuid> <rule action='accept' direction='in' priority='500'> <ip srcipaddr='10.25.104.0' srcipmask='24'/> </rule> <rule action='accept' direction='in' priority='600'> <ip srcipaddr='10.117.50.0' srcipmask='24'/> </rule> <rule action='drop' direction='in' priority='1000'/> </filter> Within the guest, the IPs are both setup on one interface, with the IP for second network (10.117.50.0/24) configured as an alias, like so: 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 00:00:0a:d0:4e:f3 brd ff:ff:ff:ff:ff:ff inet 10.25.104.1/24 brd 10.25.104.255 scope global eth1 valid_lft forever preferred_lft forever inet 10.117.50.1/24 brd 10.117.50.255 scope global eth1:0 valid_lft forever preferred_lft forever inet6 fe80::200:aff:fed0:4ef3/64 scope link valid_lft forever preferred_lft forever The problem I'm running into is that after applying the nwfilter, I cannot reach the second network, only the first. Is this an issue with both IPs being on the same interface? The machine I'm attempting to reach has the same exact configuration -- i.e. it has an IP on the same network for both networks. Thanks in advance for any advice that can be given. -- Andre Goree -=-=-=-=-=- Email - andre at drenet.net Website - http://blog.drenet.net PGP key - http://www.drenet.net/pubkey.html -=-=-=-=-=-

1 1

[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] virt-install --connect lxc:///
by ales drtik 28 Mar '18

28 Mar '18

After reboot of the host i have different error message: root@blade1:~# virt-install --connect lxc:/// --name test_LXC --memory 128 --filesystem /home/lxcuser/LXC,/ --init /bin/sh WARNING No operating system detected, VM performance may suffer. Specify an OS with --os-variant for optimal results. Starting install... ERROR internal error: guest failed to start: Failure in libvirt_lxc startup: cannot find init path '/bin/sh' relative to container root: No such file or directory Domain installation does not appear to have been successful. If it was, you can restart your domain by running: virsh --connect lxc:/// start test_LXC otherwise, please restart your installation. root@blade1:~# ls -al /home/lxcuser/LXC total 24 drwxr-xr-x 6 root root 4096 Mar 28 16:09 . drwxr-xr-x+ 7 lxcuser lxcuser 4096 Mar 28 13:20 .. drwxr-xr-x 2 root root 4096 Mar 28 16:09 dev drwxr-xr-x 2 root root 4096 Mar 28 16:09 .oldroot drwxr-xr-x 2 root root 4096 Mar 28 16:09 proc drwxr-xr-x 2 root root 4096 Mar 28 16:09 sys

2 1

[libvirt-users] virt-install --connect lxc:///
by ales drtik 28 Mar '18

28 Mar '18

Hi, I would like to install LXC container by virt-install. >From man: virt-install \ --connect lxc:/// \ --name container \ --memory 128 \ --filesystem /home/LXC,/ \ --init /bin/sh But my err is: root@blade1:/home/lxcuser/LXC# virt-install --connect lxc:/// --name test_LXC --memory 128 --filesystem \ /home/lxcuser/LXC,/ --init /bin/sh WARNING No operating system detected, VM performance may suffer. Specify an OS with --os-variant for optimal results. Starting install... ERROR internal error: guest failed to start: Failure in libvirt_lxc startup: Failed to create /home/lxcuser/LXC/.oldroot: Invalid argument Domain installation does not appear to have been successful. If it was, you can restart your domain by running: virsh --connect lxc:/// start test_LXC otherwise, please restart your installation. What is wrong with this?

1 0

[libvirt-users] Attempt to define unprivileged LXC by libvirt
by ales drtik 23 Mar '18

23 Mar '18

Hi, i converted LXC conf to xml by: lxcuser@blade1:~/.local/share/lxc/test_deb$ virsh -c lxc:/// domxml-from- native lxc-tools /home/lxcuser/.local/share/lxc/test_deb/config <domain type='lxc'> <name>test_deb</name> <uuid>cce77799-89fd-41fd-99c1-101e00844e23</uuid> <memory unit='KiB'>65536</memory> <currentMemory unit='KiB'>65536</currentMemory> <vcpu placement='static'>1</vcpu> <os> <type arch='x86_64'>exe</type> <init>/sbin/init</init> </os> <idmap> <uid start='1258512' target='0' count='65536'/> <gid start='1258512' target='0' count='65536'/> </idmap> <features> <capabilities policy='allow'> </capabilities> </features> <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='/home/lxcuser/.local/share/lxc/test_deb/rootfs'/> <target dir='/'/> </filesystem> <interface type='bridge'> <mac address='00:16:3e:ab:21:1b'/> <source bridge='br0'/> <link state='up'/> </interface> </devices> </domain> Now attempt to define by virsh gives this err: lxcuser@blade1:~/.local/share/lxc/test_deb$ virsh -c lxc:/// define tmp/test _deb.xml error: Failed to define domain from /tmp/test_deb.xml error: unsupported configuration: You must map the root user of container Debian stretch. Where am I wrong ?

2 3

[libvirt-users] Network interface name of guest via python API
by Dennis Jacobfeuerborn 23 Mar '18

23 Mar '18

Hi, I'm trying to get some basic data from running guests on a libvirt HV but one thing I'm missing is the name of the network interfaces of the guests. I can get the MAC address from the XML but there seems to be no function to actually get the name of the interface. The only function that comes close is this one: https://libvirt.org/html/libvirt-libvirt-domain.html#virDomainInterfaceAddr… This function requires a parameter that I don't really have enough information about. What is the best way to enumerate a guests interfaces including the name? Regards, Dennis

2 2

[libvirt-users] 回复： Fwd: About libvirt domain snapshot problem(for single disk snapshot)
by James Iter 22 Mar '18

22 Mar '18

My negligence。 -- James Iter 在 2018年3月22日星期四，下午11:02，Dominik Psenner 写道： > I believe that Your mail went to the wrong recipient. As far as I'm > concerned it should have been sent to the libvirt-users mailing list, > shouldn't it? > > > On 2018-03-22 15:55, James Iter wrote: > > Thank your reply. > > I found the method. > > Now, I sharing to you. > > When create snapshot, just add ’no’ value to the ’snapshot’ option with —diskspec. > > As below: > > > > ``` bash > > snapshot-create-as 8x0lbzvS --name sys_disk --disk-only --quiesce --atomic --diskspec "vda,snapshot=external" --diskspec "vdb,snapshot=no" > > ``` > > > > > > -- > > James Iter > > > > > > 在 2018年3月21日星期三，下午6:24，Dominik Psenner 写道： > > > > > (shameless plug) > > > > > > To do automated daily backups of a few machines I wrote a small toolset to get the job done and make it as less a hassle as you can get. The source is on github https://github.com/dpsenner/libvirt-administration-tools/. Use it if you find it useful. > > > > > > Note that I have yet not tested it with multiple disks but the tool uses the output of `virsh dombklst`. In theory that should snapshot all disks of a guest machine. > > > > > > Cheers > > > On Tue, 20 Mar 2018, 19:54 James Iter, <james.iter.cn(a)gmail.com (mailto:james.iter.cn@gmail.com)> wrote: > > > > > > > > Hi, dear friends. > > > > My guest has two disks, vda and vdb. both are qcow2 local file. > > > > When guest running state. > > > > I want to take the vda snapshot of guest(just vda, no include vdb). but I met libvirt do snapshot for all disks of guest. > > > > > > > > About methods as follow: > > > > 1、 > > > > ``` bash > > > > virsh > > > > snapshot-create-as 8x0lbzvS --name sys_disk3 --disk-only --diskspec "vda,snapshot=external" > > > > ``` > > > > ``` result > > > > > > > > [root@10k03 ~]# ls -lh /opt/Images/*sys_disk3 > > > > > > > > > > > > -rw-------. 1 qemu qemu 194K 3月 20 23:27 /opt/Images/00d76a58-9637-4402-9739-21afd1246e06.sys_disk3 > > > > > > > > > > > > -rw-------. 1 qemu qemu 704K 3月 20 23:52 /opt/Images/8d582c1c-355a-4297-9434-2f2f562c77df.sys_disk3 > > > > > > > > > > > > ``` > > > > > > > > 2、 > > > > ``` python > > > > > > > > #!/usr/bin/env python > > > > > > > > > > > > # -*- coding: utf-8 -*- > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > import libvirt > > > > > > > > > > > > import libvirt_qemu > > > > > > > > > > > > import json > > > > > > > > > > > > import sys > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > name = sys.argv[1] > > > > > > > > > > > > print name > > > > > > > > > > > > conn = libvirt.open() > > > > > > > > > > > > dom = conn.lookupByName(name) > > > > > > > > > > > > > > > > > > > > > > > > > > > > xml = """ > > > > > > > > > > > > <domainsnapshot> > > > > > > > > > > > > <name>sysdisk_by_xml</name> > > > > > > > > > > > > <description>By xml</description> > > > > > > > > > > > > <disks> > > > > > > > > > > > > <disk name='vda' snapshot='external'> > > > > > > > > > > > > </disk> > > > > > > > > > > > > </disks> > > > > > > > > > > > > </domainsnapshot> > > > > > > > > > > > > """ > > > > > > > > > > > > > > > > > > > > > > > > > > > > flags = 0 > > > > > > > > > > > > flags |= libvirt.VIR_DOMAIN_SNAPSHOT_CREATE_DISK_ONLY > > > > > > > > > > > > flags |= libvirt.VIR_DOMAIN_SNAPSHOT_CREATE_QUIESCE > > > > > > > > > > > > > > > > > > > > > > > > > > > > ret = dom.snapshotCreateXML(xmlDesc=xml, flags=flags) > > > > > > > > > > > > ``` > > > > ``` result > > > > > > > > [root@10k03 ~]# ls -lh /opt/Images/*sysdisk_by_xml > > > > > > > > > > > > -rw-------. 1 qemu qemu 194K 3月 20 23:52 /opt/Images/00d76a58-9637-4402-9739-21afd1246e06.sysdisk_by_xml > > > > > > > > > > > > -rw-------. 1 qemu qemu 1.2M 3月 21 00:03 /opt/Images/8d582c1c-355a-4297-9434-2f2f562c77df.sysdisk_by_xml > > > > > > > > > > > > ``` > > > > 。 > > > > > > > > > > > > Then, I searched by google. see your page(https://www.redhat.com/archives/libvirt-users/2013-June/msg00102.html). > > > > > > > > Now, I want to ask you, have you found the method? > > > > > > > > > > > > -- > > > > James Iter > > > > > > > > > > > > _______________________________________________ > > > > libvirt-users mailing list > > > > libvirt-users(a)redhat.com (mailto:libvirt-users@redhat.com) > > > > https://www.redhat.com/mailman/listinfo/libvirt-users > > > > > > > > > > > > > > > > >

1 0

[libvirt-users] Attempt to migrate guest to the same host localhost.localdomain
by llilulu 21 Mar '18

21 Mar '18

Hi My libvirt version is 3.4.0, I migrate guest between two host, The two host have same hostname( hostname cmd output same), I try find solution on Internet, I find someone say host uuid same, But virsh sysinfo output uuid is different, when I change one host's hostname, migrate success. I wish know why, and Can I solution this problem not change hostname. My program use api virDomainMigrateToURI2, flag arg is VIR_MIGRATE_LIVE | VIR_MIGRATE_PEER2PEER . I use virsh migrate --live --p2p. Thanks

2 1

Re: [libvirt-users] Persisting the libvirt guest's reason code.
by Daniel P. Berrangé 20 Mar '18

20 Mar '18

Re-adding the mailing list - please don't take discussions off-list in this way. On Tue, Mar 20, 2018 at 05:14:45PM +0000, Tanmoy Sinha wrote: > Daniel, > > Thanks for your prompt response. I have another question, as soon as I do > virsh save <GuestID> <filename>, the corresponding xml and pid under > /var/run/libvirt/qemu is gone, but the guest still has a definition. At > this point, if I query the domain state (i.e. virsh domstate --reason > <GUESTID>) it reads shutoff(saved). Where does this fetch the reason from, > when the /var/run/libvirt/qemu/Guestname.xml file is gone? Libvirtd > maintains the reason code in-memory? That's true only if the guest has a persistent config file in /etc/libvirt. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|

1 0

[libvirt-users] About libvirt domain snapshot problem(for single disk snapshot)
by James Iter 20 Mar '18

20 Mar '18

Hi, dear friend. My guest has two disks, vda and vdb. both are qcow2 local file. When guest running state. I want to take the vda snapshot of guest(just vda, no include vdb). but I met libvirt do snapshot for all disks of guest. About methods for follow: 1、 ``` bash virsh snapshot-create-as 8x0lbzvS --name sys_disk3 --disk-only --diskspec "vda,snapshot=external" ``` ``` result [root@10k03 ~]# ls -lh /opt/Images/*sys_disk3 -rw-------. 1 qemu qemu 194K 3月 20 23:27 /opt/Images/00d76a58-9637-4402-9739-21afd1246e06.sys_disk3 -rw-------. 1 qemu qemu 704K 3月 20 23:52 /opt/Images/8d582c1c-355a-4297-9434-2f2f562c77df.sys_disk3 ``` 2、 ``` python #!/usr/bin/env python # -*- coding: utf-8 -*- import libvirt import libvirt_qemu import json import sys name = sys.argv[1] print name conn = libvirt.open() dom = conn.lookupByName(name) xml = """ <domainsnapshot> <name>sysdisk_by_xml</name> <description>By xml</description> <disks> <disk name='vda' snapshot='external'> </disk> </disks> </domainsnapshot> """ flags = 0 flags |= libvirt.VIR_DOMAIN_SNAPSHOT_CREATE_DISK_ONLY flags |= libvirt.VIR_DOMAIN_SNAPSHOT_CREATE_QUIESCE ret = dom.snapshotCreateXML(xmlDesc=xml, flags=flags) ``` ``` result [root@10k03 ~]# ls -lh /opt/Images/*sysdisk_by_xml -rw-------. 1 qemu qemu 194K 3月 20 23:52 /opt/Images/00d76a58-9637-4402-9739-21afd1246e06.sysdisk_by_xml -rw-------. 1 qemu qemu 1.2M 3月 21 00:03 /opt/Images/8d582c1c-355a-4297-9434-2f2f562c77df.sysdisk_by_xml ``` 。 Then, I search by google. see your page(https://www.redhat.com/archives/libvirt-users/2013-June/msg00102.html). Now, I want to ask you, was you found the way? -- James Iter

1 1

[libvirt-users] Persisting the libvirt guest's reason code.
by Tanmoy Sinha 20 Mar '18

20 Mar '18

Hi, I am currently facing an issue with libvirt w.r.t a guest's state and reason code. Precisely following are steps: 1. I have a running guest named *linux-test *on KVM 2. I do a * $> virsh save linux-test linux-saved.dat* 3. At this point * $> virsh domstate --reason linux-test *shows *shutoff(saved)* 4. I restarted the libvirtd daemon * $>systemctl restart libvirtd* 5. Now when I check for the domain state, * $> virsh domstate --reason linux-test *it reads *shutoff(unknown)* >From what I understand: The reason code for a particular state is maintained in-memory (no persistence in libvirt). Now when libvirtd restarts it queries the qemu monitor for all the running qemu processes and reassigns the state and reason. But for guests which are in shutoff state, there’s exists no QEMU instance for it, hence it has no way to know what was the last reason (i..e the default value 0 or UNKNOWN), but the state remains as shutfoff! Is there a patch for it? Or someway to retain the reason code across reboots and restart? Regards, Tanmoy Sinha

2 1

[libvirt-users] rtc_timeoffset libvirt patch
by Volodymyr Matviiv 19 Mar '18

19 Mar '18

Hello, Could you please clarify if below patch is going to be released every with some stable version of libvirt. Do you have any info which version? https://www.redhat.com/archives/libvir-list/2018-February/msg00981.html Thank you in advance for your answer.

2 1

[libvirt-users] Specify DNS and gateway for dnsmasq
by Gionatan Danti 16 Mar '18

16 Mar '18

Hi all, how I can set dhcp options as DNS, gateway, etc in libvirt's network definitions? From what I read here[1], I can use the <option> tag. However, I can not find nothing on libvirt official documentation. I am missing something? Thanks. [1] https://www.redhat.com/archives/libvir-list/2013-March/msg00166.html -- 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

4 6

[libvirt-users] qemu-img snapshot on running virtual machine
by Gionatan Danti 16 Mar '18

16 Mar '18

Hi all, I have a question about internal qcow2 snapshots of a live/running virtual machine taken via "qemu-img snapshot command". My question is: is it safe to execute the command above against a running machine? Or it will cause corruption? Naively I think it should *not* be safe, however, I would like a direct confirmation. Thanks. -- Danti Gionatan Supporto Tecnico Assyoma S.r.l. - www.assyoma.it email: g.danti(a)assyoma.it - info(a)assyoma.it GPG public key ID: FF5F32A8

3 4

[libvirt-users] Resource control is not supported on this host
by Allence 14 Mar '18

14 Mar '18

Libvirt release version V4.1.0 It add a element is cachetune After we add this, We can use host-cpu-cache But when i add it, my host get a error message: "Resource control is not supported on this host" Why? Following is my environment: kernel : 4.1.5, libvirt : 4.1.0 qemu : 2.9 host : lfs-7.0 my add cachetune in xml: <cachetune vcpus='0-3'> <cache id='1' level='3' type='data' size='3' unit='MiB'/> </cachetune>

4 4

[libvirt-users] Xen PVH Support in libvirt
by Tizian Lamatsch 14 Mar '18

14 Mar '18

Hello @ all, i wonder if there is any support for Xen PVH (https://wiki.xen.org/wiki/Xen_Project_Software_Overview) within libvirt. If i parse a xen native domU config file with 'virsh domxml-from-native' in which i set type='pvh' it changes it in the libvirt xml output to normal pv. Also the docs of libvirt do not state something like pvh. I am currently running Xen 4.10.0 with LibVirt 4.0.0. If it is not possible at the moment, can you please tell if this is a planned feature of libvirt? Thanks in advance for your help! Best Regards, Tizian

2 1

[libvirt-users] auto propagate interface status change
by John Lemon 13 Mar '18

13 Mar '18

1 0

[libvirt-users] libvirt connect vmware workstation fail
by 吴金灿 13 Mar '18

13 Mar '18

bash: vmwarews+ssh://jc@127.0.0.1/session: No such file or directory [jc@te ~]$ virsh -c vmwarews+ssh://jc@127.0.0.1/session 错误：连接到管理程序失败错误：不支持的操作：ssh 连接驱动程序不支持在没有套接字路径的情况下连接到会话实例 [jc@te ~]$ virsh -c vmwarews+ssh://root@127.0.0.1/session 错误：连接到管理程序失败错误：不支持的操作：ssh 连接驱动程序不支持在没有套接字路径的情况下连接到会话实例 [jc@te ~]$ virsh -c vmwarews:///session Segmentation fault (核心已转储)

2 1

[libvirt-users] KVM or Qemu
by Jamie Fargen 12 Mar '18

12 Mar '18

List- I know this may be slightly off topic and if so tell me to hit up the emu-discuss mailing list, but does anyone know how to detect the difference between a guest that is being fully emulates using qemu and a guest that is running para-virtualized using KVM? I have and when I inspect the CPUs I see the following.... # cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 13 model name : QEMU Virtual CPU version 1.5.3 stepping : 3 microcode : 0x1 cpu MHz : 1995.312 cache size : 4096 KB physical id : 0 siblings : 1 core id : 0 cpu cores : 1 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 4 wp : yes flags : fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pse36 clflush mmx fxsr sse sse2 syscall nx lm rep_good nopl pni cx16 hypervisor lahf_lm abm bogomips : 3990.62 clflush size : 64 cache_alignment : 64 address sizes : 46 bits physical, 48 bits virtual power management: # dmidecode # dmidecode 2.12-dmifs SMBIOS 2.4 present. 10 structures occupying 326 bytes. Table at 0x000F7190. Handle 0x0000, DMI type 0, 24 bytes BIOS Information Vendor: Seabios Version: 0.5.1 Release Date: 01/01/2011 Address: 0xE8000 Runtime Size: 96 kB ROM Size: 64 kB Characteristics: BIOS characteristics not supported Targeted content distribution is supported BIOS Revision: 1.0 Handle 0x0100, DMI type 1, 27 bytes System Information Manufacturer: Red Hat Product Name: KVM Version: RHEL 7.0.0 PC (i440FX + PIIX, 1996) Serial Number: Not Specified UUID: 1851A1FE-5ABB-42BD-B651-1A5931ADEE40 Wake-up Type: Power Switch SKU Number: Not Specified Family: Red Hat Enterprise Linux Handle 0x0300, DMI type 3, 20 bytes Chassis Information Manufacturer: Bochs Type: Other Lock: Not Present Version: Not Specified Serial Number: Not Specified Asset Tag: Not Specified Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: Unknown OEM Information: 0x00000000 Height: Unspecified Number Of Power Cords: Unspecified Handle 0x0401, DMI type 4, 32 bytes Processor Information Socket Designation: CPU 1 Type: Central Processor Family: Other Manufacturer: Bochs ID: D3 06 00 00 FD FB 8B 07 Version: Not Specified Voltage: Unknown External Clock: Unknown Max Speed: 2000 MHz Current Speed: 2000 MHz Status: Populated, Enabled Upgrade: Other L1 Cache Handle: Not Provided L2 Cache Handle: Not Provided L3 Cache Handle: Not Provided Since it is report a Qemu cpu and Manufacturer Bochs I am suspecting that it is qemu fully emulated vs KVM para-virtualized.

2 1

[libvirt-users] snapshot with libvirt tools or with lvm tools ?
by Lentes, Bernd 09 Mar '18

09 Mar '18

Hi, i asked already a time ago about snapshots. I have some guests, each resides in a raw file, placed on an ext3 fs which is on top of a logical volume, for each guest a dedicated lv. The raw is not a "must have", if there are obvious reasons i can convert them to a qcow2. What i want is a consistent backup of each guest taken overnight. If possible i won't have downtime. I can use the libvirt tools, but the lvm way seems to be more elegant. Before copying the file the guests resides in i take a snapshot from the respective lv. Then i mount the snapshot and transfer it via rsync on a CIFS share. Rsync seems to be the appropriate tool because i just transfer the changes in the file compared to the file from a day before. So i don't have to transfer complete and big raw files but just the difference. The guest still can be running, and after the transfer of the snapshot file i just delete it, and the next night the same procedure. What do you think ? 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 Muenchen Deutsches Forschungszentrum fuer Gesundheit und Umwelt (GmbH) Ingolstaedter Landstr. 1 85764 Neuherberg www.helmholtz-muenchen.de Aufsichtsratsvorsitzende: MinDir'in Baerbel Brumme-Bothe Geschaeftsfuehrer: Prof. Dr. Guenther Wess, Heinrich Bassler, Dr. Alfons Enhsen Registergericht: Amtsgericht Muenchen HRB 6466 USt-IdNr: DE 129521671

1 2

[libvirt-users] About .img file while creating vm
by amey pandit 09 Mar '18

09 Mar '18

Hi, I am trying to create vm using virsh create x.xml. But I am confused as what is the .img file that is required. Here is the Disk tag from my xml. <disk type='file' device='disk'> <driver name='qemu' type='qcow2'/> * <source file='/xxx/xx_vm.img'/> * <target dev='hda'/> </disk> Is it .ova file that is converted to .img ? If anybody have links or some guide related to the topic that would be really helpful. Thank you, Amey

2 1

[libvirt-users] Statistics domain memory block when domain shutdown
by llilulu 09 Mar '18

09 Mar '18

Hi My libvirt version is 3.4.0,host system is centos 7.4 ,kernel is 3.10.0-693.el7.x86_64 , when I shutdown domain in virtual system, My program call virDomainMemoryStats, My program blocked in this api. the call stack is #0 0x00007ff242d78a3d in poll () from /lib64/libc.so.6 #1 0x00007ff243755ce8 in virNetClientIOEventLoop () from /lib64/libvirt.so.0 #2 0x00007ff24375654b in virNetClientSendInternal () from /lib64/libvirt.so.0#3 0x00007ff2437579b3 in virNetClientSendWithReply () from /lib64/libvirt.so.0 #4 0x00007ff2437581c2 in virNetClientProgramCall () from /lib64/libvirt.so.0#5 0x00007ff24372d392 in callFull.isra.3 () from /lib64/libvirt.so.0 #6 0x00007ff24373b8a1 in remoteDomainMemoryStats () from /lib64/libvirt.so.0 #7 0x00007ff2436f14e2 in virDomainMemoryStats () from /lib64/libvirt.so.0 #8 0x00007ff22ee975c2 in VM::getMemoryStats (this=0x7ff1d4064ae0, Begin I think is my program problem, But when I use virsh domstats cmd , The cmd block too. In my program, I set timeout event for virConnectPtr. But my program blocked all the time. I find my system log, I find some libvirtd error: libvirtd: 2018-03-08 04:25:13.144+0000: 1289: error : virKeepAliveTimerInternal:143 : internal error: connection closed due to keepalive timeout Mar 7 23:33:05 localhost libvirtd: 2018-03-08 04:33:05.738+0000: 1289: error : virNetSocketReadWire:1808 : End of file while reading data: Input/output error Mar 7 23:33:14 localhost libvirtd: 2018-03-08 04:33:14.253+0000: 1289: error : virNetSocketReadWire:1808 : End of file while reading data: Input/output error Mar 7 23:33:16 localhost libvirtd: 2018-03-08 04:33:16.962+0000: 1289: error : virNetSocketReadWire:1808 : End of file while reading data: Input/output error Mar 7 23:33:25 localhost libvirtd: 2018-03-08 04:33:25.879+0000: 1300: warning : qemuDomainObjBeginJobInternal:3847 : Cannot start job (query, none) for domain d7bb3005-4fa4-4c3a-8802-ab55464d074b; current job is (query, none) owned by (1299 remoteDispatchDomainMemoryStats, 0 <null>) for (3680s, 0s) Mar 7 23:33:25 localhost libvirtd: 2018-03-08 04:33:25.879+0000: 1300: error : qemuDomainObjBeginJobInternal:3859 : Timed out during operation: cannot acquire state change lock (held by remoteDispatchDomainMemoryStats) Mar 7 23:33:25 localhost libvirtd: 2018-03-08 04:33:25.879+0000: 1300: warning : qemuGetProcessInfo:1428 : cannot parse process status data Mar 7 23:33:25 localhost libvirtd: 2018-03-08 04:33:25.880+0000: 1300: error : virNetDevTapInterfaceStats:751 : internal error: /proc/net/dev: Interface not found Mar 7 23:33:41 localhost libvirtd: 2018-03-08 04:33:41.826+0000: 1298: warning : qemuDomainObjBeginJobInternal:3847 : Cannot start job (query, none) for domain d7bb3005-4fa4-4c3a-8802-ab55464d074b; current job is (query, none) owned by (1299 remoteDispatchDomainMemoryStats, 0 <null>) for (3696s, 0s)Mar 7 23:33:41 localhost libvirtd: 2018-03-08 04:33:41.826+0000: 1298: error : qemuDomainObjBeginJobInternal:3859 : Timed out during operation: cannot acquire state change lock (held by remoteDispatchDomainMemoryStats) Is this problem a bug or I can't statistics some specifi status domain? Thanks

2 1

[libvirt-users] Lib virt v4.x packages for Xenial
by Stephen Bates 06 Mar '18

06 Mar '18

Hi Libvirt Users! Apologies in advance as I am sure this has been asked before (but I could not find it in the archives). Has anyone had any success creating .deb packages for Xenial for libvirt and libvirt-bin for v4.0 or v4.1? A quick scan of the PPA respository does not show anything this recent. Is there a fundamental issue that prevents these package files being created? If so has anyone got a primer for how best to install a recent version of libvirt and associated tools on Xenial? We have a bare-metal server we have to keep on LTS but I need to be able to run recent versions of QEMU to get access to certain NVMe model features that were only recently added... Cheers Stephen

1 0

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

05 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] Can't shutdown/reboot Windows 10 guest if on lock screen
by Sebastian Arcus 05 Mar '18

05 Mar '18

I am running Windows 10 vms on a Linux host with libvirt 4.0.0 and qemu 2.10.2 I can shutdown and reboot the Windows 10 guests if the no user is logged in the vm, or if the user is logged in and active/seeing the desktop. But after a while, when the lock screen kicks in (but the user is still logged in technically), the shutdown and reboot commands don't have any effect any more. Is there any way around this (except for disabling automatic screen locking on Windows)? Thank you for any hints.

1 0

[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] NIC cannot unplug
by llilulu 05 Mar '18

05 Mar '18

Hi: I encounter a promble, when I start a domain(only a blank disk, not install system), I can hotplug NIC, But I cannot hot unplug NIC. I consider the domain start from a blank disk, not install system, so the domain haven't virtio too, I suspect virtio problem. But I cann't confirm. Can any one tell me? Thanks

2 1

[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