- Users - libvirt List Archives

[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

[libvirt-users] Sometimes libvirt fails to update domain block file after blockcommit.
by Matthew Schumacher 29 Apr '15

29 Apr '15

Posted to https://bugzilla.redhat.com/show_bug.cgi?id=1217185 I just stumbled on another bug while snapshotting and think it's related to 1210903 and 1197592 as it seems like some sort of race condition because it depends on what logging is in place and doesn't happen every time. Here are the details: I wrote this test script to snapshot and commit over and over: #!/bin/sh while [ 1 ]; do echo "Starting snapshot test `date`" virsh snapshot-create-as test 20150429 20150429-backup --disk-only --atomic virsh domblklist test virsh blockcommit test vda --active --pivot --verbose virsh snapshot-delete test 20150429 --metadata virsh domblklist test rm /glustervol1/vm/test/test.20150429 echo "Ending snapshot test `date`" echo echo sleep 2 done If I run libvirtd in the foreground with debug set to 1 I can't get it to fail, it does what it's supposed to do, snapshot and commit over and over. If I run libvirtd in the foreground with debug set to 3, then I will always eventually get this: Starting snapshot test Wed Apr 29 09:34:34 AKDT 2015 Domain snapshot 20150429 created Target Source ------------------------------------------------ vda /glustervol1/vm/test/test.20150429 hdc /dev/sr0 Block Commit: [100 %] Successfully pivoted Domain snapshot 20150429 deleted Target Source ------------------------------------------------ vda /glustervol1/vm/test/test.20150429 hdc /dev/sr0 Ending snapshot test Wed Apr 29 09:34:35 AKDT 2015 Starting snapshot test Wed Apr 29 09:34:37 AKDT 2015 error: unsupported configuration: source for disk 'vda' is not a regular file; refusing to generate external snapshot name Target Source ------------------------------------------------ vda /glustervol1/vm/test/test.20150429 hdc /dev/sr0 error: internal error: qemu block name '/glustervol1/vm/test/test.qcow2' doesn't match expected '/glustervol1/vm/test/test.20150429' error: Domain snapshot not found: no domain snapshot with matching name '20150429' Target Source ------------------------------------------------ vda /glustervol1/vm/test/test.20150429 hdc /dev/sr0 rm: can't remove '/glustervol1/vm/test/test.20150429': No such file or directory Ending snapshot test Wed Apr 29 09:34:37 AKDT 2015 At this point libvirt is confused about which file is the backing store because the first run did pivot after blockcommit, but didn't update the block file. From the logs: 2015-04-29 17:33:41.052+0000: 25192: warning : qemuDomainObjTaint:1972 : Domain id=2 name='test' uuid=4b9cc25b-68d1-4ce8-8a65-2a378e255e36 is tainted: high-privileges 2015-04-29 17:34:37.322+0000: 25191: error : virDomainSnapshotAlignDisks:609 : unsupported configuration: source for disk 'vda' is not a regular file; refusing to generate external snapshot name 2015-04-29 17:34:37.352+0000: 25194: error : qemuMonitorJSONDiskNameLookup:3977 : internal error: unable to find backing name for device drive-virtio-disk0 2015-04-29 17:34:37.354+0000: 25194: error : qemuMonitorJSONDiskNameLookupOne:3914 : internal error: qemu block name '/glustervol1/vm/test/test.qcow2' doesn't match expected '/glustervol1/vm/test/test.20150429' So libvirt insists that the block file is: root@wasvirt2:/glustervol1/vm/waspbx# virsh domblklist test Target Source ------------------------------------------------ vda /glustervol1/vm/test/test.20150429 hdc /dev/sr0 But that file isn't in use and isn't what qemu is using: root@wasvirt2:/glustervol1/vm/waspbx# lsof | grep test 25300 /usr/bin/qemu-system-x86_64 /var/log/libvirt/qemu/test.log 25300 /usr/bin/qemu-system-x86_64 /var/log/libvirt/qemu/test.log 25300 /usr/bin/qemu-system-x86_64 /glustervol1/vm/test/test.qcow2 The only way to straighten this out is to destroy and start the domain.

1 0

[libvirt-users] non failover equivalent to "virsh migrate --copy-storage-all"
by Andreas Buschmann 29 Apr '15

29 Apr '15

Hello, I have two servers where I can push VMs from one to the other by issuing the command virsh migrate --live --persistent --copy-storage-all --verbose \ test6 qemu+ssh://kvmhost2/system on kvmhost1. I can get the VM back by issuing the equivalent command on kvmhost2: virsh migrate --live --persistent --copy-storage-all --verbose \ test6 qemu+ssh://kvmhost1/system virsh copies the local data file /data/vm/test6.qcow2 with the filesystem over to the other server. Is there a way to just copy the data file over to the second server, without moving the VM? I want the equivalent of doing these two migrations is sequence, but without moving the VM. The goal is to get a backup copy of a running system onto a second system (kvmhost2). The copy (snapshot) from kvmhost2 can then be copied to a backup server, and can be used for a fast recovery point if kvmhost1 dies. Mit freundlichen Gruessen Andreas Buschmann -- Andreas Buschmann [Senior Systems Engineer] net.DE AG

3 3

[libvirt-users] Semantics of "virsh migrate --copy-storage-all" vs. --copy-storage-inc
by Andreas Buschmann 29 Apr '15

29 Apr '15

Hello, what is really the difference between virsh migrate --copy-storage-all and virsh migrate --copy-storage-inc ? There are some documents talking about NBD snapshots, but the user visible semantics are incomplete. Where does the incremental stuff happen? Does it require qcow2 files? Does it work with raw files? Does "--copy-storage-inc" require existing snapshots? Does "--copy-storage-inc" require existing snapshots which are in an external file so that there is a visible chain [base] <- [sn1] <- [sn2] Background: I am trying to understand what really happens, so I can use the tools for a reasonable fast failover between two servers with local storage. more Background: I have VMs and bare metal servers which do use expensive shared storages like NetApp, EMC² VNX, HP and others, but the shared storage boxes all require customer visible maintenance downtimes every 12 to 20 month. And these downtimes take a long lead time and are between 01:00 and 05:00. Mit freundlichen Gruessen Andreas Buschmann -- Andreas Buschmann [Senior Systems Engineer] net.DE AG

2 1

[libvirt-users] Virtual Smartcard GPG
by roky＠openmailbox.org 29 Apr '15

29 Apr '15

Hi. Is is possible to use GPG on the host instead of NSS with virtual smartcards? Please document how or add support for it. Can a virtual smartcard make the host less secure? If there are bugs in GPG/NSS backend on the host can they be abused by untrusted code in the vm?

2 1

[libvirt-users] Disable weak ciphers in vnc_tls
by Matthias Fenner 29 Apr '15

29 Apr '15

Dear libvirt team, we a currently in a pci-dss certification process and our security scanner found weak ciphers in the vlc_tls service on our centos6 box: When I scan using sslscan I can see that sslv3 and rc4 is accepted: inf0rmix@tardis:~$ sslscan myhost:16514 | grep Accepted Accepted SSLv3 256 bits DHE-RSA-AES256-SHA Accepted SSLv3 256 bits AES256-SHA Accepted SSLv3 128 bits DHE-RSA-AES128-SHA Accepted SSLv3 128 bits AES128-SHA Accepted SSLv3 128 bits RC4-SHA Accepted SSLv3 128 bits RC4-MD5 Accepted SSLv3 112 bits EDH-RSA-DES-CBC3-SHA Accepted SSLv3 112 bits DES-CBC3-SHA Accepted TLSv1 256 bits DHE-RSA-AES256-SHA Accepted TLSv1 256 bits DHE-RSA-CAMELLIA256-SHA Accepted TLSv1 256 bits AES256-SHA Accepted TLSv1 256 bits CAMELLIA256-SHA Accepted TLSv1 128 bits DHE-RSA-AES128-SHA Accepted TLSv1 128 bits DHE-RSA-CAMELLIA128-SHA Accepted TLSv1 128 bits AES128-SHA Accepted TLSv1 128 bits CAMELLIA128-SHA Accepted TLSv1 128 bits RC4-SHA Accepted TLSv1 128 bits RC4-MD5 Accepted TLSv1 112 bits EDH-RSA-DES-CBC3-SHA Accepted TLSv1 112 bits DES-CBC3-SHA how do we turn it off and only allow tlv>=1.1 Kind regards, Matthias Fenner

2 1