- Users - libvirt List Archives

[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 08 May '15

08 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