- Users - libvirt List Archives

[libvirt-users] mkfs fails on qemu-nbd device
by Tanmoy Sinha 27 Jun '19

27 Jun '19

Hi All, I am unable to figure out the issue here, when I try to create a filesystem (ext4) on a virtual disk using qemu-nbd. This happens intermittently. Following is the sequence of commands:- $> qemu-img create -f qcow2 test.qcow2 30G $> qemu-nbd --connect=/dev/nbd0 test.qcow2 $> *mkfs.ext4 /dev/nbd0* * mkfs.ext4: Device size reported to be zero. Invalid partition specified, or* *Thu Jun 13 14:44:24 2019 partition table wasn't reread after running fdisk, due to* *Thu Jun 13 14:44:24 2019 a modified partition being busy and in use. You may need to reboot* *Thu Jun 13 14:44:24 2019 to re-read your partition table.* Following is the version details: root@localhost:~# qemu-img --version qemu-img version 2.8.1(Debian 1:2.8+dfsg-6+deb9u7) Copyright (c) 2003-2016 Fabrice Bellard and the QEMU Project developers root@localhost:~# qemu-nbd --version qemu-nbd version 0.0.1 Written by Anthony Liguori. Copyright (C) 2006 Anthony Liguori <anthony(a)codemonkey.ws>. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. root@localhost:~# uname -a Linux localhost 4.9.0-9-amd64 #1 SMP Debian 4.9.168-1+deb9u2 (2019-05-13) x86_64 GNU/Linux Regards Tanmoy Sinha

2 2

[libvirt-users] Intermittent live migration hang with ceph RBD attached volume
by Scott Sullivan 22 Jun '19

22 Jun '19

Software in use: *Source hypervisor:* *Qemu:* stable-2.12 branch *Libvirt*: v3.2-maint branch *OS*: CentOS 6 *Destination hypervisor: **Qemu:* stable-2.12 branch *Libvirt*: v4.9-maint branch *OS*: CentOS 7 I'm experiencing an intermittent live migration hang of a virtual machine (KVM) with a ceph RBD volume attached. At the high level what I see is that when this does happen, the virtual machine is left in a paused state (per virsh list) on both source and destination hypervisors indefinitely. Here's the virsh command I am running on the source (where 10.30.76.66 is the destination hypervisor): virsh migrate --live --copy-storage-all --verbose --xml > /root/live_migration.cfg test_vm qemu+ssh://10.30.76.66/system tcp:// > 10.30.76.66 Here it is in "ps faux" while its in the hung state: root 10997 0.3 0.0 380632 6156 ? Sl 12:24 0:26 > \_ virsh migrate --live --copy-storage-all --verbose --xml > /root/live_migration.cfg test_vm qemu+ssh://10.30.76.66/sys > root 10999 0.0 0.0 60024 4044 ? S 12:24 0:00 > \_ ssh 10.30.76.66 sh -c 'if 'nc' -q 2>&1 | grep "requires an argument" > >/dev/null 2>&1; then ARG=-q0;else ARG=;fi;'nc' $ARG -U The only reason i'm using the `--xml` arg is so the auth information can be updated for the new hypervisor (I setup a cephx user for each hypervisor). Below is a diff between my normal xml config and the one I passed in --xml arg to illustrate: 60,61c60,61 > < <auth username="source"> > < <secret type="ceph" > uuid="d4a47178-ab90-404e-8f25-058148da8446"/> > --- > > <auth username="destination"> > > <secret type="ceph" > uuid="72e9373d-7101-4a93-a7d2-6cce5ec1e6f1"/> The libvirt secret as shown above is properly setup with good credentials on both source and destination hypervisors. When this happens, I don't see anything logged on the destination hypervisor in the libvirt log. However in the source hypervisors log, I do see this: 2019-06-21 12:38:21.004+0000: 28400: warning : > qemuDomainObjEnterMonitorInternal:3764 : This thread seems to be the async > job owner; entering monitor without asking for a nested job is dangerous But nothing else logged in the libvirt log on either source or destination. The actual `virsh migrate --live` command pasted above still runs while stuck in this state, and it just outputs "Migration: [100 %]" over and over. If I strace the qemu process on the source, I see this over and over: ppoll([{fd=9, events=POLLIN}, {fd=8, events=POLLIN}, {fd=4, events=POLLIN}, > {fd=6, events=POLLIN}, {fd=15, events=POLLIN}, {fd=18, events=POLLIN}, > {fd=19, events=POLLIN}, {fd=35, events=0}, {fd=35, events=POLLIN}], 9, {0, > 14960491}, NULL, 8) = 0 (Timeout) Here's those fds: [root@source ~]# ll /proc/31804/fd/{8,4,6,15,18,19,35} > lrwx------ 1 qemu qemu 64 Jun 21 13:18 /proc/31804/fd/15 -> socket:[931291] > lrwx------ 1 qemu qemu 64 Jun 21 13:18 /proc/31804/fd/18 -> socket:[931295] > lrwx------ 1 qemu qemu 64 Jun 21 13:18 /proc/31804/fd/19 -> socket:[931297] > lrwx------ 1 qemu qemu 64 Jun 21 13:18 /proc/31804/fd/35 -> socket:[931306] > lrwx------ 1 qemu qemu 64 Jun 21 13:18 /proc/31804/fd/4 -> [signalfd] > lrwx------ 1 qemu qemu 64 Jun 21 13:18 /proc/31804/fd/6 -> [eventfd] > lrwx------ 1 qemu qemu 64 Jun 21 13:18 /proc/31804/fd/8 -> [eventfd] > [root@source ~]# > > [root@source ~]# grep -E '(931291|931295|931297|931306)' /proc/net/tcp > 3: 00000000:170C 00000000:0000 0A 00000000:00000000 00:00000000 > 00000000 107 0 931295 1 ffff88043a27f840 99 0 0 10 -1 > > 4: 00000000:170D 00000000:0000 0A 00000000:00000000 00:00000000 > 00000000 107 0 931297 1 ffff88043a27f140 99 0 0 10 -1 > > [root@source ~]# Further, on the source, if I query the blockjobs status, it says no blockjob is running: [root@source ~]# virsh list > Id Name State > ---------------------------------------------------- > 11 test_vm paused > [root@source ~]# virsh blockjob 11 vda > No current block job for vda > [root@source ~]# and that nc/ssh connection is still ok in the hung state: [root@source~]# netstat -tuapn|grep \.66 > tcp 0 0 10.30.76.48:48876 10.30.76.66:22 > ESTABLISHED 10999/ssh > [root@source ~]# > root 10999 0.0 0.0 60024 4044 ? S 12:24 0:00 > \_ ssh 10.30.76.66 sh -c 'if 'nc' -q 2>&1 | grep "requires an argument" > >/dev/null 2>&1; then ARG=-q0;else ARG=;fi;'nc' $ARG -U > /var/run/libvirt/libvirt-sock' Here's the state of the migration on source while its stuck like this: [root@source ~]# virsh qemu-monitor-command 11 '{"execute":"query-migrate"}' > > {"return":{"status":"completed","setup-time":2,"downtime":2451,"total-time":3753,"ram":{"total":2114785280,"postcopy-requests":0,"dirty-sync-count":3,"page-size":4096,"remaining":0,"mbps":898.199209,"transferred":421345514,"duplicate":414940,"dirty-pages-rate":0,"skipped":0,"normal-bytes":416796672,"normal":101757}},"id":"libvirt-317"} > [root@source ~]# I'm unable the run the above command on the destination while its in this state however, and get a lock error (which could be expected perhaps, since it never cutover to the source yet): [root@destination ~]# virsh list > Id Name State > ----------------------- > 4 test_vm paused > [root@destination ~]# virsh qemu-monitor-command 4 > '{"execute":"query-migrate"}' > error: Timed out during operation: cannot acquire state change lock (held > by monitor=remoteDispatchDomainMigratePrepare3Params) > [root@destination ~]# Does anyone have any pointers of other things I should check? Or if this was/is a known bug in perhaps the old stable-3.2? I haven't seen this when migrating on a host with libvirt 4.9 on both source and destinations. However the ones I have with the older 3.2 are centos 6 based, and aren't as easily upgraded to 4.9. Or, if anyone has ideas of patches I could potentially look to port to 3.2 to mitigate this, that would also be welcome. Would also be interested in forcing the cutover in this state if possible, though I suspect that isn't safe since the block-job isnt running while in this bad state. Thanks in advance

1 0

[libvirt-users] libvirtd does not update VM .xml configuration on filesystem after virsh blockcommit
by Saso Tavcar 20 Jun '19

20 Jun '19

Hi, Recently We've upgraded some KVM hosts from Fedora 29 to Fedora 30 and now experience broken VM configurations on filesystem after virsh blockcommit. Commands "virsh dumpxml ..." and "virsh dumpxml --inactive ..." is showing diffrent configuration than the one on filesystem. In case of restart libvirtd or system reboot, there are broken VM xml configurations on filesystem. Everything is OK on Fedora 29 KVM hosts! 0. XML configurations before snapshot is taken (all good, nothing found) [root@server1 ~]# cat /etc/libvirt/qemu/somedomain.com.ncloud.xml| grep BACK [root@server1 ~]# cat /etc/libvirt/qemu/somedomain.com.ncloud.xml| grep backingStore [root@server1 ~]# /usr/bin/virsh --quiet dumpxml somedomain.com.ncloud|grep BACK [root@server1 ~]# /usr/bin/virsh --quiet dumpxml somedomain.com.ncloud|grep backingStore [root@server1 ~]# /usr/bin/virsh --quiet dumpxml --inactive somedomain.com.ncloud|grep BACK [root@server1 ~]# /usr/bin/virsh --quiet dumpxml --inactive somedomain.com.ncloud|grep backingStore 1. When VM snapshot is taken with (all OK) /usr/bin/virsh --quiet snapshot-create-as --domain somedomain.com.ncloud .... there is a change of configuration, active, inactive and filesystem: - active (virsh dumpxml) [root@server1 ~]# /usr/bin/virsh --quiet dumpxml somedomain.com.ncloud|grep BACK <source file='/Virtualization/linux/somedomain.com/somedomain.com.ncloud.qcow2-BACKUPING_NOW'/> <source file='/Virtualization/linux/somedomain.com/somedomain.com.ncloud-swap.qcow2-BACKUPING_NOW'/> <source file='/Virtualization/linux/somedomain.com/somedomain.com.ncloud-data1.qcow2-BACKUPING_NOW'/> <source file='/Virtualization/linux/somedomain.com/somedomain.com.ncloud-data2.qcow2-BACKUPING_NOW'/> [root@server1 ~]# /usr/bin/virsh --quiet dumpxml somedomain.com.ncloud|grep backingStore <backingStore type='file'> </backingStore> <backingStore type='file'> </backingStore> <backingStore type='file'> </backingStore> <backingStore type='file'> </backingStore> - inactive (virsh dumpxml --inactive) [root@server1 ~]# /usr/bin/virsh --quiet dumpxml --inactive somedomain.com.ncloud|grep BACK <source file='/Virtualization/linux/somedomain.com/somedomain.com.ncloud.qcow2-BACKUPING_NOW'/> <source file='/Virtualization/linux/somedomain.com/somedomain.com.ncloud-swap.qcow2-BACKUPING_NOW'/> <source file='/Virtualization/linux/somedomain.com/somedomain.com.ncloud-data1.qcow2-BACKUPING_NOW'/> <source file='/Virtualization/linux/somedomain.com/somedomain.com.ncloud-data2.qcow2-BACKUPING_NOW'/> [root@server1 ~]# /usr/bin/virsh --quiet dumpxml --inactive somedomain.com.ncloud|grep backingStore <backingStore type='file'> </backingStore> <backingStore type='file'> </backingStore> <backingStore type='file'> </backingStore> <backingStore type='file'> </backingStore> - XML configuration on filesystem has changed [root@server1 ~]# ls -al /etc/libvirt/qemu/somedomain.com.ncloud.xml -rw-------. 1 root root 6260 Jun 18 23:00 /etc/libvirt/qemu/somedomain.com.ncloud.xml [root@server1 ~]# cat /etc/libvirt/qemu/somedomain.com.ncloud.xml |grep BACK <source file='/Virtualization/linux/somedomain.com/somedomain.com.ncloud.qcow2-BACKUPING_NOW'/> <source file='/Virtualization/linux/somedomain.com/somedomain.com.ncloud-swap.qcow2-BACKUPING_NOW'/> <source file='/Virtualization/linux/somedomain.com/somedomain.com.ncloud-data1.qcow2-BACKUPING_NOW'/> <source file='/Virtualization/linux/somedomain.com/somedomain.com.ncloud-data2.qcow2-BACKUPING_NOW'/> [root@server1 ~]# cat /etc/libvirt/qemu/somedomain.com.ncloud.xml |grep backingStore <backingStore type='file'> </backingStore> <backingStore type='file'> </backingStore> <backingStore type='file'> </backingStore> <backingStore type='file'> </backingStore> 2. When VM backup is done, data merged with virsh backcommit ..." and snapshot deleted (NOT OK!!!) ... /usr/bin/virsh --quiet blockcommit somedomain.com.ncloud sdd --active --pivot /usr/bin/virsh --quiet snapshot-delete --domain somedomain.com.ncloud somedomain.com.ncloud-SNAPSHOT --metadata there is a following state of VM configurations: - active (virsh dumpxml), [root@server1 ~]# /usr/bin/virsh --quiet dumpxml somedomain.com.ncloud|grep BACK ;;; OK [root@server1 ~]# /usr/bin/virsh --quiet dumpxml somedomain.com.ncloud|grep backingStore ;;; why is there empty backingStore left ??? <backingStore/> <backingStore/> <backingStore/> <backingStore/> - inactive [root@server1 qemu]# virsh dumpxml --inactive somedomain.com.ncloud |grep BACK ;;; OK [root@server1 qemu]# virsh dumpxml --inactive somedomain.com.ncloud |grep backingStore ;;; OK - XML on filesystem (.xml file on filesystem has not changed/reverted since snapshot has been taken - NOT OK!!!!, should be cleared of snapshot source file and backingStore) [root@server1 ~]# ls -al /etc/libvirt/qemu/somedomain.com.ncloud.xml -rw-------. 1 root root 6260 Jun 18 23:00 /etc/libvirt/qemu/somedomain.com.ncloud.xml [root@server1 qemu]# cat somedomain.com.ns2.xml |grep BACK <source file='/Virtualization/linux/somedomain.com/somedomain.com.ns2.qcow2-BACKUPING_NOW'/> [root@server1 qemu]# cat somedomain.com.ns2.xml |grep backingStore <backingStore type='file' index='1'> </backingStore> ############################################################################################################################################################################## - Fedora 29 has libvirt 4.7.0 and qemu 3.0.1: [root@solaris1 ~]# rpm -qa |grep libvirt-daemon-kvm libvirt-daemon-kvm-4.7.0-3.fc29.x86_64 [root@solaris1 ~]# rpm -qa |grep qemu-system-x86 qemu-system-x86-core-3.0.1-3.fc29.x86_64 qemu-system-x86-3.0.1-3.fc29.x86_64 - Fedora 30 has libvirt 5.1.0 and qemu 3.1.0: [root@server1 ~]# rpm -qa |grep libvirt-daemon-kvm libvirt-daemon-kvm-5.1.0-8.fc30.x86_64 [root@server1 ~]# rpm -qa |grep qemu-system-x86 qemu-system-x86-3.1.0-8.fc30.x86_64 qemu-system-x86-core-3.1.0-8.fc30.x86_64 For every VM from "virsh list" we do following steps (in script) for VM backup: /usr/bin/virsh --quiet domblklist somedomain.com.ncloud /usr/bin/virsh --quiet dumpxml --inactive somedomain.com.ncloud > /Backuping/VMs/Daily/somedomain.com.ncloud.xml /usr/bin/virsh --quiet snapshot-create-as --domain somedomain.com.ncloud somedomain.com.ncloud-SNAPSHOT --diskspec sda,file=/Virtualization/linux/somedomain.com/somedomain.com.ncloud.qcow2-B… --diskspec sdb,file=/Virtualization/linux/somedomain.com/somedomain.com.ncloud-swap.qc… --diskspec sdc,file=/Virtualization/linux/somedomain.com/somedomain.com.ncloud-data1.q… --diskspec sdd,file=/Virtualization/linux/somedomain.com/somedomain.com.ncloud-data2.q… --disk-only --atomic --quiesce /usr/bin/virsh --quiet snapshot-list somedomain.com.ncloud /usr/bin/scp -p server1.somedomain.us:/Virtualization/linux/somedomain.com/somedomain.com.n… somedomain.com.ncloud.qcow2 /usr/bin/scp -p server1.somedomain.us:/Virtualization/linux/somedomain.com/somedomain.com.n… somedomain.com.ncloud-swap.qcow2 /usr/bin/scp -p server1.somedomain.us:/Virtualization/linux/somedomain.com/somedomain.com.n… somedomain.com.ncloud-data1.qcow2 /usr/bin/scp -p server1.somedomain.us:/Virtualization/linux/somedomain.com/somedomain.com.n… somedomain.com.ncloud-data2.qcow2 /usr/bin/virsh --quiet blockcommit somedomain.com.ncloud sda --active --pivot /usr/bin/virsh --quiet blockcommit somedomain.com.ncloud sdb --active --pivot /usr/bin/virsh --quiet blockcommit somedomain.com.ncloud sdc --active --pivot /usr/bin/virsh --quiet blockcommit somedomain.com.ncloud sdd --active --pivot /usr/bin/virsh --quiet snapshot-delete --domain somedomain.com.ncloud somedomain.com.ncloud-SNAPSHOT --metadata /usr/bin/ssh server1.somedomain.us "/usr/bin/rm /Virtualization/linux/somedomain.com/somedomain.com.ncloud.qcow2-BACKUPING_NOW" /usr/bin/ssh server1.somedomain.us "/usr/bin/rm /Virtualization/linux/somedomain.com/somedomain.com.ncloud-swap.qcow2-BACKUPING_NOW" /usr/bin/ssh server1.somedomain.us "/usr/bin/rm /Virtualization/linux/somedomain.com/somedomain.com.ncloud-data1.qcow2-BACKUPING_NOW" /usr/bin/ssh server1.somedomain.us "/usr/bin/rm /Virtualization/linux/somedomain.com/somedomain.com.ncloud-data2.qcow2-BACKUPING_NOW" /usr/bin/pigz --best --rsyncable somedomain.com.ncloud.qcow2 /usr/bin/pigz --best --rsyncable somedomain.com.ncloud-swap.qcow2 /usr/bin/pigz --best --rsyncable somedomain.com.ncloud-data1.qcow2 /usr/bin/pigz --best --rsyncable somedomain.com.ncloud-data2.qcow2 There is no error on script (commands) execution: [root@server1 ~]# /Backuping/bin/simple_KVM_backup.pl --depth 7 --path Daily --hosting_server server1.somedomain.us ###Backuping VM somedomain.com.ncloud: + Moving somedomain.com.ncloud.xml.06 to somedomain.com.ncloud.xml.07. + Moving somedomain.com.ncloud.qcow2.gz.06 to somedomain.com.ncloud.qcow2.gz.07. ... + Disk snapshot somedomain.com.ncloud-SNAPSHOT for somedomain.com.ncloud ... Domain snapshot somedomain.com.ncloud-SNAPSHOT created Name Creation Time State ----------------------------------------------------------------------- somedomain.com.ncloud-SNAPSHOT 2019-06-18 23:00:04 +0200 disk-snapshot Done! + Time scp start : 2019-06-18 23:00:05 somedomain.com.ncloud.qcow2 100% 20GB 401.3MB/s 00:51 Done! somedomain.com.ncloud-swap.qcow2 100% 4097MB 483.5MB/s 00:08 Done! somedomain.com.ncloud-data1.qcow2 100% 100GB 400.7MB/s 04:15 Done! somedomain.com.ncloud-data2.qcow2 100% 100GB 440.6MB/s 03:52 Done! + Time scp end : 2019-06-18 23:09:14 + Time blockcommit start : 2019-06-18 23:09:14 Successfully pivoted Successfully pivoted Successfully pivoted Successfully pivoted + Time blockcommit end : 2019-06-18 23:09:16 + Snapshot delete ... Domain snapshot somedomain.com.ncloud-SNAPSHOT deleted Done! + Delete snapshot files ... Done! + Time compress start : 2019-06-18 23:09:17 Regards, saso

3 2

[libvirt-users] Libvirt API for getting disk capacity from VM XML
by Varsha Verma 15 Jun '19

15 Jun '19

Hello everyone, I am doing an outreachy internship at Openstack Ironic. In the sushy-tools project, we are using libvirt VMs to simulate bare metal machines for testing purposes. In the XML description of a domain, there are a bunch of disk elements giving information about the various storage devices attached to the domain. Is there some way to get the size/capacity of those disks using the libvirt API? -- *Regards,* *Varsha Verma* *Fourth Year Undergraduate* *Department of Electrical Engineering* *IIT-BHU, Varanasi*

2 1

[libvirt-users] blockcommit of domain not successfull
by Lentes, Bernd 14 Jun '19

14 Jun '19

Hi, i have several domains running on a 2-node HA-cluster. Each night i create snapshots of the domains, after copying the consistent raw file to a CIFS server i blockcommit the changes into the raw files. That's running quite well. But recent the blockcommit didn't work for one domain: I create a logfile from the whole procedure: =============================================================== ... Sat Jun 1 03:05:24 CEST 2019 Target Source ------------------------------------------------ vdb /mnt/snap/severin.sn hdc - /usr/bin/virsh blockcommit severin /mnt/snap/severin.sn --verbose --active --pivot Block commit: [ 0 %]Block commit: [ 15 %]Block commit: [ 28 %]Block commit: [ 35 %]Block commit: [ 43 %]Block commit: [ 53 %]Block commit: [ 63 %]Block commit: [ 73 %]Block commit: [ 82 %]Block commit: [ 89 %]Block commit: [ 98 %]Block commit: [100 %]Target Source ------------------------------------------------ vdb /mnt/snap/severin.sn ... ============================================================== The libvirtd-log says (it's UTC IIRC): ============================================================= ... 2019-05-31 20:31:34.481+0000: 4170: error : qemuMonitorIO:719 : internal error: End of file from qemu monitor 2019-06-01 01:05:32.233+0000: 4170: error : qemuMonitorIO:719 : internal error: End of file from qemu monitor 2019-06-01 01:05:43.804+0000: 22605: warning : qemuGetProcessInfo:1461 : cannot parse process status data 2019-06-01 01:05:43.848+0000: 22596: warning : qemuGetProcessInfo:1461 : cannot parse process status data 2019-06-01 01:06:11.438+0000: 26112: warning : qemuDomainObjBeginJobInternal:4865 : Cannot start job (destroy, none) for doma in severin; current job is (modify, none) owned by (5372 remoteDispatchDomainBlockJobAbort, 0 <null>) for (39s, 0s) 2019-06-01 01:06:11.438+0000: 26112: error : qemuDomainObjBeginJobInternal:4877 : Timed out during operation: cannot acquire state change lock (held by remoteDispatchDomainBlockJobAbort) 2019-06-01 01:06:13.976+0000: 5369: warning : qemuGetProcessInfo:1461 : cannot parse process status data 2019-06-01 01:06:14.028+0000: 22596: warning : qemuGetProcessInfo:1461 : cannot parse process status data 2019-06-01 01:06:44.165+0000: 5371: warning : qemuGetProcessInfo:1461 : cannot parse process status data 2019-06-01 01:06:44.218+0000: 22605: warning : qemuGetProcessInfo:1461 : cannot parse process status data 2019-06-01 01:07:14.343+0000: 5369: warning : qemuGetProcessInfo:1461 : cannot parse process status data 2019-06-01 01:07:14.387+0000: 22598: warning : qemuGetProcessInfo:1461 : cannot parse process status data 2019-06-01 01:07:44.495+0000: 22605: warning : qemuGetProcessInfo:1461 : cannot parse process status data ... =========================================================== and "cannot parse process status data" continuously until the end of the logfile. The syslog from the domain itself didn't reveal anything, it just continues to run. The libvirt log from the domains just says: qemu-system-x86_64: block/mirror.c:864: mirror_run: Assertion `((&bs->tracked_requests)->lh_first == ((void *)0))' failed. Hosts are SLES 12 SP4 with libvirt-daemon-4.0.0-8.9.1.x86_64. Bernd -- Bernd Lentes Systemadministration Institut für Entwicklungsgenetik Gebäude 35.34 - Raum 208 HelmholtzZentrum münchen bernd.lentes(a)helmholtz-muenchen.de phone: +49 89 3187 1241 phone: +49 89 3187 3827 fax: +49 89 3187 2294 http://www.helmholtz-muenchen.de/idg wer Fehler macht kann etwas lernen wer nichts macht kann auch nichts lernen Helmholtz Zentrum Muenchen Deutsches Forschungszentrum fuer Gesundheit und Umwelt (GmbH) Ingolstaedter Landstr. 1 85764 Neuherberg www.helmholtz-muenchen.de Stellv. Aufsichtsratsvorsitzender: MinDirig. Dr. Manfred Wolter Geschaeftsfuehrung: Prof. Dr. med. Dr. h.c. Matthias Tschoep, Heinrich Bassler, Kerstin Guenther Registergericht: Amtsgericht Muenchen HRB 6466 USt-IdNr: DE 129521671

2 11

[libvirt-users] Using qemu active blockcommit results in 'Permission denied' error
by Marcus Hoffmann 13 Jun '19

13 Jun '19

Hello all, I tried following this guide: https://wiki.libvirt.org/page/Live-disk-backup-with-active-blockcommit Unfortunately when I try to do the final virsh blockcommit step I always get the following error: error: internal error: unable to execute QEMU command 'block-commit': Could not reopen file: Permission denied I checked directory und image file permissions, app-armor profiles (set to complain mode for now.) and libvirt logs but nothing there gives me any hints what might be going wrong. This is on a debian buster system, using libvirtd (libvirt) 5.0.0 qemu 3.1+dfsg-7 I would appreciate any hints on how to proceed/get more debug info on this. Thanks! Marcus

2 7

[libvirt-users] lxc - pass filesystem off host's automounts
by lejeczek 11 Jun '19

11 Jun '19

hi guys in my qutest I have this: ... <filesystem type='mount' accessmode='passthrough'> <source dir='/home'/> <target dir='/home'/> </filesystem> ... and on the host /home/* are user home dirs which are automounted off a glusterfs volume. The guest starts okey, I can see dirs under /home but if I go to /home/userA I get: ls: cannot access /home/userA/: Too many levels of symbolic links Do you know if what I'm trying should just work a okey? many thanks, L.

2 2

[libvirt-users] Same host migration
by Sukrit Bhatnagar 10 Jun '19

10 Jun '19

Hi, I have been selected for GSoC'19 under qemu and was trying out migration of the pvrdma device. For my current task, I need to perform a "null" migration i.e. migrate the VM to the same host for testing purpose. I am using libvirt 5.1.0 on Fedora 30. >From what I know, libvirt does not allow this type of migration by default. Trying this: virsh migrate --unsafe --verbose fedora29 qemu+unix:///system results in the following error: error: internal error: Attempt to migrate guest to the same host dell Is there some way I can get this to work? If the solution requires changing the source code, then that is also fine. Using qemu-system-x86_64 to perform migration allows same-host migration. I need the same functionality using virsh as libvirt performs some additional servicing which is required for the device I am migrating. Thanks, Sukrit

3 2

[libvirt-users] Cloud automation
by Adrien Macor 10 Jun '19

10 Jun '19

Hi, I have a question for you: Let’s suppose I have three physical servers; two on the same area, and the last one elsewhere (not on the same network, but all three have connectivity between each others). May I use this infrastructure with libvirt? I mean in terms of cloud automation: is it possible to remotely deploy VMs (with particulary configurations) with libvirt? For example, is it possible to have one master node controlling the two others? Thanks for the reply

3 2

Re: [libvirt-users] Easy solution for custom firewall rules-
by Joshua Kramer 04 Jun '19

04 Jun '19

Nakta wrote: > libvirts nwfilter module can achieve that. I read over those resources and I did what I thought would be correct, but it's not having any effect. I created a new nwfilter like this: <filter name='allow-virbr2-vpn' chain='ipv4' priority='-700'> <rule action='accept' direction='in' priority='500'> <all state='ESTABLISHED'/> </rule> <rule action='accept' direction='out' priority='500'> <all state='ESTABLISHED,RELATED'/> </rule> <rule action='accept' direction='in' priority='100'> <ip dstipaddr='192.168.8.0' dstipmask='24'/> </rule> <rule action='accept' direction='out' priority='100'> <ip srcipaddr='192.168.8.0' srcipmask='24'/> </rule> <rule action='drop' direction='inout' priority='500'> <all/> </rule> </filter> I then associated that filter with the Interface device on the VM server within KVM... and shutdown/restart that VM. <interface type='network'> <mac address='XX:XX:XX:XX:XX:XX'/> <source network='locservers'/> <model type='virtio'/> <filterref filter='allow-virbr2-vpn'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> After this, nothing happens. I did 'ebtables --list', and the new rules aren't there. I also did the same with iptables as well as firewalld itself. The new rules are nowhere to be found. What did I do incorrectly here? Thanks! -JK

2 1

[libvirt-users] Easy solution for custom firewall rules- is it possible?
by Joshua Kramer 04 Jun '19

04 Jun '19

Hello All- I've looked in several places and haven't found an answer to this question: is it possible to have libvirt add custom rules to iptables for virtual network interfaces? I took a look at the "Firewall and Network Filtering in Libvirt" page and it seems overly complicated for what I want to do. Given an interface virbr2 and its network 192.168.4.0/24, libvirt installs the following rules in iptables. Essentially, these rules will drop any packets for the interface virbr2 where the source or destination is not on the 192.168.4.0/24 network. -P FORWARD ACCEPT -A FORWARD -d 192.168.4.0/24 -o virbr2 -j ACCEPT -A FORWARD -s 192.168.4.0/24 -i virbr2 -j ACCEPT -A FORWARD -i virbr2 -o virbr2 -j ACCEPT -A FORWARD -o virbr2 -j REJECT --reject-with icmp-port-unreachable -A FORWARD -i virbr2 -j REJECT --reject-with icmp-port-unreachable I have a VPN server on the 4/24 network- and it hands out addresses in the 8/24 network. So I would like libvirt to also create the following rules in iptables: -A FORWARD -d 192.168.8.0/24 -o virbr2 -j ACCEPT -A FORWARD -s 192.168.8.0/24 -i virbr2 -j ACCEPT I've tried creating direct rules in firewalld for the FORWARD_direct chain. Firewalld happily creates those rules, but they are never reached, because they fall AFTER the libvirt rules. I've also tried creating an IP address on the virbr2 interface in the 8/24 network, but that doesn't work either. How can I get this done? Thanks!! -JK

3 2

[libvirt-users] logging of domains
by Lentes, Bernd 30 May '19

30 May '19

Hi, recently i had some domains stopped without any obvious reason for me. Unfortunately i didn't find the cause. I'd like to log information about the domains that i have more information the next time this will happen. In /etc/libvirt/libvirtd.conf i have: log_level = 3 log_outputs="3:file:/var/log/libvirt/libvirtd.log" which creates enormous log files, but with logrotate and xz i can manage that. But i think this is just related to libvirtd. The logs for the domains under /var/log/libvirt/qemu are poor and very small, nearly no information. Is there a way to be more verbose with the domains so that i may find helpful information in these logs when the domains stop for the next time ? Thanks. Bernd -- Bernd Lentes Systemadministration Institut für Entwicklungsgenetik Gebäude 35.34 - Raum 208 HelmholtzZentrum münchen bernd.lentes(a)helmholtz-muenchen.de phone: +49 89 3187 1241 phone: +49 89 3187 3827 fax: +49 89 3187 2294 http://www.helmholtz-muenchen.de/idg wer Fehler macht kann etwas lernen wer nichts macht kann auch nichts lernen Helmholtz Zentrum Muenchen Deutsches Forschungszentrum fuer Gesundheit und Umwelt (GmbH) Ingolstaedter Landstr. 1 85764 Neuherberg www.helmholtz-muenchen.de Stellv. Aufsichtsratsvorsitzender: MinDirig. Dr. Manfred Wolter Geschaeftsfuehrung: Prof. Dr. med. Dr. h.c. Matthias Tschoep, Heinrich Bassler, Kerstin Guenther Registergericht: Amtsgericht Muenchen HRB 6466 USt-IdNr: DE 129521671

2 1

[libvirt-users] libvirt blkiotune mechanism
by Maksym Isaiev 30 May '19

30 May '19

Hello! We are using oVirt in our infrastructure, which uses libvirt as backend. Last time we needed to activate storage QoS aka libvirt blkiotune parameters. So some questions appeared about how libvirt limitation mechanism works: 1. What happened to overlimit storage traffic in small time period after we apply blkiotune parameters on high loaded virtual machine on fly: a) All over-limit traffic pulled into some queue, where all disk transactions can be successfully finished with QoS throughput? b) All over-limitation data dropped and opened transactions state became failed? c) All active transactions finishes on speed beyond blkiotune parameters limit, but all new transactions immediately are limited based on configured limits? Thanks in advance!

1 0

[libvirt-users] Snapshot of single block device
by jarek 29 May '19

29 May '19

Hello! I have a guest with one qcow2 disk image (vda) and one physical partition (sda) from host. When I'm trying to get snapshot with: virsh snapshot-create-as ..... It fails with message: error: unsupported configuration: source for disk 'sda' is not a regular file; refusing to generate external snapshot name I understand, that it is not possible to make a snapshot of physical device, but it is enough for me to take snapshot of vda. How to force virsh to ignore sda ? best regards Jarek

2 3

[libvirt-users] [Libvirt failed to claim Virtual Functions on hostdev network after VM reboot]
by Fuzail Ahmad 29 May '19

29 May '19

Problem Statement: Libvirt failed to claim Virtual Functions on hostdev network after VM reboot. Version-Release number of selected component (if applicable): libvirtd (libvirt) 2.0.0 kernel-4.1.12-112.16.4.el7uek.x86_64 Reproducible: Not always Description: I am doing a reboot of Virtual machines and sometimes one of the VM does not start and fail with the following error In total I have spun 3 VMs out of which 2 gets started and 1 of them fail with the below error. [root@sriov2 ~]# virsh start VM3 error: Failed to attach interface error: internal error: network 'hostnet' requires exclusive access to interfaces, but none are available [root@sriov2 ~]# virsh net-dumpxml hostnet <network connections='2'> <name>hostnet</name> <uuid>c1fb4ead-21b8-4d69-8ad9-669c55b3dfc7</uuid> <forward mode='hostdev' managed='yes'> <address type='pci' domain='0x0000' bus='0x0f' slot='0x10' function='0x0'/> <address type='pci' domain='0x0000' bus='0x0f' slot='0x10' function='0x2'/> </forward> </network> However, "ip link show" command shows 8 VFs in total. # ip link show ens2 ens2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc mq state UP mode DEFAULT qlen 1000 link/ether 00:0a:f7:d5:a7:50 brd ff:ff:ff:ff:ff:ff vf 0 MAC 52:54:00:6d:7c:a0, spoof checking off, link-state auto vf 1 MAC 52:54:00:44:c9:b6, spoof checking off, link-state auto vf 2 MAC 52:54:00:30:7a:86, spoof checking off, link-state auto vf 3 MAC c6:9a:1b:82:90:ea, spoof checking off, link-state auto vf 4 MAC 46:db:e2:33:c7:a4, spoof checking off, link-state auto vf 5 MAC 76:65:e1:f7:82:78, spoof checking off, link-state auto vf 6 MAC 8e:a0:8b:e5:1a:66, spoof checking off, link-state auto vf 7 MAC ba:f4:83:19:80:bf, spoof checking off, link-state auto # Please, letme know if I need to attach any additional information. Regards Fuzail

3 2

[libvirt-users] libvirtd not starting
by Lothar Schilling 22 May '19

22 May '19

Hi everybody, I've set up an new CentOS 7.6.1810 server. Then, via yum I installed qemu-kvm libvirt libvirt-python libguestfs-tools virt-install. There were no problems. But when I try to systemctl start libvirtd I get the following message: "libvirtd: process 472: arguments to dbus_message_iter_append_basic() were incorrect, assertion "_dbus_check_is_valid_utf8 (*string_p)" failed in file ../../dbus/dbus-message.c line 2754." Starting libvirtd manually just by issuing the command "libvirtd" without any further arguments is working, though. I do not have the slightest idea what is going on, especially as I didn't change anything about the config files. Any help would be appreciated, thank you Lothar Schilling

3 8

[libvirt-users] VM bootup got failed with systemd/dbus error messages
by PRIYANKA M A 22 May '19

22 May '19

We are having one server machine (ubuntu 16.04 OS) with 10 VMs. When the server is rebooted, some VMs got failed to boot with systemd/dbus error messages. Rebooting the affected VMs resolves this issue. Jan 30 20:40:02 VM systemd[1]: Failed to subscribe to NameOwnerChanged signal for 'org.freedesktop.DisplayManager': Connection timed out Jan 30 20:40:02 VM systemd[1]: Failed to subscribe to NameOwnerChanged signal for 'org.freedesktop.NetworkManager': Connection timed out Jan 30 20:40:02 VM systemd[1]: Failed to subscribe to NameOwnerChanged signal for 'org.freedesktop.login1': Connection timed out Jan 30 20:40:02 VM systemd[1]: Failed to subscribe to NameOwnerChanged signal for 'org.freedesktop.Accounts': Connection timed out Jan 30 20:40:02 VM systemd[1]: Failed to subscribe to NameOwnerChanged signal for 'org.freedesktop.Avahi': Connection timed out Jan 30 20:40:02 VM systemd[1]: Failed to subscribe to NameOwnerChanged signal for 'org.freedesktop.ModemManager1': Connection timed out Jan 30 20:40:02 VM systemd[1]: Failed to subscribe to activation signal: Connection timed out Jan 30 20:40:02 VM systemd[1]: Failed to register name: Connection timed out Jan 30 20:40:02 VM systemd[1]: Failed to set up API bus: Connection timed out an 30 20:40:32 VM dbus[1009]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Jan 30 20:40:32 VM systemd-logind[998]: Failed to enable subscription: Failed to activate service 'org.freedesktop.systemd1': timed out Jan 30 20:40:32 VM systemd-logind[998]: Failed to fully start up daemon: Connection timed out Host machine specifications:- OS : Ubuntu 16.04 Kernel : 4.15.0-47-generic CPUs : 48 ( 2*12*2) RAM : 64G VM specifications:- OS : Ubuntu 16.04 Kernel : 4.13.16 CPUs : 8 RAM : 4G Attached the full log file. Kindly help us to resolve this issue with a permanent fix. *With Best Regards,* M A PRIYANKA VVDN Technologies Pvt Ltd *Cell : * +91 8489574081 | *Skype :* priyankamathavan27 -- _Disclaimer: _© 2019 VVDN Technologies Pvt. Ltd. This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful.__

1 0

[libvirt-users] GVT-g - suboptimal user experience
by Alex Ivanov 20 May '19

20 May '19

Hi. In the current state of gvt-g the user experience is suboptimal. So my question is what are the ETAs for following features: 1. Accelerated virt-manager console using gvt-g device 2. Custom resolutions or dynamic resolution 3. UEFI VMs support (Windows guest) Thanks.

4 6

[libvirt-users] virtio-user intarfece
by Avi Cohen 19 May '19

19 May '19

Hello all i have multiple workload containers connected to my DPDK-app. I have another special container - which all packets are mirrored to it. Is it possible for zero-copy reason - that all virtio interfaces shared memory between my DPDK-app and workload containers - can be accessed by this special container ? it means that for every workload container X this is a shared memory between the:

1 1

Re: [libvirt-users] [libvirt] surprising <backingStore type='file'> setting in domain.xml
by Thomas Stein 17 May '19

17 May '19

(switched to libvirt-users as it seems to be more appropriate) On 2019-05-16 23:02, Eric Blake wrote: > On 5/16/19 10:20 AM, Thomas Stein wrote: >> Hello all. >> >> My currently used versions: libvirt-5.2.0 and qemu-4.0.0. >> >> Here is my problem. I'm struggeling since a few weeks with a strange >> behaviour by either qemu or libvirt. After a reboot of >> the hardware node the $domain.xml contains suddenly a backingStore >> setting which was not there before reboot. >> Something like that: >> >> <devices> >> <emulator>/usr/bin/qemu-system-x86_64</emulator> >> <disk type='file' device='disk'> >> <driver name='qemu' type='qcow2'/> >> <source >> file='/var/lib/libvirt/shinymail/shinymail_weekly.qcow2-2019-05-15'/> >> <backingStore type='file'> >> <format type='qcow2'/> >> <source file='/var/lib/libvirt/images/shinymail.qcow2'/> > > Yes, this matches: > >> </backingStore> >> <target dev='vda' bus='virtio'/> >> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' >> function='0x0'/> >> </disk> >> ... >> >> This obviousely happens after a backup has been running. The Backup >> Script looks like this: >> >> <snip> >> virsh snapshot-create-as --domain shinymail weekly --diskspec >> vda,file=/var/lib/libvirt/shinymail/shinymail_weekly.qcow2-$(date >> +%Y-%m-%d) --disk-only --atomic --no-metadata > > the effects of this command. > > Ultimately, I'm TRYING to get my new 'virsh domain-backup' command > integrated into the next libvirt release, which has the advantage of > performing a backup WITHOUT having to modify the <domain> XML. But > until > that happens, any time you use 'virsh snapshot-create-as' as part of a > sequence for performing backups, you ARE modifying the <domain> XML, > and > if you want to revert to the external backup, or if... Cool. Will it be in 5.4.0 already? >> >> cp ... >> >> virsh blockcommit shinymail vda --active --verbose --pivot >> <snip> > > ...blockcommit fails for whatever reason to undo the effects of > 'snapshot-create-as' in creating a temporary overlay, then yes, you do > have to worry about the temporary overlay being in the way, where > you'll > have to manually edit the <domain> definition to match the actual disk > layouts you really want. So you're saying blockcommit fails me somehow? What i'm asking myself is, why does this problem suddenly appear. It worked literally for years this way. thanks for your answer Eric. cheers t. >> >> So after that "dmblklist shinymail" does show the right source file >> but >> after a reboot it tries to use the weekly snapshot >> again which leads to filesystem errors. >> >> Someone has an idea what could cause such a behaviour? >>

1 0

[libvirt-users] surprising <backingStore type='file'> setting in domain.xml
by Thomas Stein 17 May '19

17 May '19

Hello all. My currently used versions: libvirt-5.2.0 and qemu-4.0.0. Here is my problem. I'm struggeling since a few weeks with a strange behaviour by either qemu or libvirt. After a reboot of the hardware node the $domain.xml contains suddenly a backingStore setting which was not there before reboot. Something like that: <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2'/> <source file='/var/lib/libvirt/shinymail/shinymail_weekly.qcow2-2019-05-15'/> <backingStore type='file'> <format type='qcow2'/> <source file='/var/lib/libvirt/images/shinymail.qcow2'/> </backingStore> <target dev='vda' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </disk> ... This obviousely happens after a backup has been running. The Backup Script looks like this: <snip> virsh snapshot-create-as --domain shinymail weekly --diskspec vda,file=/var/lib/libvirt/shinymail/shinymail_weekly.qcow2-$(date +%Y-%m-%d) --disk-only --atomic --no-metadata cp ... virsh blockcommit shinymail vda --active --verbose --pivot <snip> So after that "dmblklist shinymail" does show the right source file but after a reboot it tries to use the weekly snapshot again which leads to filesystem errors. Someone has an idea what could cause such a behaviour? cheers t. -- libvir-list mailing list libvir-list(a)redhat.com https://www.redhat.com/mailman/listinfo/libvir-list

1 0

[libvirt-users] domain still running although snapshot-file is deleted !?!
by Lentes, Bernd 15 May '19

15 May '19

Hi, i have a strange situation: A domain is still running where domblklist points to a snapshot file and also dumpxml says the current drive is that snapshot file. But the file has been deleted hours ago. And the domain is still running. I can login via ssh, the database and the webserver are still running, domain is performant. How can that be ? Also lsof shows that the file is deleted: qemu-syst 27007 qemu 15ur REG 254,14 335609856 183599 /mnt/snap/sim.sn (deleted) qemu-syst 27007 qemu 16ur REG 254,14 335609856 183599 /mnt/snap/sim.sn (deleted) qemu-syst 27007 27288 qemu 15ur REG 254,14 335609856 183599 /mnt/snap/sim.sn (deleted) qemu-syst 27007 27288 qemu 16ur REG 254,14 335609856 183599 /mnt/snap/sim.sn (deleted) CPU\x200/ 27007 27308 qemu 15ur REG 254,14 335609856 183599 /mnt/snap/sim.sn (deleted) CPU\x200/ 27007 27308 qemu 16ur REG 254,14 335609856 183599 /mnt/snap/sim.sn (deleted) CPU\x201/ 27007 27309 qemu 15ur REG 254,14 335609856 183599 /mnt/snap/sim.sn (deleted) CPU\x201/ 27007 27309 qemu 16ur REG 254,14 335609856 183599 /mnt/snap/sim.sn (deleted) vnc_worke 27007 27321 qemu 15ur REG 254,14 335609856 183599 /mnt/snap/sim.sn (deleted) vnc_worke 27007 27321 qemu 16ur REG 254,14 335609856 183599 /mnt/snap/sim.sn (deleted) Bernd -- Bernd Lentes Systemadministration Institut für Entwicklungsgenetik Gebäude 35.34 - Raum 208 HelmholtzZentrum münchen bernd.lentes(a)helmholtz-muenchen.de phone: +49 89 3187 1241 phone: +49 89 3187 3827 fax: +49 89 3187 2294 http://www.helmholtz-muenchen.de/idg wer Fehler macht kann etwas lernen wer nichts macht kann auch nichts lernen Helmholtz Zentrum Muenchen Deutsches Forschungszentrum fuer Gesundheit und Umwelt (GmbH) Ingolstaedter Landstr. 1 85764 Neuherberg www.helmholtz-muenchen.de Stellv. Aufsichtsratsvorsitzender: MinDirig. Dr. Manfred Wolter Geschaeftsfuehrung: Prof. Dr. med. Dr. h.c. Matthias Tschoep, Heinrich Bassler, Kerstin Guenther Registergericht: Amtsgericht Muenchen HRB 6466 USt-IdNr: DE 129521671

2 1

[libvirt-users] domains paused without any obvious reason
by Lentes, Bernd 15 May '19

15 May '19

Hi, i have a two node HA-Cluster with several domains as resources. Currently it's running in test mode. Some domains (all on the same host) stopped running, virsh list shows them as "paused". All stopped at the same time (11th of may, 7:00 am), my monitoring system began to yell. I don't have any clue why this happened. virsh domblkerror says for all the domains (5) "no space". The days before the domains were running fine and i know that all disks inside the domain should have enough space. Also the host is not running out of space. The logs don't say anything sensefully, unfortunately i didn't have a log for the libvirtd daemon, i just configured that now. The domains are stopped each day by cron at 10:30 pm for a short moment, a snapshot is taken, domains are started again, the backing file is copied to a CIFS server and if that is finished the snapshot is blockcommited into the backing file. That's working fine already for several days. This cronjob creates a log and it's looking fine. The domains reside in naked Logical Volumes, the respective Volume Group has enough space. Bernd -- Bernd Lentes Systemadministration Institut für Entwicklungsgenetik Gebäude 35.34 - Raum 208 HelmholtzZentrum münchen bernd.lentes(a)helmholtz-muenchen.de phone: +49 89 3187 1241 phone: +49 89 3187 3827 fax: +49 89 3187 2294 http://www.helmholtz-muenchen.de/idg wer Fehler macht kann etwas lernen wer nichts macht kann auch nichts lernen Helmholtz Zentrum Muenchen Deutsches Forschungszentrum fuer Gesundheit und Umwelt (GmbH) Ingolstaedter Landstr. 1 85764 Neuherberg www.helmholtz-muenchen.de Stellv. Aufsichtsratsvorsitzender: MinDirig. Dr. Manfred Wolter Geschaeftsfuehrung: Prof. Dr. med. Dr. h.c. Matthias Tschoep, Heinrich Bassler, Kerstin Guenther Registergericht: Amtsgericht Muenchen HRB 6466 USt-IdNr: DE 129521671

2 3

[libvirt-users] VM display is blank when open (but Gnome Boxes thumbnails ok)
by Michel Rozpendowski 14 May '19

14 May '19

Hi, I also posted this question on the IRC #virt channel but have not received any reaction at the moment of posting this message to the mailing list. Since I last turned off my laptop (Dell XPS-15-9570 running Ubuntu 19.04) on Friday 10 May (I had to do it by long power press by the way), I am no longer able to get the display of my VMs: I am getting a black screen, even though I can see it running in the thumbnail of Gnome Boxes. You can see the described behaviour on the following video capture: https://youtu.be/Lv67g0foyzc. Troubleshooting Log from Gnome Boxes is available here: https://pastebin.com/9eWGYsJV. It was working all properly on Friday before I turn off my laptop. Any clue what could be wrong and how I could solve this issue (I digged the Internet for 2 hours without success)? Thanks in advance for your help! Kind regards, Michel

2 2

[libvirt-users] Cannot get interface MTU - qemu quest fails to start off OpenVswitch
by lejeczek 13 May '19

13 May '19

hi guys I have a qemu guest and openvswitch bridge and the guest fails to start: $ virsh start work8 error: Failed to start domain work8-vm-win2016 error: Cannot get interface MTU on 'ovsbr0': No such device LXC guest which uses the same source network starts just fine. I'm on Centos 7 with openvswitch-2.9.0-3.el7.x86_64 from centos-openstack-pike repo and libvirt-4.5.0-10.el7_6.7.x86_64. Would anybody care to suggest a possible reson(s) causing the failure? many thanks, L.

2 6