May 2015 - Users - libvirt List Archives

[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] virDomainCoreDumpWithFormat files created as root
by NoxDaFox 18 Nov '15

18 Nov '15

Greetings, I am dumping a guest VM memory for inspection using the command "virDomainCoreDumpWithFormat" and the created files appear to belong to root (both user and group). I have searched around but didn't find any answer. Is there a way to instruct QEMU to create those files under a different user? Thank you.

5 7

[libvirt-users] Snapshots vs filesystem shares
by anonym 27 Jun '15

27 Jun '15

[Please keep me Cc:ed since I'm not subscribed to the list!] Hi list, The tl;dr; is: with Libvirt/QEMU, should it be possible to mount a filesystem share (of type='mount') after restoring from a snapshot that was taken when the filesystem share wasn't mounted? It's pretty clear that Libvirt/QEMU (currently, at least) doesn't support taking snapshots of a live guest which has active filesystem shares (type='mount'). I get this error: Call to virDomainSaveFlags failed: internal error: unable to execute QEMU command 'migrate': Migration is disabled when VirtFS export path '${TARGET_PATH}' is mounted in the guest using mount_tag '$TAG' (Libvirt::Error) I have a use case where I very much would like this combination. It wouldn't be a problem if the filesystem shares would have to be temporarily unmounted while taking the snapshot, and mounted again after restoring it. However, while trying that, `mount` hangs when trying to mount a filesystem share again *after* restoring the snapshot (unmounting and remounting works perfectly before that, of course). Nothing is reported in syslog. I've also tried unloading combinations of the various 9p and virtio related modules (like 9p, 9pnet_virtio, 9pnet, virtio, etc) before taking the snapshot, and then reload them after restoring it, in hope of getting them into a sane state again (or whatever is the issue). But then I've seen errors like this in syslog: 9pnet: Installing 9P2000 support virtio-pci 0000:00:08.0: irq 42 for MSI/MSI-X virtio-pci 0000:00:08.0: irq 43 for MSI/MSI-X virtio-pci 0000:00:08.0: irq 42 for MSI/MSI-X virtio-pci 0000:00:08.0: irq 43 for MSI/MSI-X 9pnet_virtio: probe of virtio3 failed with error -2 FS-Cache: Loaded 9p: Installing v9fs 9p2000 file system support FS-Cache: Netfs '9p' registered for caching 9pnet_virtio: no channels available and `mount` complains that the source (tag) doesn't exist when trying to mount the filesystem share again. For the record, the mount command I always use is simply: mount -t 9p -o trans=virtio $TAG $TARGET_DIR I've tried setting `-o debug=0xfff` but I get no debug info at all. Is it expected behaviour that filesystem shares get into a broken state after restoring a snapshot? If it's of any relevance, here's some more context: * The host is running Debian Jessie with Linux 3.16.7-ckt9-3~deb8u1, Libvirt 1.2.9, QEMU 2.1. * The guest is Tails (https://tails.boum.org) which is Debian Wheezy with Linux 3.16.7-ckt9-3. I doubt it matters since I tested this ~two years ago, and got (IIRC) the exact same results. Cheers!

1 1

Re: [libvirt-users] [ovirt-users] Bug in Snapshot Removing
by Soeren Malchow 11 Jun '15

11 Jun '15

Small addition again: This error shows up in the log while removing snapshots WITHOUT rendering the Vms unresponsive — Jun 01 01:33:45 mc-dc3ham-compute-02-live.mc.mcon.net libvirtd[1657]: Timed out during operation: cannot acquire state change lock Jun 01 01:33:45 mc-dc3ham-compute-02-live.mc.mcon.net vdsm[6839]: vdsm vm.Vm ERROR vmId=`56848f4a-cd73-4eda-bf79-7eb80ae569a9`::Error getting block job info Traceback (most recent call last): File "/usr/share/vdsm/virt/vm.py", line 5759, in queryBlockJobs… — From: Soeren Malchow <soeren.malchow(a)mcon.net<mailto:soeren.malchow@mcon.net>> Date: Monday 1 June 2015 00:56 To: "libvirt-users(a)redhat.com<mailto:libvirt-users@redhat.com>" <libvirt-users(a)redhat.com<mailto:libvirt-users@redhat.com>>, users <users(a)ovirt.org<mailto:users@ovirt.org>> Subject: [ovirt-users] Bug in Snapshot Removing Dear all I am not sure if the mail just did not get any attention between all the mails and this time it is also going to the libvirt mailing list. I am experiencing a problem with VM becoming unresponsive when removing Snapshots (Live Merge) and i think there is a serious problem. Here are the previous mails, http://lists.ovirt.org/pipermail/users/2015-May/033083.html The problem is on a system with everything on the latest version, CentOS 7.1 and ovirt 3.5.2.1 all upgrades applied. This Problem did NOT exist before upgrading to CentOS 7.1 with an environment running ovirt 3.5.0 and 3.5.1 and Fedora 20 with the libvirt-preview repo activated. I think this is a bug in libvirt, not ovirt itself, but i am not sure. The actual file throwing the exception is in VDSM (/usr/share/vdsm/virt/vm.py, line 697). We are very willing to help, test and supply log files in anyway we can. Regards Soeren

3 12

[libvirt-users] Freeze Windows Guests For Consistent Storage Snapshots
by Payes Anand 09 Jun '15

09 Jun '15

Hi, Is it possible to freeze windows guests for a consistent storage level snapshot. I am using openstack icehouse on centos 6.6 Hypervisor: KVM Libvirt: 0.10.2 Qemu: 0.10.2 Guest OS: Windows 7 and Windows Server 2008 I was able to freeze Centos guests by issuing the command: virsh qemu-agent-command <guest_ID> '{"execute":"guest-fsfreeze-freeze"}' For CentOS guests, I enabled access between compute nodes and guests through a socket by setting metadata parameter, hw_qemu_guest_agent=yes for the guest image. And then installing qemu-guest-agent inside the guest. What steps do i have to follow for windows ? Regars, Payes

2 2

[libvirt-users] Bug in Snapshot Removing
by Soeren Malchow 01 Jun '15

01 Jun '15

Dear all I am not sure if the mail just did not get any attention between all the mails and this time it is also going to the libvirt mailing list. I am experiencing a problem with VM becoming unresponsive when removing Snapshots (Live Merge) and i think there is a serious problem. Here are the previous mails, http://lists.ovirt.org/pipermail/users/2015-May/033083.html The problem is on a system with everything on the latest version, CentOS 7.1 and ovirt 3.5.2.1 all upgrades applied. This Problem did NOT exist before upgrading to CentOS 7.1 with an environment running ovirt 3.5.0 and 3.5.1 and Fedora 20 with the libvirt-preview repo activated. I think this is a bug in libvirt, not ovirt itself, but i am not sure. The actual file throwing the exception is in VDSM (/usr/share/vdsm/virt/vm.py, line 697). We are very willing to help, test and supply log files in anyway we can. Regards Soeren

2 1

[libvirt-users] snapshots and vmdk
by Boylan, Ross 01 Jun '15

01 Jun '15

Does libvirt support snapshotting when the virtual disk comes from a vmdk file? http://wiki.libvirt.org/page/Snapshots#Desired_functionality seems to say no, since it says "'virsh snapshot', which requires all disk images to be qcow2". OTOH, man virsh, http://libvirt.org/formatsnapshot.html, and http://libvirt.org/formatdomain.html#elementsDisks seem to indicate more flexibility, though I see nothing about vmdk. If there is support for vmdk, is it just for external snapshots, or do internal snapshots work? Currently running libvirt 0.9.12, qemu-kvm 1.1.2 (though I could use vmware workstation), linux kernel 3.2.0. Thanks. Ross Boylan

2 2

[libvirt-users] Block Commit: [100 %]error: failed to pivot job for disk vda (Bug filed)
by Matthew Schumacher 01 Jun '15

01 Jun '15

Hello List, Seems like blockcopy --wait doesn't work work qemu-2.2.x. I found someone else having the same problem, but it never went anywhere: https://www.redhat.com/archives/libvirt-users/2015-January/msg00045.html I went ahead and did some more debugging and created a bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1210903 I'm going to do some more debugging and hopefully figure this out, but wanted it to post it here so that it gets more attention. Thanks, schu

2 4

[libvirt-users] libvirt and VMWare Workstation Shared Server mode (of GSX history)
by vincent＠cojot.name 31 May '15

31 May '15

Hi everyone, I searched previous postings and I couldn't find a definitive answer on this.. I run a small lab of RHEL/Centos Based servers on which there's VMWare Workstation running on a non-standard port but still manageable by tools like VMrun (and the Fusion of Workstation GUI, of course). I'm trying to use virsh with this setup and getting the following error from both RHEL6 and RHEL7: $ virsh -c esx://user1@server1:943/?no_verify=1 Enter user1's password for server1: error: internal error Expecting product 'gsx' or 'esx' or 'embeddedEsx' or 'vpx' but found 'ws' error: failed to connect to the hypervisor I tried 'gsx' as a type too but to no avail. The mode that I'm using is called by vmware a 'ws-shared' mode..: $ /usr/bin/vmrun -T ws-shared -h https://localhost:943/sdk -u user1 listRegisteredVM Host password: Total registered VMs: 35 [ha-datacenter/standard] VCS41_node1/VCS4.vmx [ha-datacenter/standard] VCS41_node2/VCS4.vmx [ha-datacenter/standard] VCS41_node3/VCS4.vmx [ha-datacenter/standard] VCS41_node4/VCS4.vmx [ha-datacenter/standard] VCS51_node1/VCS5.vmx [ha-datacenter/standard] VCS51_node2/VCS5.vmx [ha-datacenter/standard] VCS51_node3/VCS5.vmx [ha-datacenter/standard] VCS51_node4/VCS5.vmx [ha-datacenter/standard] DOS622/dos.vmx [ha-datacenter/standard] Solaris8/solaris8.vmx [ha-datacenter/standard] Solaris10/solaris10.vmx [ha-datacenter/standard] VCS60_node1/VCS6.vmx [ha-datacenter/standard] VCS60_node2/VCS6.vmx [ha-datacenter/standard] MacOSX_107/Mac_OS_X_Lion.vmx [...] Would that be something easy to hack/add for the libvirt versions I'm using? (RHEL6/7) even if this means recompiling some src.rpms.. Any suggestions? Thanks, ,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-, Vincent S. Cojot, Computer Engineering. STEP project. _.,-*~'`^`'~*-,._.,-*~ Ecole Polytechnique de Montreal, Comite Micro-Informatique. _.,-*~'`^`'~*-,. Linux Xview/OpenLook resources page _.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~' http://step.polymtl.ca/~coyote _.,-*~'`^`'~*-,._ coyote(a)NOSPAM4cojot.name They cannot scare me with their empty spaces Between stars - on stars where no human race is I have it in me so much nearer home To scare myself with my own desert places. - Robert Frost

2 2

[libvirt-users] whats the holdup on whql signed virtio drivers?
by pixelfairy 31 May '15

31 May '15

why is it so hard to get signed virtio drivers? is it politics? a license issue? can someone with involved with or knows of these decisions comment? dont want to start a thread of speculation. we all know all where that leads and i dont want it drowing out any answers.

1 0

[libvirt-users] Virsh and VBox
by Daniel Barney Briseño 29 May '15

29 May '15

Hello to everyone, I am setting up an OpenStack environment with Virtual Box on my MacBook Pro. I am running VBox: 4.3 Virsh: 1.2.14 And when I try to connect to the Hypervisor, I get the following error. DBARNEY-M-DNTF:~ dbarney$ virsh -c vbox+ssh://dbarney@192.168.56.101 setlocale: No such file or directory error: failed to connect to the hypervisor error: internal error: received hangup / error event on socket Where 192.168.56.101 is a Ubuntu guess VM. Could you please indicate me what I am missing Thank you all!!! Daniel Barney CCIE #47842

1 0

[libvirt-users] routed network and physical interface
by Giovanni Tirloni 28 May '15

28 May '15

Hello, I've created a routed network that forwards to a physical interface: <network> <name>default</name> <forward dev='eth0' mode='route'/> <mac address='52:54:00:f2:5b:4f'/> <ip address='192.168.100.1' netmask='255.255.255.0'> <dhcp> <range start='192.168.100.10' end='192.168.100.20'/> </dhcp> </ip> </network> When this network is started, the iptables rules are associated with eth0, as expected. However, the "virbr0" bridge interface that is create automatically does not contain the eth0 interface. I have to manually run "brctl addif virbr0 eth0" so the guests can communicate with the outside. I was under the impression libvirt would add the physical interface automatically, based on the <forward> definition. Is it how it should work? Giovanni

2 1

[libvirt-users] Standalone KVM boot from USB ?
by Matt . 25 May '15

25 May '15

Hi Guys, I'm looking for a solution so I can boot a HyperVisor from USB which I can manage through Foreman and also Manually if needed. ESXi can do so, but I'm looking for an opensource solution. KVM would be best but I wonder if there is a way to create some sort of live environment where only KVM settings are written to the USB disk and not that much logging and so on. Has anyone an idea about some persistent USBkey setup or so ? Ideas are very welcome! Thanks, Matt

2 2

[libvirt-users] unable to edit existing snapshot
by NoxDaFox 25 May '15

25 May '15

Greetings, due to hardware failure I had to replace my workstation which has a different CPU. I have a VM with several snapshots and I need to revert to a specific one. While reverting to it, I get an error due to unsupported CPU features. Therefore, I try to edit the snapshot XML through the command: virsh snapshot-edit <domain_name> <snapshot_name> When I save the changes I get the error message: error: intermal error: unexpected domain snapshot <snapshot_name> already exists Tried to look around for solution but didn't find any information related to my problem. Am I doing something wrong? It's quite critical for me to be able to revert to that state of the machine. Is there any chance to do so via libvirt? Thank you.

4 5

[libvirt-users] Shutdown Windows Server 2012 acpi
by Dominique Ramaekers 24 May '15

24 May '15

Hi, I've got a virtual Windows server 2012 R2 running on lib-virt and qemu. I've enabled acpi in the VM settings and edited following registry keys: HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System\Shutdownwithoutlogon to 1 HKLM\Microsoft\Windows NT\CurrentVersion\Windows\ShutdownWarningDialogTimeout to 10 This worked fine until there was a second user that loged in through mstsc and didn't log off. Looking on forums and blogs I couldn't find a solution for this. Any help would be appreciated... Greetings, Dominique.

1 0

[libvirt-users] libvirt with gcc5 Test failing
by Athenas Jimenez 23 May '15

23 May '15

Hello! I'm trying to compile libvirt using GCC 5.1 but one of the test are failing and I have no idea why :( Hopefully someone of you could help me, here part of my log: ========================================== libvirt 1.2.14: tests/test-suite.log ========================================== # TOTAL: 109 # PASS: 107 # SKIP: 1 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: qemuxml2argvtest ====================== TEST: qemuxml2argvtest ........................................ 40 ....................!..!................ 80 ........................................ 120 ........................................ 160 ........................................ 200 ........................................ 240 ........................................ 280 ........................................ 320 ..........!.!..!........................ 360 ........................................ 400 ........................................ 440 ........!! 450 FAIL FAIL qemuxml2argvtest (exit status: 1) ******************************************************************************** Running using "$ VIR_TEST_DEBUG=2 make check" 1) QEMU XML-2-ARGV minimal ... OK 2) QEMU XML-2-ARGV minimal-no-memory ... OK 3) QEMU XML-2-ARGV minimal-msg-timestamp ... OK 4) QEMU XML-2-ARGV minimal-s390 ... OK 5) QEMU XML-2-ARGV machine-aliases1 ... OK 6) QEMU XML-2-ARGV machine-aliases2 ... OK 7) QEMU XML-2-ARGV machine-core-on ... OK 8) QEMU XML-2-ARGV machine-core-off ... OK 9) QEMU XML-2-ARGV machine-core-on ... Got expected error: unsupported configuration: dump-guest-core is not available with this QEMU binary OK 10) QEMU XML-2-ARGV machine-core-on ... Got expected error: unsupported configuration: dump-guest-core is not available with this QEMU binary OK 11) QEMU XML-2-ARGV machine-usb-opt ... OK 12) QEMU XML-2-ARGV kvm ... OK 13) QEMU XML-2-ARGV boot-cdrom ... OK 14) QEMU XML-2-ARGV boot-network ... OK 15) QEMU XML-2-ARGV boot-floppy ... OK 16) QEMU XML-2-ARGV boot-multi ... OK 17) QEMU XML-2-ARGV boot-menu-enable ... OK 18) QEMU XML-2-ARGV boot-menu-enable ... OK 19) QEMU XML-2-ARGV boot-menu-enable-with-timeout ... OK 20) QEMU XML-2-ARGV boot-menu-enable-with-timeout ... Got expected error: unsupported configuration: splash timeout is not supported by this QEMU binary OK 21) QEMU XML-2-ARGV boot-menu-enable-with-timeout-invalid ... OK 22) QEMU XML-2-ARGV boot-menu-disable ... OK 23) QEMU XML-2-ARGV boot-menu-disable-drive ... OK 24) QEMU XML-2-ARGV boot-menu-disable-drive-bootindex ... OK 25) QEMU XML-2-ARGV boot-dev+order ... OK 26) QEMU XML-2-ARGV boot-order ... OK 27) QEMU XML-2-ARGV boot-complex ... OK 28) QEMU XML-2-ARGV boot-complex-bootindex ... OK 29) QEMU XML-2-ARGV boot-strict ... OK 30) QEMU XML-2-ARGV reboot-timeout-disabled ... OK 31) QEMU XML-2-ARGV reboot-timeout-enabled ... OK 32) QEMU XML-2-ARGV reboot-timeout-enabled ... Got expected error: unsupported configuration: reboot timeout is not supported by this QEMU binary OK 33) QEMU XML-2-ARGV bios ... OK 34) QEMU XML-2-ARGV bios-nvram ... OK 35) QEMU XML-2-ARGV clock-utc ... OK 36) QEMU XML-2-ARGV clock-localtime ... OK 37) QEMU XML-2-ARGV clock-localtime-basis-localtime ... OK 38) QEMU XML-2-ARGV clock-variable ... OK 39) QEMU XML-2-ARGV clock-france ... OK 40) QEMU XML-2-ARGV clock-hpet-off ... OK 41) QEMU XML-2-ARGV clock-catchup ... OK 42) QEMU XML-2-ARGV cpu-kvmclock ... OK 43) QEMU XML-2-ARGV cpu-host-kvmclock ... OK 44) QEMU XML-2-ARGV kvmclock ... OK 45) QEMU XML-2-ARGV clock-timer-hyperv-rtc ... OK 46) QEMU XML-2-ARGV cpu-eoi-disabled ... OK 47) QEMU XML-2-ARGV cpu-eoi-enabled ... OK 48) QEMU XML-2-ARGV controller-order ... OK 49) QEMU XML-2-ARGV eoi-disabled ... OK 50) QEMU XML-2-ARGV eoi-enabled ... OK 51) QEMU XML-2-ARGV pv-spinlock-disabled ... OK 52) QEMU XML-2-ARGV pv-spinlock-enabled ... OK 53) QEMU XML-2-ARGV kvmclock+eoi-disabled ... OK 54) QEMU XML-2-ARGV hyperv ... OK 55) QEMU XML-2-ARGV hyperv-off ... OK 56) QEMU XML-2-ARGV kvm-features ... OK 57) QEMU XML-2-ARGV kvm-features-off ... OK 58) QEMU XML-2-ARGV pmu-feature ... OK 59) QEMU XML-2-ARGV pmu-feature-off ... OK 60) QEMU XML-2-ARGV hugepages ... OK 61) QEMU XML-2-ARGV hugepages-pages ... libvirt: error : unsupported configuration: NUMA node 1 is unavailable FAILED 62) QEMU XML-2-ARGV hugepages-pages2 ... OK 63) QEMU XML-2-ARGV hugepages-pages3 ... OK 64) QEMU XML-2-ARGV hugepages-shared ... libvirt: error : unsupported configuration: NUMA node 1 is unavailable FAILED 65) QEMU XML-2-ARGV hugepages-memaccess-invalid ... OK 66) QEMU XML-2-ARGV hugepages-pages4 ... Got expected error: unsupported configuration: NUMA node 1 is unavailable OK 67) QEMU XML-2-ARGV hugepages-pages5 ... OK 68) QEMU XML-2-ARGV hugepages-pages6 ... OK 69) QEMU XML-2-ARGV nosharepages ... OK 70) QEMU XML-2-ARGV disk-cdrom ... OK 71) QEMU XML-2-ARGV disk-iscsi ... OK 72) QEMU XML-2-ARGV disk-cdrom-network-http ... OK 73) QEMU XML-2-ARGV disk-cdrom-network-https ... OK 74) QEMU XML-2-ARGV disk-cdrom-network-ftp ... OK 75) QEMU XML-2-ARGV disk-cdrom-network-ftps ... OK 76) QEMU XML-2-ARGV disk-cdrom-network-tftp ... OK 77) QEMU XML-2-ARGV disk-cdrom-empty ... OK 78) QEMU XML-2-ARGV disk-cdrom-tray ... OK 79) QEMU XML-2-ARGV disk-cdrom-tray-no-device-cap ... OK 80) QEMU XML-2-ARGV disk-floppy ... OK 81) QEMU XML-2-ARGV disk-floppy-tray-no-device-cap ... OK 82) QEMU XML-2-ARGV disk-floppy-tray ... OK 83) QEMU XML-2-ARGV disk-virtio-s390 ... OK 84) QEMU XML-2-ARGV disk-many ... OK 85) QEMU XML-2-ARGV disk-virtio ... OK 86) QEMU XML-2-ARGV disk-virtio-ccw ... OK 87) QEMU XML-2-ARGV disk-virtio-ccw-many ... OK 88) QEMU XML-2-ARGV disk-virtio-scsi-ccw ... OK 89) QEMU XML-2-ARGV disk-order ... OK 90) QEMU XML-2-ARGV disk-xenvbd ... OK 91) QEMU XML-2-ARGV disk-drive-boot-disk ... OK 92) QEMU XML-2-ARGV disk-drive-boot-cdrom ... OK 93) QEMU XML-2-ARGV floppy-drive-fat ... OK 94) QEMU XML-2-ARGV disk-drive-fat ... OK 95) QEMU XML-2-ARGV disk-drive-readonly-disk ... OK 96) QEMU XML-2-ARGV disk-drive-readonly-no-device ... OK 97) QEMU XML-2-ARGV disk-drive-fmt-qcow ... OK 98) QEMU XML-2-ARGV disk-drive-shared ... OK 99) QEMU XML-2-ARGV disk-drive-cache-v1-wt ... OK 100) QEMU XML-2-ARGV disk-drive-cache-v1-wb ... OK 101) QEMU XML-2-ARGV disk-drive-cache-v1-none ... OK 102) QEMU XML-2-ARGV disk-drive-error-policy-stop ... OK 103) QEMU XML-2-ARGV disk-drive-error-policy-enospace ... OK 104) QEMU XML-2-ARGV disk-drive-error-policy-wreport-rignore ... OK 105) QEMU XML-2-ARGV disk-drive-cache-v2-wt ... OK 106) QEMU XML-2-ARGV disk-drive-cache-v2-wb ... OK 107) QEMU XML-2-ARGV disk-drive-cache-v2-none ... OK 108) QEMU XML-2-ARGV disk-drive-cache-directsync ... OK 109) QEMU XML-2-ARGV disk-drive-cache-unsafe ... OK 110) QEMU XML-2-ARGV disk-drive-copy-on-read ... OK 111) QEMU XML-2-ARGV disk-drive-network-nbd ... OK 112) QEMU XML-2-ARGV disk-drive-network-nbd-export ... OK 113) QEMU XML-2-ARGV disk-drive-network-nbd-ipv6 ... OK 114) QEMU XML-2-ARGV disk-drive-network-nbd-ipv6-export ... OK 115) QEMU XML-2-ARGV disk-drive-network-nbd-unix ... OK 116) QEMU XML-2-ARGV disk-drive-network-iscsi ... OK 117) QEMU XML-2-ARGV disk-drive-network-iscsi-auth ... OK 118) QEMU XML-2-ARGV disk-drive-network-iscsi-lun ... OK 119) QEMU XML-2-ARGV disk-drive-network-gluster ... OK 120) QEMU XML-2-ARGV disk-drive-network-rbd ... OK 121) QEMU XML-2-ARGV disk-drive-network-sheepdog ... OK 122) QEMU XML-2-ARGV disk-drive-network-rbd-auth ... OK 123) QEMU XML-2-ARGV disk-drive-network-rbd-ipv6 ... OK 124) QEMU XML-2-ARGV disk-drive-network-rbd-no-colon ... Got expected error: unsupported configuration: ':' not allowed in RBD source volume name 'poolname/imagename:rbd_cache=1:rbd_cache_size=67108864:rbd_cache_max_dirty=0' OK 125) QEMU XML-2-ARGV disk-drive-no-boot ... OK 126) QEMU XML-2-ARGV disk-usb ... OK 127) QEMU XML-2-ARGV disk-usb-device ... OK 128) QEMU XML-2-ARGV disk-usb-device-removable ... OK 129) QEMU XML-2-ARGV disk-scsi-device ... OK 130) QEMU XML-2-ARGV disk-scsi-device-auto ... OK 131) QEMU XML-2-ARGV disk-scsi-disk-split ... OK 132) QEMU XML-2-ARGV disk-scsi-disk-wwn ... OK 133) QEMU XML-2-ARGV disk-scsi-disk-vpd ... OK 134) QEMU XML-2-ARGV disk-scsi-disk-vpd-build-error ... Got expected error: unsupported configuration: Only scsi disk supports vendor and product OK 135) QEMU XML-2-ARGV disk-scsi-vscsi ... OK 136) QEMU XML-2-ARGV disk-scsi-virtio-scsi ... OK 137) QEMU XML-2-ARGV disk-virtio-scsi-num_queues ... OK 138) QEMU XML-2-ARGV disk-virtio-scsi-cmd_per_lun ... OK 139) QEMU XML-2-ARGV disk-virtio-scsi-max_sectors ... OK 140) QEMU XML-2-ARGV disk-scsi-megasas ... OK 141) QEMU XML-2-ARGV disk-sata-device ... OK 142) QEMU XML-2-ARGV disk-aio ... OK 143) QEMU XML-2-ARGV disk-source-pool ... OK 144) QEMU XML-2-ARGV disk-source-pool-mode ... OK 145) QEMU XML-2-ARGV disk-ioeventfd ... OK 146) QEMU XML-2-ARGV disk-copy_on_read ... OK 147) QEMU XML-2-ARGV disk-drive-discard ... OK 148) QEMU XML-2-ARGV disk-snapshot ... OK 149) QEMU XML-2-ARGV event_idx ... OK 150) QEMU XML-2-ARGV virtio-lun ... OK 151) QEMU XML-2-ARGV disk-scsi-lun-passthrough ... OK 152) QEMU XML-2-ARGV disk-serial ... OK 153) QEMU XML-2-ARGV graphics-vnc ... OK 154) QEMU XML-2-ARGV graphics-vnc-socket ... OK 155) QEMU XML-2-ARGV graphics-vnc-websocket ... OK 156) QEMU XML-2-ARGV graphics-vnc-policy ... OK 157) QEMU XML-2-ARGV graphics-vnc-sasl ... OK 158) QEMU XML-2-ARGV graphics-vnc-tls ... OK 159) QEMU XML-2-ARGV graphics-sdl ... OK 160) QEMU XML-2-ARGV graphics-sdl-fullscreen ... OK 161) QEMU XML-2-ARGV nographics ... OK 162) QEMU XML-2-ARGV nographics-vga ... OK 163) QEMU XML-2-ARGV graphics-spice ... OK 164) QEMU XML-2-ARGV graphics-spice-sasl ... OK 165) QEMU XML-2-ARGV graphics-spice-agentmouse ... OK 166) QEMU XML-2-ARGV graphics-spice-compression ... OK 167) QEMU XML-2-ARGV graphics-spice-timeout ... OK 168) QEMU XML-2-ARGV graphics-spice-qxl-vga ... OK 169) QEMU XML-2-ARGV graphics-spice-usb-redir ... OK 170) QEMU XML-2-ARGV graphics-spice-agent-file-xfer ... OK 171) QEMU XML-2-ARGV input-usbmouse ... OK 172) QEMU XML-2-ARGV input-usbtablet ... OK 173) QEMU XML-2-ARGV misc-acpi ... OK 174) QEMU XML-2-ARGV misc-disable-s3 ... OK 175) QEMU XML-2-ARGV misc-disable-suspends ... OK 176) QEMU XML-2-ARGV misc-enable-s4 ... OK 177) QEMU XML-2-ARGV misc-enable-s4 ... Got expected error: unsupported configuration: setting ACPI S4 not supported OK 178) QEMU XML-2-ARGV misc-no-reboot ... OK 179) QEMU XML-2-ARGV misc-uuid ... OK 180) QEMU XML-2-ARGV vhost_queues-invalid ... OK 181) QEMU XML-2-ARGV net-vhostuser ... OK 182) QEMU XML-2-ARGV net-user ... OK 183) QEMU XML-2-ARGV net-virtio ... OK 184) QEMU XML-2-ARGV net-virtio-device ... OK 185) QEMU XML-2-ARGV net-virtio-disable-offloads ... OK 186) QEMU XML-2-ARGV net-virtio-netdev ... OK 187) QEMU XML-2-ARGV net-virtio-s390 ... OK 188) QEMU XML-2-ARGV net-virtio-ccw ... OK 189) QEMU XML-2-ARGV net-eth ... OK 190) QEMU XML-2-ARGV net-eth-ifname ... OK 191) QEMU XML-2-ARGV net-eth-names ... OK 192) QEMU XML-2-ARGV net-client ... OK 193) QEMU XML-2-ARGV net-server ... OK 194) QEMU XML-2-ARGV net-mcast ... OK 195) QEMU XML-2-ARGV net-hostdev ... OK 196) QEMU XML-2-ARGV net-hostdev-multidomain ... OK 197) QEMU XML-2-ARGV net-hostdev-multidomain ... Got expected error: unsupported configuration: non-zero domain='2424' in host device PCI address not supported in this QEMU binary OK 198) QEMU XML-2-ARGV net-hostdev-vfio ... OK 199) QEMU XML-2-ARGV net-hostdev-vfio-multidomain ... OK 200) QEMU XML-2-ARGV net-hostdev-vfio-multidomain ... Got expected error: unsupported configuration: non-zero domain='0021' in host device PCI address not supported in this QEMU binary OK 201) QEMU XML-2-ARGV serial-vc ... OK 202) QEMU XML-2-ARGV serial-pty ... OK 203) QEMU XML-2-ARGV serial-dev ... OK 204) QEMU XML-2-ARGV serial-file ... OK 205) QEMU XML-2-ARGV serial-unix ... OK 206) QEMU XML-2-ARGV serial-tcp ... OK 207) QEMU XML-2-ARGV serial-udp ... OK 208) QEMU XML-2-ARGV serial-tcp-telnet ... OK 209) QEMU XML-2-ARGV serial-many ... OK 210) QEMU XML-2-ARGV serial-spiceport ... OK 211) QEMU XML-2-ARGV serial-spiceport-nospice ... OK 212) QEMU XML-2-ARGV parallel-tcp ... OK 213) QEMU XML-2-ARGV console-compat ... OK 214) QEMU XML-2-ARGV console-compat-auto ... OK 215) QEMU XML-2-ARGV serial-vc-chardev ... OK 216) QEMU XML-2-ARGV serial-pty-chardev ... OK 217) QEMU XML-2-ARGV serial-dev-chardev ... OK 218) QEMU XML-2-ARGV serial-file-chardev ... OK 219) QEMU XML-2-ARGV serial-unix-chardev ... OK 220) QEMU XML-2-ARGV serial-tcp-chardev ... OK 221) QEMU XML-2-ARGV serial-udp-chardev ... OK 222) QEMU XML-2-ARGV serial-tcp-telnet-chardev ... OK 223) QEMU XML-2-ARGV serial-many-chardev ... OK 224) QEMU XML-2-ARGV parallel-tcp-chardev ... OK 225) QEMU XML-2-ARGV parallel-parport-chardev ... OK 226) QEMU XML-2-ARGV console-compat-chardev ... OK 227) QEMU XML-2-ARGV channel-guestfwd ... OK 228) QEMU XML-2-ARGV channel-virtio ... OK 229) QEMU XML-2-ARGV channel-virtio-state ... OK 230) QEMU XML-2-ARGV channel-virtio-auto ... OK 231) QEMU XML-2-ARGV console-virtio ... OK 232) QEMU XML-2-ARGV console-virtio-many ... OK 233) QEMU XML-2-ARGV console-virtio-s390 ... OK 234) QEMU XML-2-ARGV console-virtio-ccw ... OK 235) QEMU XML-2-ARGV console-sclp ... OK 236) QEMU XML-2-ARGV channel-spicevmc ... OK 237) QEMU XML-2-ARGV channel-spicevmc-old ... OK 238) QEMU XML-2-ARGV smartcard-host ... OK 239) QEMU XML-2-ARGV smartcard-host-certificates ... OK 240) QEMU XML-2-ARGV smartcard-passthrough-tcp ... OK 241) QEMU XML-2-ARGV smartcard-passthrough-spicevmc ... OK 242) QEMU XML-2-ARGV smartcard-controller ... OK 243) QEMU XML-2-ARGV usb-controller ... OK 244) QEMU XML-2-ARGV usb-piix3-controller ... OK 245) QEMU XML-2-ARGV usb-ich9-ehci-addr ... OK 246) QEMU XML-2-ARGV input-usbmouse-addr ... OK 247) QEMU XML-2-ARGV usb-ich9-companion ... OK 248) QEMU XML-2-ARGV usb-ich9-no-companion ... OK 249) QEMU XML-2-ARGV usb-hub ... OK 250) QEMU XML-2-ARGV usb-ports ... OK 251) QEMU XML-2-ARGV usb-redir ... OK 252) QEMU XML-2-ARGV usb-redir-boot ... OK 253) QEMU XML-2-ARGV usb-redir-filter ... OK 254) QEMU XML-2-ARGV usb1-usb2 ... OK 255) QEMU XML-2-ARGV usb-none ... OK 256) QEMU XML-2-ARGV usb-none-other ... OK 257) QEMU XML-2-ARGV usb-none-hub ... OK 258) QEMU XML-2-ARGV usb-none-usbtablet ... OK 259) QEMU XML-2-ARGV smbios ... OK 260) QEMU XML-2-ARGV smbios-date ... OK 261) QEMU XML-2-ARGV smbios-uuid-match ... OK 262) QEMU XML-2-ARGV watchdog ... OK 263) QEMU XML-2-ARGV watchdog-device ... OK 264) QEMU XML-2-ARGV watchdog-dump ... OK 265) QEMU XML-2-ARGV balloon-device ... OK 266) QEMU XML-2-ARGV balloon-device-auto ... OK 267) QEMU XML-2-ARGV balloon-device-period ... OK 268) QEMU XML-2-ARGV sound ... OK 269) QEMU XML-2-ARGV sound-device ... OK 270) QEMU XML-2-ARGV fs9p ... OK 271) QEMU XML-2-ARGV hostdev-usb-address ... OK 272) QEMU XML-2-ARGV hostdev-usb-address-device ... OK 273) QEMU XML-2-ARGV hostdev-usb-address-device-boot ... OK 274) QEMU XML-2-ARGV hostdev-pci-address ... OK 275) QEMU XML-2-ARGV hostdev-pci-address-device ... OK 276) QEMU XML-2-ARGV hostdev-vfio ... OK 277) QEMU XML-2-ARGV hostdev-vfio-multidomain ... OK 278) QEMU XML-2-ARGV hostdev-vfio-multidomain ... Got expected error: unsupported configuration: non-zero domain='55aa' in host device PCI address not supported in this QEMU binary OK 279) QEMU XML-2-ARGV pci-rom ... OK 280) QEMU XML-2-ARGV restore-v1 ... OK 281) QEMU XML-2-ARGV restore-v2 ... OK 282) QEMU XML-2-ARGV restore-v2 ... OK 283) QEMU XML-2-ARGV restore-v2-fd ... OK 284) QEMU XML-2-ARGV restore-v2-fd ... OK 285) QEMU XML-2-ARGV migrate ... OK 286) QEMU XML-2-ARGV qemu-ns ... OK 287) QEMU XML-2-ARGV smp ... OK 288) QEMU XML-2-ARGV iothreads ... OK 289) QEMU XML-2-ARGV iothreads-disk ... OK 290) QEMU XML-2-ARGV iothreads-disk-virtio-ccw ... OK 291) QEMU XML-2-ARGV cpu-topology1 ... OK 292) QEMU XML-2-ARGV cpu-topology2 ... OK 293) QEMU XML-2-ARGV cpu-topology3 ... OK 294) QEMU XML-2-ARGV cpu-minimum1 ... OK 295) QEMU XML-2-ARGV cpu-minimum2 ... OK 296) QEMU XML-2-ARGV cpu-exact1 ... OK 297) QEMU XML-2-ARGV cpu-exact2 ... OK 298) QEMU XML-2-ARGV cpu-exact2-nofallback ... OK 299) QEMU XML-2-ARGV cpu-fallback ... OK 300) QEMU XML-2-ARGV cpu-nofallback ... Got expected error: unsupported configuration: CPU model Westmere is not supported by hypervisor OK 301) QEMU XML-2-ARGV cpu-strict1 ... OK 302) QEMU XML-2-ARGV cpu-numa1 ... OK 303) QEMU XML-2-ARGV cpu-numa2 ... OK 304) QEMU XML-2-ARGV cpu-numa-no-memory-element ... OK 305) QEMU XML-2-ARGV cpu-numa3 ... OK 306) QEMU XML-2-ARGV cpu-numa-disjoint ... Got expected error: unsupported configuration: disjoint NUMA cpu ranges are not supported with this QEMU OK 307) QEMU XML-2-ARGV cpu-numa-disjoint ... OK 308) QEMU XML-2-ARGV cpu-numa-memshared ... Got expected error: unsupported configuration: Shared memory mapping is supported only with hugepages OK 309) QEMU XML-2-ARGV cpu-numa-memshared ... Got expected error: unsupported configuration: Shared memory mapping is not supported with this QEMU OK 310) QEMU XML-2-ARGV cpu-host-model ... OK 311) QEMU XML-2-ARGV cpu-host-model-fallback ... OK 312) QEMU XML-2-ARGV cpu-host-model-nofallback ... Got expected error: unsupported configuration: CPU model core2duo is not supported by hypervisor OK 313) QEMU XML-2-ARGV cpu-host-passthrough ... OK 314) QEMU XML-2-ARGV cpu-host-passthrough ... Got expected error: unsupported configuration: the QEMU binary does not support kvm OK 315) QEMU XML-2-ARGV cpu-qemu-host-passthrough ... Got expected error: unsupported configuration: CPU mode 'host-passthrough' is only supported with kvm OK 316) QEMU XML-2-ARGV cpu-Haswell ... OK 317) QEMU XML-2-ARGV cpu-Haswell2 ... OK 318) QEMU XML-2-ARGV cpu-Haswell3 ... OK 319) QEMU XML-2-ARGV cpu-Haswell-noTSX ... OK 320) QEMU XML-2-ARGV memtune ... OK 321) QEMU XML-2-ARGV memtune-unlimited ... OK 322) QEMU XML-2-ARGV blkiotune ... OK 323) QEMU XML-2-ARGV blkiotune-device ... OK 324) QEMU XML-2-ARGV cputune ... OK 325) QEMU XML-2-ARGV cputune-zero-shares ... OK 326) QEMU XML-2-ARGV cputune-iothreadsched-toomuch ... OK 327) QEMU XML-2-ARGV cputune-vcpusched-overlap ... OK 328) QEMU XML-2-ARGV cputune-numatune ... OK 329) QEMU XML-2-ARGV numatune-memory ... OK 330) QEMU XML-2-ARGV numatune-memory-invalid-nodeset ... OK 331) QEMU XML-2-ARGV numatune-memnode ... libvirt: error : unsupported configuration: NUMA node 1 is unavailable FAILED 332) QEMU XML-2-ARGV numatune-memnode ... Got expected error: unsupported configuration: Per-node memory binding is not supported with this QEMU OK 333) QEMU XML-2-ARGV numatune-memnode-no-memory ... libvirt: error : unsupported configuration: NUMA node 3 is unavailable FAILED 334) QEMU XML-2-ARGV numatune-memnode-no-memory ... Got expected error: unsupported configuration: Per-node memory binding is not supported with this QEMU OK 335) QEMU XML-2-ARGV numatune-auto-nodeset-invalid ... OK 336) QEMU XML-2-ARGV numatune-auto-prefer ... libvirt: error : unsupported configuration: NUMA node 1 is unavailable FAILED 337) QEMU XML-2-ARGV numatune-static-nodeset-exceed-hostnode ... Got expected error: unsupported configuration: NUMA node 1 is unavailable OK 338) QEMU XML-2-ARGV numatune-memnode-nocpu ... OK 339) QEMU XML-2-ARGV numatune-memnodes-problematic ... OK 340) QEMU XML-2-ARGV numad ... OK 341) QEMU XML-2-ARGV numad-auto-vcpu-static-numatune ... OK 342) QEMU XML-2-ARGV numad-auto-vcpu-static-numatune-no-nodeset ... OK 343) QEMU XML-2-ARGV numad-auto-memory-vcpu-cpuset ... OK 344) QEMU XML-2-ARGV numad-auto-memory-vcpu-no-cpuset-and-placement ... OK 345) QEMU XML-2-ARGV numad-static-memory-auto-vcpu ... OK 346) QEMU XML-2-ARGV blkdeviotune ... OK 347) QEMU XML-2-ARGV blkdeviotune-max ... OK 348) QEMU XML-2-ARGV multifunction-pci-device ... OK 349) QEMU XML-2-ARGV monitor-json ... OK 350) QEMU XML-2-ARGV no-shutdown ... OK 351) QEMU XML-2-ARGV seclabel-dynamic ... OK 352) QEMU XML-2-ARGV seclabel-dynamic-baselabel ... OK 353) QEMU XML-2-ARGV seclabel-dynamic-override ... OK 354) QEMU XML-2-ARGV seclabel-dynamic-labelskip ... OK 355) QEMU XML-2-ARGV seclabel-dynamic-relabel ... OK 356) QEMU XML-2-ARGV seclabel-static ... OK 357) QEMU XML-2-ARGV seclabel-static-relabel ... OK 358) QEMU XML-2-ARGV seclabel-static-labelskip ... OK 359) QEMU XML-2-ARGV seclabel-none ... OK 360) QEMU XML-2-ARGV seclabel-dac-none ... OK 361) QEMU XML-2-ARGV seclabel-multiple ... OK 362) QEMU XML-2-ARGV seclabel-device-duplicates ... OK 363) QEMU XML-2-ARGV pseries-basic ... OK 364) QEMU XML-2-ARGV pseries-vio ... OK 365) QEMU XML-2-ARGV pseries-usb-default ... OK 366) QEMU XML-2-ARGV pseries-usb-multi ... OK 367) QEMU XML-2-ARGV pseries-vio-user-assigned ... OK 368) QEMU XML-2-ARGV pseries-vio-address-clash ... OK 369) QEMU XML-2-ARGV pseries-nvram ... OK 370) QEMU XML-2-ARGV pseries-usb-kbd ... OK 371) QEMU XML-2-ARGV pseries-cpu-exact ... OK 372) QEMU XML-2-ARGV pseries-cpu-compat ... OK 373) QEMU XML-2-ARGV pseries-cpu-le ... OK 374) QEMU XML-2-ARGV disk-ide-drive-split ... OK 375) QEMU XML-2-ARGV disk-ide-wwn ... OK 376) QEMU XML-2-ARGV disk-geometry ... OK 377) QEMU XML-2-ARGV disk-blockio ... OK 378) QEMU XML-2-ARGV video-device-pciaddr-default ... OK 379) QEMU XML-2-ARGV video-vga-nodevice ... OK 380) QEMU XML-2-ARGV video-vga-device ... OK 381) QEMU XML-2-ARGV video-vga-device-vgamem ... OK 382) QEMU XML-2-ARGV video-qxl-nodevice ... OK 383) QEMU XML-2-ARGV video-qxl-device ... OK 384) QEMU XML-2-ARGV video-qxl-device-vgamem ... OK 385) QEMU XML-2-ARGV video-qxl-sec-nodevice ... Got expected error: unsupported configuration: only one video card is currently supported OK 386) QEMU XML-2-ARGV video-qxl-sec-device ... OK 387) QEMU XML-2-ARGV video-qxl-sec-device-vgamem ... OK 388) QEMU XML-2-ARGV video-invalid ... OK 389) QEMU XML-2-ARGV virtio-rng-default ... OK 390) QEMU XML-2-ARGV virtio-rng-random ... OK 391) QEMU XML-2-ARGV virtio-rng-egd ... OK 392) QEMU XML-2-ARGV virtio-rng-multiple ... OK 393) QEMU XML-2-ARGV virtio-rng-egd-crash ... OK 394) QEMU XML-2-ARGV virtio-rng-ccw ... OK 395) QEMU XML-2-ARGV s390-usb-none ... OK 396) QEMU XML-2-ARGV s390-piix-controllers ... OK 397) QEMU XML-2-ARGV ppc-dtb ... OK 398) QEMU XML-2-ARGV ppce500-serial ... OK 399) QEMU XML-2-ARGV tpm-passthrough ... OK 400) QEMU XML-2-ARGV tpm-no-backend-invalid ... OK 401) QEMU XML-2-ARGV pci-autoadd-addr ... OK 402) QEMU XML-2-ARGV pci-autoadd-idx ... OK 403) QEMU XML-2-ARGV pci-many ... OK 404) QEMU XML-2-ARGV pci-bridge-many-disks ... OK 405) QEMU XML-2-ARGV pcie-root ... OK 406) QEMU XML-2-ARGV q35 ... OK 407) QEMU XML-2-ARGV hostdev-scsi-lsi ... OK 408) QEMU XML-2-ARGV hostdev-scsi-virtio-scsi ... OK 409) QEMU XML-2-ARGV hostdev-scsi-readonly ... OK 410) QEMU XML-2-ARGV hostdev-scsi-virtio-scsi ... OK 411) QEMU XML-2-ARGV hostdev-scsi-lsi-iscsi ... OK 412) QEMU XML-2-ARGV hostdev-scsi-lsi-iscsi-auth ... OK 413) QEMU XML-2-ARGV hostdev-scsi-virtio-iscsi ... OK 414) QEMU XML-2-ARGV hostdev-scsi-virtio-iscsi-auth ... OK 415) QEMU XML-2-ARGV mlock-on ... OK 416) QEMU XML-2-ARGV mlock-on ... Got expected error: unsupported configuration: memory locking not supported by QEMU binary OK 417) QEMU XML-2-ARGV mlock-off ... OK 418) QEMU XML-2-ARGV mlock-unsupported ... OK 419) QEMU XML-2-ARGV pci-bridge-negative-index-invalid ... OK 420) QEMU XML-2-ARGV pci-bridge-duplicate-index ... OK 421) QEMU XML-2-ARGV pci-root-nonzero-index ... OK 422) QEMU XML-2-ARGV pci-root-address ... OK 423) QEMU XML-2-ARGV hotplug-base ... OK 424) QEMU XML-2-ARGV pcihole64 ... OK 425) QEMU XML-2-ARGV pcihole64-none ... Got expected error: unsupported configuration: 64-bit PCI hole size setting is not supported with this QEMU binary OK 426) QEMU XML-2-ARGV pcihole64-q35 ... OK 427) QEMU XML-2-ARGV arm-vexpressa9-nodevs ... OK 428) QEMU XML-2-ARGV arm-vexpressa9-basic ... OK 429) QEMU XML-2-ARGV arm-vexpressa9-virtio ... OK 430) QEMU XML-2-ARGV arm-virt-virtio ... OK 431) QEMU XML-2-ARGV aarch64-virt-virtio ... OK 432) QEMU XML-2-ARGV aarch64-aavmf-virtio-mmio ... OK 433) QEMU XML-2-ARGV aarch64-virt-default-nic ... OK 434) QEMU XML-2-ARGV kvm-pit-device ... OK 435) QEMU XML-2-ARGV kvm-pit-delay ... OK 436) QEMU XML-2-ARGV kvm-pit-device ... OK 437) QEMU XML-2-ARGV panic ... OK 438) QEMU XML-2-ARGV panic-no-address ... OK 439) QEMU XML-2-ARGV fips-enabled ... OK 440) QEMU XML-2-ARGV shmem ... OK 441) QEMU XML-2-ARGV shmem ... Got expected error: unsupported configuration: ivshmem device is not supported with this QEMU binary OK 442) QEMU XML-2-ARGV shmem-invalid-size ... Got expected error: XML error: shmem size must be a power of two OK 443) QEMU XML-2-ARGV shmem-small-size ... Got expected error: XML error: shmem size must be at least 1 MiB (1024 KiB) OK 444) QEMU XML-2-ARGV shmem-msi-only ... OK 445) QEMU XML-2-ARGV cpu-host-passthrough-features ... OK 446) QEMU XML-2-ARGV memory-hotplug-nonuma ... Got expected error: unsupported configuration: At least one numa node has to be configured when enabling memory hotplug OK 447) QEMU XML-2-ARGV memory-hotplug ... Got expected error: unsupported configuration: memory hotplug isn't supported by this QEMU binary OK 448) QEMU XML-2-ARGV memory-hotplug ... OK 449) QEMU XML-2-ARGV memory-hotplug-dimm ... libvirt: error : unsupported configuration: NUMA node 1 is unavailable FAILED 450) QEMU XML-2-ARGV memory-hotplug-dimm-addr ... libvirt: error : unsupported configuration: NUMA node 1 is unavailable FAILED FAIL qemuxml2argvtest (exit status: 1) Thanks for your help!!

3 2

[libvirt-users] Qemu-guest agent
by Umer Khan 22 May '15

22 May '15

Hi all, I am new to libvirt, I am trying to execute some commands inside guest domains from my host machine using libvirt-Python API. So far I have been able to open up a stream but I am not sure how to send commands on the stream (through virDomainOpenConsole). After hours of searching through different forums I found out that there is a utlity called qemu-guest agent which can solve my problem. But I am not sure how to enable this agent on host and domain, and how this will be used to communicate to guest domains. Any help in this matter will be really appreciated. Thanks

2 1

[libvirt-users] Blockcommit error
by Mathew Moon 21 May '15

21 May '15

HI, I am receiving the following error when I try to run blockcommit: ============================================================== root@farnsworth:/var/lib/libvirt/images# virsh blockcommit pg94-test vda --top /var/lib/libvirt/images/pg94-test.snap4 --active --pivot --verbose error: unsupported flags (0x4) in function qemuDomainBlockCommit ============================================================== I get the same error if I try only --top and --verbose flags. I am running Ubuntu Server 10.04 LTS. The snapshots I am committing were created using the following command: ============================================================== virsh snapshot-create-as --domain $DOMAIN $SNAP $DESC --disk-only --diskspec vda,snapshot=external,file=/var/lib/libvirt/images/${FILENAME} --atomic || error "Could not create snapshot." 2 ============================================================== Below is my Qemu and Libvirt version info. I don't think it is actually a problem with the command. It looks like if I provide invalid flags to the command itself I get a different error. I get this error if the command is syntactically correct and tries to actually execute the blockcommit. Any ideas what could be going on here? After reading a message between Kashyap and someone else on the list that was posted a while back it looks like it may have something to do with the snapshots not having defined their file format, but I don't know how to tell if this is it for sure, or how to go back and add that information. =============================================================== root@farnsworth:/var/lib/libvirt/images# qemu-img --version qemu-img version 2.2.1, Copyright (c) 2004-2008 Fabrice Bellard root@farnsworth:/var/lib/libvirt/images# kvm --version QEMU emulator version 2.2.1, Copyright (c) 2003-2008 Fabrice Bellard root@farnsworth:/var/lib/libvirt/images# virsh -v 1.2.6 root@farnsworth:/var/lib/libvirt/images# qemu-system-x86_64 --version QEMU emulator version 2.2.1, Copyright (c) 2003-2008 Fabrice Bellard root@farnsworth:/var/lib/libvirt/images# ===============================================================

2 1

[libvirt-users] Drivers supporting space_hard_limit
by Christian Haase 21 May '15

21 May '15

Hi, In the XML documentation I found the element space_hard_limit for filesystems [1]. Is this feature implemented for any constellation? I try to use it with lxc 1.0.6-6 and libvirt 1.2.9-9 (all from debian jessie): <domain type='lxc' id='1234'> .... <devices> <emulator>/usr/lib/libvirt/libvirt_lxc</emulator> .... <filesystem type='mount' accessmode='passthrough'> <source dir='/tmp/libvirt/mnt'/> <target dir='/mnt'/> <space_hard_limit unit='bytes'>5242880</space_hard_limit> </filesystem> .... </devices> </domain> For testing I use dd if=/dev/zero of=/mnt/foo and ^C after a few gigabytes. Is this a supported configuration? If yes, I can provide some more info to reproduce, if not, I think this should be noted in the docs ("Only used by ??? driver"). Thanks, Christian [1] http://libvirt.org/formatdomain.html#elementsFilesystems -- ifu Hamburg - material flows and software "We enable sustainable production." ifu Hamburg GmbH Max-Brauer-Allee 50 - 22765 Hamburg - Germany fon: +49 40 480009-0 - fax: +49 40 480009-22 - email: info(a)ifu.com Managing Director: Jan Hedemann - Commercial Register: Hamburg, HRB 52629 www.ifu.com - www.umberto.de - www.e-sankey.com

1 1

[libvirt-users] qemu/kvm: "spurious APIC interrupt"
by Stefan G. Weichinger 20 May '15

20 May '15

I know, that this might be more QEMU-specific than a libvirt-topic ... but I hope that someone in here can point me to a solution as well as there are many qemu-users in here as well I assume. - I run an ancient linux-VM with a 2.2.x kernel (I have to keep it up as the software in there is compiled against that ...) We get a lot of dmesg-lines like: spurious APIC interrupt on CPU#0, should never happen I think that this slows the VM down? I tried to disable APIC in the VMs config and in the VM (kernel-option) etc but without success so far. I also tried various clock-settings ... might setting another <type> in the vm.xml help? I have: <os> <type arch='x86_64' machine='pc-1.1'>hvm</type> the original installation was on a Pentium 2 or 3, if I remember correctly. fyi: the host is a Gentoo Linux machine, libvirt 1.2.15, qemu 2.2.1-r2 (=current). Any pointers? google didn't help much here. Thanks, Stefan

1 0

[libvirt-users] xl extra parameters equivalent for libvirt
by Emma Anderson 20 May '15

20 May '15

hi, I use xl toolstack to manage vms on a Xen machine, and also pass some custom parameters when creating a vm, for example: xl create vm.cfg ' param="xyz" ' I am moving to libvirt for vm management. How I can pass those extra parameters using libvirt? Thanks.

4 4

[libvirt-users] Pivot without copy
by Mathew Moon 19 May '15

19 May '15

Hi, Is it possible to "pivot" to a new image without doing blockcopy or blockpull? I know how to use snapshots and blockpull to create a new image and pivot to using it live, but what I would like to do is to have a VM switch from using imageA.qcow2 to image2.qcow2 while running. I don't see why this wouldn't be possible since some of the existing libvirt tools can do this when they are done. I would love to see an example from a bash terminal as well as how it would be done using the python API. Regards, Mathew

2 7

[libvirt-users] Hardware requirements for SPICEd desktops
by Lucio Crusca 19 May '15

19 May '15

Hello, I posted the following to the kvm list yesterday, but now I suspect this is a more appropriate place to ask... I'm considering to build a new server and to use SPICE protocol to deploy all the Windows guests to the local network. It's my understanding that: 1. I should create the guests on the server 2. I should use remote-viewer on a minimal desktop linux on the clients over SPICE protocol 3. I should enable QXL on the server 4. I can get clients USB ports and soundcards working in the guests Now, assuming I've understood the above correctly, I haven't understood what are the hardware requirements server and client side: 1. Let's say I assign 4GB of RAM to each guest and that the network has 20 running guests at any given time, should the server have at least 80GB (20 by 4) of RAM or can I "oversell" a bit and bet on the fact that only few guests will actually use 4GB? 2. What's a reasonable amount of RAM to have installed client-side, for 4GB-RAM guests? 3. Should the clients have a CPU that supports VT-x? 4. Is it possible to have QXL supported on the clients regardless of the physical video adapter installed? 5. And what about the soundcard support? Will any linux-supported soundcard do on the clients?

1 1

[libvirt-users] Live Migration failure: An error occurred, but the cause is unknown
by RockCui＠zhaoxin.com 14 May '15

14 May '15

Hi everyone, I’m testing the new Openstack Kilo on Ubuntu-15.04 and hypervisor is KVM. I can creat instance successfully , but live migration is always failed. Error report like this (from nova-compute.log on a compute node): 2015-05-12 18:11:12.753 3641 INFO nova.virt.libvirt.driver [-] [instance: cee4965c-b298-4b5b-8669-bee9ac72c720] Migration running for 0 secs, memory 0% remaining; (bytes processed=0, remaining=0, total=0) 2015-05-12 18:11:16.342 3641 ERROR nova.virt.libvirt.driver [-] [instance: cee4965c-b298-4b5b-8669-bee9ac72c720] Live Migration failure: An error occurred, but the cause is unknown 2015-05-12 18:11:16.777 3641 ERROR nova.virt.libvirt.driver [-] [instance: cee4965c-b298-4b5b-8669-bee9ac72c720] Migration operation has aborted If someone has a clue what may cause this, pls help. Thanks. Rock Cui 本邮件仅针对指定的收件人发送并可能含有保密或专有内容。任何非指定收件人所为之查阅、转发或使用本信息是不被允许的。如果您误收到本邮件，请立即告知发件人并删除本邮件及所有附件。谢谢！ The information transmitted in this e-mail is intended only for the addressee and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of this information by persons or entities other than the intended recipient is prohibited. If you received this e-mail in error, please notify the sender immediately, and delete this e-mail and any attachments. Thank you.

2 1

[libvirt-users] libvirtError: this function is not supported by the connection driver: virDomainSnapshotNum
by big strong 12 May '15

12 May '15

I tried to create && open a snapshot of xen and the error appears. Is there anyway to support xen snapshotting with libxl/libvirt? This blog http://searchservervirtualization.techtarget.com/tip/Creating-snapshots-in-… offers two way to backup xen vm with linux commands, can we integrate it into libvirt?

2 1

[libvirt-users] Qemu crash detection clarification
by Vasileios Anagnostopoulos 11 May '15

11 May '15

Hi, I am interested in the API of libvirt to detect the evnt that a domain has crashed. I am using QEMU hypervisor. I saw through a commit https://bugzilla.redhat.com/show_bug.cgi?id=636164 that a panic device has been added. However in the TODO list http://wiki.libvirt.org/page/Todo#Hypervisor_driver I found out that crash detection is not supported. What is the status of QEMU crash detection through the libvirt API? thanks -- Dr. Vasileios Anagnostopoulos (MSc,PhD) Researcher/Developer ICCS/NTUA 9 Heroon Polytechneiou Str., Zografou 15773 Athens,Greece T (+30) 2107723404 M (+30) 6936935388 E vanag(a)mail.ntua.gr<mailto:vanag@mail.ntua.gr> www.ntua.gr< http://www.ntua.gr/>

1 0

[libvirt-users] Editing http://libvirt.org/sources/virshcmdref/html-single/#sect-attach-device
by Mauricio Tavares 10 May '15

10 May '15

I just noticed the entries on attach-disk and attach-devices are a bit on the empty size. As I am just attaching a usb device to one of my vm clients, I was wondering if I could offer examples to those entries.

3 2

[libvirt-users] vnetX interface name persistence
by Lucas Brasilino 08 May '15

08 May '15

Hi! I'm aware that (host side) vnetX are created when VM boots. But I'm trying to figure out a way ti create a persistence in vnetX names. What I mean is, say, I want to associate VMs vm0 to vnet0, vm1 to vnet1, vm2 to vnet2 and so forth, no matter which order the VMs are booted. I looked around network XML format, but did't find something... Since I'm using Open vSwitch as bridge, and it is controlled by my OpenFlow application, I can query for OF ports numbers based on port names (interfaces names). OVSDB can be used for such query, but the controller I'm using, Pox, has a limited support to it (stills in development). I'm using libvirt 1.0.5 and Qemu/KVM 1.4.2 on a Fedora 19 host. Thanks a lot in advance. -- Att Lucas Brasilino MSc Student @ Federal University of Pernambuco (UFPE) / Brazil twitter: @lucas_brasilino

2 1

[libvirt-users] Failed dependencies with perl-Sys-Virt
by xuanmao_001 08 May '15

08 May '15

Hi, erveryone: I compiled libvirt-1.1.2.tar.gz from source. my compile step: ./configure --prefix=/usr --libdir=/usr/lib64 --without-xen --without-xen-inotify \ --without-uml --without-openvz --without-vmware --without-vbox --without-lxc \ --without-esx --without-parallels --without-phyp -- without-test --with-yajl \ --without-selinux --without-secdriver-selinux make && make install #ls -l /usr/lib64/libvirt* -rw-r--r-- 1 root root 10144610 2月 6 15:34 /usr/lib64/libvirt.a -rwxr-xr-x 1 root root 1018 5月 8 19:51 /usr/lib64/libvirt.la -rwxr-xr-x 1 root root 1064 5月 8 19:51 /usr/lib64/libvirt-lxc.la lrwxrwxrwx 1 root root 23 5月 8 19:51 /usr/lib64/libvirt-lxc.so -> libvirt-lxc.so.0.1001.2 lrwxrwxrwx 1 root root 23 5月 8 19:51 /usr/lib64/libvirt-lxc.so.0 -> libvirt-lxc.so.0.1001.2 -rwxr-xr-x 1 root root 75419 5月 8 19:51 /usr/lib64/libvirt-lxc.so.0.1001.2 -rw-r--r-- 1 root root 78856 2月 6 15:34 /usr/lib64/libvirt-qemu.a -rwxr-xr-x 1 root root 1070 5月 8 19:51 /usr/lib64/libvirt-qemu.la lrwxrwxrwx 1 root root 24 5月 8 20:31 /usr/lib64/libvirt-qemu.so -> libvirt-qemu.so.0.1001.2 lrwxrwxrwx 1 root root 24 5月 8 20:31 /usr/lib64/libvirt-qemu.so.0 -> libvirt-qemu.so.0.1001.2 -rwxr-xr-x 1 root root 74097 5月 8 19:51 /usr/lib64/libvirt-qemu.so.0.1001.2 lrwxrwxrwx 1 root root 19 5月 8 20:31 /usr/lib64/libvirt.so -> libvirt.so.0.1001.2 lrwxrwxrwx 1 root root 19 5月 8 20:31 /usr/lib64/libvirt.so.0 -> libvirt.so.0.1001.2 -rwxr-xr-x 1 root root 8100016 5月 8 19:51 /usr/lib64/libvirt.so.0.1001.2 everyone seems ok, but when I install perl-Sys-Virt-0.10.2-5.el6.x86_64.rpm with rpm -ivh, it occured error message: error: Failed dependencies: libvirt.so.0()(64bit) is needed by perl-Sys-Virt-0.10.2-5.el6.x86_64 libvirt.so.0(LIBVIRT_0.0.3)(64bit) is needed by perl-Sys-Virt-0.10.2-5.el6.x86_64 libvirt.so.0(LIBVIRT_0.0.5)(64bit) is needed by perl-Sys-Virt-0.10.2-5.el6.x86_64 libvirt.so.0(LIBVIRT_0.1.0)(64bit) is needed by perl-Sys-Virt-0.10.2-5.el6.x86_64 libvirt.so.0(LIBVIRT_0.1.1)(64bit) is needed by perl-Sys-Virt-0.10.2-5.el6.x86_64 libvirt.so.0(LIBVIRT_0.1.4)(64bit) is needed by perl-Sys-Virt-0.10.2-5.el6.x86_64 libvirt.so.0(LIBVIRT_0.1.5)(64bit) is needed by perl-Sys-Virt-0.10.2-5.el6.x86_64 libvirt.so.0(LIBVIRT_0.1.9)(64bit) is needed by perl-Sys-Virt-0.10.2-5.el6.x86_64 libvirt.so.0(LIBVIRT_0.10.0)(64bit) is needed by perl-Sys-Virt-0.10.2-5.el6.x86_64 libvirt.so.0(LIBVIRT_0.10.2)(64bit) is needed by perl-Sys-Virt-0.10.2-5.el6.x86_64 ... I checked with the follow command. [root@CH08134252 ~]# nm -A -D /usr/lib64/libvirt.so.0 | grep LIBVIRT /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.0.3 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.0.5 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.1.0 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.1.1 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.1.4 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.1.5 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.1.9 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.10.0 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.10.2 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.2.0 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.2.1 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.2.3 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.3.0 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.3.2 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.3.3 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.4.0 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.4.1 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.4.2 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.4.5 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.5.0 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.6.0 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.6.1 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.6.3 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.6.4 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.7.0 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.7.1 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.7.2 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.7.3 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.7.5 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.7.7 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.8.0 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.8.1 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.8.2 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.8.5 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.8.6 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.8.8 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.9.0 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.9.10 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.9.11 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.9.13 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.9.2 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.9.3 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.9.4 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.9.5 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.9.7 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.9.8 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_0.9.9 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_1.0.0 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_1.0.1 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_1.0.2 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_1.0.3 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_1.0.5 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_1.0.6 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_1.1.0 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_1.1.1 /usr/lib64/libvirt.so.0:0000000000000000 A LIBVIRT_PRIVATE_1.1.2 I have no idea, please give me some help. thanks. xuanmao_001

2 2

[libvirt-users] Live Migration failure: this function is not supported by the connection driver: virDomainMigrateToURI2
by RockCui＠zhaoxin.com 07 May '15

07 May '15

Hi everyone, I’m testing the new openstack kilo on ubuntu15.04 and hypervisor is xen4.5. I can creat instance successfully , but live migration is always failed. Error report like this: 2015-05-07 10:47:22.135 1331 ERROR nova.virt.libvirt.driver [-] [instance: b1081b86-fdce-4fcc-82c4-51896de4418c] Live Migration failure: this function is not supported by the connection driver: virDomainMigrateToURI2 2015-05-07 10:47:22.246 1331 WARNING nova.virt.libvirt.driver [-] [instance: b1081b86-fdce-4fcc-82c4-51896de4418c] Error monitoring migration: this function is not supported by the connection driver: virDomainGetJobInfo 2015-05-07 10:47:22.246 1331 TRACE nova.virt.libvirt.driver [instance: b1081b86-fdce-4fcc-82c4-51896de4418c] Traceback (most recent call last): 2015-05-07 10:47:22.246 1331 TRACE nova.virt.libvirt.driver [instance: b1081b86-fdce-4fcc-82c4-51896de4418c] File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 5689, in _live_migration 2015-05-07 10:47:22.246 1331 TRACE nova.virt.libvirt.driver [instance: b1081b86-fdce-4fcc-82c4-51896de4418c] dom, finish_event) 2015-05-07 10:47:22.246 1331 TRACE nova.virt.libvirt.driver [instance: b1081b86-fdce-4fcc-82c4-51896de4418c] File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 5521, in _live_migration_monitor 2015-05-07 10:47:22.246 1331 TRACE nova.virt.libvirt.driver [instance: b1081b86-fdce-4fcc-82c4-51896de4418c] info = host.DomainJobInfo.for_domain(dom) 2015-05-07 10:47:22.246 1331 TRACE nova.virt.libvirt.driver [instance: b1081b86-fdce-4fcc-82c4-51896de4418c] File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/host.py", line 164, in for_domain 2015-05-07 10:47:22.246 1331 TRACE nova.virt.libvirt.driver [instance: b1081b86-fdce-4fcc-82c4-51896de4418c] return cls._get_job_stats_compat(dom) 2015-05-07 10:47:22.246 1331 TRACE nova.virt.libvirt.driver [instance: b1081b86-fdce-4fcc-82c4-51896de4418c] File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/host.py", line 113, in _get_job_stats_compat 2015-05-07 10:47:22.246 1331 TRACE nova.virt.libvirt.driver [instance: b1081b86-fdce-4fcc-82c4-51896de4418c] info = dom.jobInfo() 2015-05-07 10:47:22.246 1331 TRACE nova.virt.libvirt.driver [instance: b1081b86-fdce-4fcc-82c4-51896de4418c] File "/usr/lib/python2.7/dist-packages/eventlet/tpool.py", line 183, in doit 2015-05-07 10:47:22.246 1331 TRACE nova.virt.libvirt.driver [instance: b1081b86-fdce-4fcc-82c4-51896de4418c] result = proxy_call(self._autowrap, f, *args, **kwargs) 2015-05-07 10:47:22.246 1331 TRACE nova.virt.libvirt.driver [instance: b1081b86-fdce-4fcc-82c4-51896de4418c] File "/usr/lib/python2.7/dist-packages/eventlet/tpool.py", line 141, in proxy_call 2015-05-07 10:47:22.246 1331 TRACE nova.virt.libvirt.driver [instance: b1081b86-fdce-4fcc-82c4-51896de4418c] rv = execute(f, *args, **kwargs) 2015-05-07 10:47:22.246 1331 TRACE nova.virt.libvirt.driver [instance: b1081b86-fdce-4fcc-82c4-51896de4418c] File "/usr/lib/python2.7/dist-packages/eventlet/tpool.py", line 122, in execute 2015-05-07 10:47:22.246 1331 TRACE nova.virt.libvirt.driver [instance: b1081b86-fdce-4fcc-82c4-51896de4418c] six.reraise(c, e, tb) 2015-05-07 10:47:22.246 1331 TRACE nova.virt.libvirt.driver [instance: b1081b86-fdce-4fcc-82c4-51896de4418c] File "/usr/lib/python2.7/dist-packages/eventlet/tpool.py", line 80, in tworker 2015-05-07 10:47:22.246 1331 TRACE nova.virt.libvirt.driver [instance: b1081b86-fdce-4fcc-82c4-51896de4418c] rv = meth(*args, **kwargs) 2015-05-07 10:47:22.246 1331 TRACE nova.virt.libvirt.driver [instance: b1081b86-fdce-4fcc-82c4-51896de4418c] File "/usr/lib/python2.7/dist-packages/libvirt.py", line 1241, in jobInfo 2015-05-07 10:47:22.246 1331 TRACE nova.virt.libvirt.driver [instance: b1081b86-fdce-4fcc-82c4-51896de4418c] if ret is None: raise libvirtError ('virDomainGetJobInfo() failed', dom=self) 2015-05-07 10:47:22.246 1331 TRACE nova.virt.libvirt.driver [instance: b1081b86-fdce-4fcc-82c4-51896de4418c] libvirtError: this function is not supported by the connection driver: virDomainGetJobInfo 2015-05-07 10:47:22.246 1331 TRACE nova.virt.libvirt.driver [instance: b1081b86-fdce-4fcc-82c4-51896de4418c] If someone has a clue what may cause this, pls help. Thanks. 本邮件仅针对指定的收件人发送并可能含有保密或专有内容。任何非指定收件人所为之查阅、转发或使用本信息是不被允许的。如果您误收到本邮件，请立即告知发件人并删除本邮件及所有附件。谢谢！ The information transmitted in this e-mail is intended only for the addressee and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of this information by persons or entities other than the intended recipient is prohibited. If you received this e-mail in error, please notify the sender immediately, and delete this e-mail and any attachments. Thank you.

3 2

[libvirt-users] Libvirt lvm pool and external snapshot
by Vasiliy Tolstov 07 May '15

07 May '15

Hello, does it possible to create external snapshot from lvm storage pool based VM? I want to create snapshot with disk only and doing volume download via libvirt api. How this possible? P.s. I know about lvm command for snapshot,but I need to use pure libvirt api.

1 0

[libvirt-users] problems with xl (libxenlight)
by big strong 07 May '15

07 May '15

Since new version of xen use xl as the default toolstack to manage xen, I've met a lot of problems. 1. xl has no commands such as start and clone, which is confusing. How can I bring a vm back after I shutdown it? 2. Each time I use 'xl shutdown domid' it comes into "PV control interface not available: external graceful shutdown not possible. Use "-F" to fallback to ACPI power event." The only way to do it is to use -F option and then the state of the vm turns to block. And it can never be started again. 3. If I want to use virt-manger with xl. How can I import a vm created with xl into virt-manager? I think there should be a convertion form cfg file to xml file, but I haven't found official solution. What I did is to create a new vm in virt-manager with the disk created by xl. but it always comes into error when I tried to manage vm with virt-manager. 4. how can I change back to use virsh instead of xl as the toolstack to manage xen? It's really aboring to counter all kinds of problems

1 0

[libvirt-users] Proper way to reference a disk
by Michael Schwager 06 May '15

06 May '15

Hi, We are running on CentOS 7.0. We want to move our VMs (kvm/qemu) from qcow/image files to logical volumes under LVM. I have moved one of them but I had a little trouble editing the disk properly and I wonder what is the correct way to do it. Specifically, in the XML under the devices/disk section why does the source say "source file=", and not "source dev="? The reason I ask is that I have a number of other machines to move and I don't want to mess them up. The source file entry for the disk was like this in our xml file: <source file='/var/lib/libvirt/images/pxetest.qcow2'/> I got the vm to work by converting the image to raw, then dumping via dd into the LV, and editing the XML using virsh as follows: <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='none'/> <*source file*='/dev/kvm_temp/pxetest'/> <target dev='vda' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> By comparison I have a test machine on another real host upon which I loaded a VM and put its disk into a logical volume. Its disk section looks like this: <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='none' io='native'/> <*source dev*='/dev/kvm_hosts/pxetest2'/> <target dev='hda' bus='ide'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> The source file / source dev thing really has me wondering. *- Mike Schwager* * Linux Network Engineer, Mocho Trading LLC* -- This message is for the named person(s) use only. It may contain confidential proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify the sender. You must not, directly or indirectly use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Mocho Trading LLC reserves the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorized to state them to be the views of any such entity.

2 3

[libvirt-users] Using Virtio drivers with kernal 2.6.18-164.el5
by Jatin Davey 06 May '15

06 May '15

Hi All I looked at this page for reference to using virtio drivers on KVM guests. http://wiki.libvirt.org/page/Virtio In the requirements section it is mentioned that we need a virtio compatible guest with kernel >= 2.6.25 One of my guest has this version: [root@localhost ~]# uname -a Linux localhost 2.6.18-164.el5 #1 SMP Thu Sep 3 03:28:30 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux I was still able to use the virtio drivers by enabling the corresponding options in the qemu xml file and also i created a new initrd image file inside my guest using the mkinitrd command as mentioned in the link provided above. My question is , Is it fine to use the virtio drivers with the kernel that i have for my guest or i definitely need to get to kernel version >= 2.6.25 ? Thanks Jatin

2 3

[libvirt-users] Source information not showing for virsh domiflist causing problems with migrating VMs
by Carl J Taylor 05 May '15

05 May '15

Hi, Does anyone know of a way to get around this problem. I have several long running VMs running on an Ubuntu 14.10 host and for some reason I am getting errors when trying to migrate them to another host. If I restart the VM then the problem does not exist, however for various reasons that is not an option with the remaining VMs. root@comp001:~# /root/bin/vm_migrate.sh ws001 comp003 virsh migrate --live --persistent --tunneled --p2p --unsafe --domain ws001 --desturi qemu+tcp://comp003/system error: internal error: No <source> 'bridge' attribute specified with <interface type='bridge'/> I have eventually figure out that the problem is not with the XML definitions for the host, but is related to the details of the network interfaces assigned to the host as output by the virsh domiflist command. The question I need to resolve is how do I populate the missing Source information. Any help gratefully appreciated. Kind regards Carl Taylor root@comp001:~# libvirtd --version libvirtd (libvirt) 1.2.8 root@comp001:~# virsh domiflist --inactive ws001 Interface Type Source Model MAC ------------------------------------------------------- - network br300 virtio 52:54:00:62:9b:20 - network br201 virtio 52:54:00:f0:73:85 - network default virtio 52:54:00:69:b1:e5 root@comp001:~# virsh domiflist ws001 Interface Type Source Model MAC ------------------------------------------------------- vnet18 bridge - virtio 52:54:00:62:9b:20 vnet19 bridge - virtio 52:54:00:f0:73:85 vnet20 network default virtio 52:54:00:69:b1:e5

1 0

[libvirt-users] [Libvirt Users]how to provide password authentication for qemu driver
by Dhaval_Shah1＠dell.com 05 May '15

05 May '15

Dell Customer Communication Hi All, I am using Compiled against library: libvirt 1.2.9 Using library: libvirt 1.2.9 Using API: QEMU 1.2.9 Running hypervisor: QEMU 2.1.2 I want user to provide username and password authentication to virConnectPtr virConnectOpenAuth(const char *name, virConnectAuthPtr auth, unsigned int flags) to login remotely for the qemu hypervisor. But it is not taking user provided username and driver. Because internally it is calling below qemu driver function, static virDrvOpenStatus qemuConnectOpen(virConnectPtr conn, virConnectAuthPtr auth ATTRIBUTE_UNUSED, unsigned int flags) so it is not taking any user provided auth parameters and it is internally calling separate function for prompting password. I don't want to provide password here. In case of windows HyperV it is working fine as it takes auth parameters but for Qemu Hypervisor I am facing this issue since here the auth parameters as marked as ATTRIBUTE_UNUSED. Can anyone help me with this that how can I achieve this? Thanks & Regards, Dhaval Shah

2 2

[libvirt-users] Hyperv on windows 2012 R2 support in libvirt
by doyensundu 04 May '15

04 May '15

Hi, I have been trying to work with libvirt apis to manage hyper-v on windows 2012 r2 server. I had taken patch a modified it to suite the latest code on GITHUB. I could able to connect. But i don't know what else to do and how to use the api's. There is no documentation. I want to use/manage hyper-v to provision guest OS's, configure network, create virtual switch etc. I see few classes ( https://msdn.microsoft.com/en-us/library/cc136822%28v=vs.85%29.aspx) have been implemented in libvirt. The classes include : Msvm_ComputerSystem, Msvm_ConcreteJob, Msvm_MemorySettingData, Msvm_ProcessorSettingData, Msvm_VirtualSystemSettingData, Win32_ComputerSystem, Win32_Processor. I want to know how to use libvirt api's to connect, provision a guest os, configure network. Few examples/guidance would be helpful to me. Thanks surender

1 0

[libvirt-users] Limitations of macvtap devices?
by Lars Kellogg-Stedman 04 May '15

04 May '15

I am running OpenStack inside a libvirt guest that is connected to the local network via a macvtap interface. My experience so far suggests that a macvtap interface will not pass traffic with a source MAC address other than the MAC address of the interface itself...for example, if inside the guest eth0 is attached to a bridge. Is that correct, or is there some setting that will make that work? Outbound traffic doesn't seem to be a problem (I can see, for example, dhcp requests on the local network), but replies get dropped before they reach the guest. Thanks, -- Lars Kellogg-Stedman <lars(a)redhat.com> | larsks @ {freenode,twitter,github} Cloud Engineering / OpenStack | http://blog.oddbit.com/

4 4

[libvirt-users] Improved Shared Folders UX and security
by drift＠ruggedinbox.com 03 May '15

03 May '15

Would it degrade security if libvirt were to handle SELinux labeling of shared folders automatically instead of the manual adjustments needed currently? Would it degrade security if libvirt were allowed to create a non existing shared directory specified in a VM's xml upon import?

1 0

[libvirt-users] SELinux for separate shared folders
by drift＠ruggedinbox.com 02 May '15

02 May '15

How can I enforce SELinux separation between the shared folders belonging to different VMs running with sVirt's SELinux dynamic labels? I want to create a permanent exception for VM 'A' to only be able to read and write to shared folder 'A' and the same for VM 'B' and shared folder 'B' svirt_image_t permits access to a shared folder but for all VMs.

1 0

[libvirt-users] libvirt nwfilter
by drift＠ruggedinbox.com 01 May '15

01 May '15

To take advantage of the filters, is it as simple as adding these couple of lines in a guest's xml file like the example from https://libvirt.org/formatnwfilter.html#nwfconcepts ? <devices> <interface type='bridge'> <mac address='00:16:3e:5d:c7:9e'/> <filterref filter='clean-traffic'> <parameter name='IP' value='10.0.0.1'/> </filterref> </interface> </devices> Can multiple filters be combined together like this? <filterref filter='clean-traffic' filter='no-ip-multicast'> <parameter name='IP' value='10.0.0.1'/> </filterref> Can the IP address parameter override the one in /etc/network/interfaces on the guest? When cloning a vm does it change the ip to avoid conflicts like it would with mac-addresses?

2 1