- Users - libvirt List Archives

[libvirt-users] migration failure
by Mark Foster 19 Nov '10

19 Nov '10

I'm setting up to do live migrations. Running KVM and libvirt on Ubuntu 10.04.1 Guest vhsot23 has qcow2 on NFS share, accessible to both vhost23 and 24 /net/fs11/srv/customer/nfs/kvm/mem52.img root@vhost23:~# virsh migrate mem52 qemu+ssh://vhost24/system At this point, it just sits there. virsh list on both vhost systems show mem52 in a paused state. I check /var/log/libvirt/qemu/mem52.log on the target system vhost24 it states... qemu: warning: error while loading state for instance 0x0 of device 'ram' Further, if I do virsh destroy mem52 on the target it cleans up fine, but after Ctrl-C on the source, mem52 cannot be managed. root@vhost23:~# virsh destroy mem52 error: Failed to destroy domain mem52 error: Timed out during operation: cannot acquire state change lock Only way to recover is manually kill the kvm process id for that guest. Please help me get this to work. -- Mark D. Foster <mark(a)foster.cc> http://mark.foster.cc/ | http://www.freegeekseattle.org/

1 0

[libvirt-users] driver type for .vdi images?
by Benjamin Hagemann 18 Nov '10

18 Nov '10

Hello libvirt experts, I use libvirt (0.7.5-5ubuntu27.7) with KVM / qemu (0.12.3+noroms-0ubuntu9.2). Some machines use raw images but same use Virtualbox images (.vdi). Since last Ubuntu 10.04 LTS update I can not start the vdi-images. The "driver name= type=" option was new. <devices> <emulator>/usr/bin/kvm</emulator> <disk type='file' device='disk'> <driver name='qemu' type='vdi'/> <source file='/path/image.vdi'/> <target dev='hda' bus='ide'/> </disk> But when I try "type=vdi" I got in the Log-File: libvir: Security Labeling error : error calling aa_change_profile() so I checked: cat vdi-machine.xml | /usr/lib/libvirt/virt-aa-helper -r --uuid libvirt-XXXXXXXX-XXXXX-XXXX-XXXX-XXXXXXXXXXXX --dryrun -p 0 libvir: Domain Config error : internal error unknown disk format 'vdi' for image.vdi virt-aa-helper: error: invalid VM definition Next I checked libvirt.org: http://libvirt.org/storage.html Valid volume format types raw, bochs, cloop, cow, dmg, iso, qcow, qcow2, vmdk, vpc => But what is the right type for .vdi-Images? By the way, the examples at this site does not know the "driver name= type=" option. Thank you very much. -- Kind regards, Benny gpg 0xFC505AB0 jabber benny(a)benny.de sip benny(a)benny.de

2 1

[libvirt-users] Changing default nic and storage types
by Chris Phillips 17 Nov '10

17 Nov '10

Hi, Simple question that I can't track down any notable discussion about, let alone an answer... Is it possible to define what the "default" nic and storage types are? I am deploying images out of cobbler using koan and all of them are running virtio wherever applicable, but this is not the default, and at present there is no way within koan or cobbler to define what type of devices they should be. I've hard coded this device type declaration into koan, but don't like that in the slightest, and would typically expect to be able to just set "default=virtio" in a libvirt config file somewhere. I fear I'm actually not missing anything and it's just hard coded for the most compatible device with no recourse to override it. Thanks Chris

4 4

[libvirt-users] network filtering
by Anton Gorlov 17 Nov '10

17 Nov '10

I try to add some rules to filtering network, example <filterref filter='clean-traffic'/> or <filterref filter='no-ip-spoofing'/> and vm not starting with message virsh start freebsd8.2 error: Failed to start domain freebsd8.2 error: internal error IP parameter must be given since libvirt was not compiled with IP address learning support what do I do wrong? libvirtd --version libvirtd (libvirt) 0.8.4

2 6

[libvirt-users] (no subject)
by David M. Barlieb 17 Nov '10

17 Nov '10

HI, I've just begun using libvirt as part of my KVM installation and have been having some confusion regarding networking of my virtual guests. I'm not sure if I should even be sending this to this mailing list and if not please let me know and if possible where I should be sending this inquiry. I understand I can setup a dedicated bridged interface for my guest. But as for the virbr interface which is the default, I'm a little confused about. When using this, does the guest os use the same ip as the host? If so, then how to packets get to the guest instead of the host. I would guess there's an alternate mac address for the guest interface and this is how it gets there but am not certain. Sorry if this seems like a simple question but I'm not very well versed in networking. daveb

4 3

[libvirt-users] java binding and virtualbox-ose
by Andrea Turli 15 Nov '10

15 Nov '10

I'm trying to connect to vbox hypervisor on an Ubuntu 10.04 machine through libvirt java binding (libvirt-java-0.4.6) by simply invoking: Connect conn = new Connect("vbox:///session", false); but I got this exception: libvir: warning : Failed to find the interface: Is the daemon running ? libvir: Remote error : unable to connect to '/var/run/libvirt/libvirt-sock': Connection refused libvir: warning : Failed to find a node driver: Is the libvirtd daemon running ? libvir: Remote error : unable to connect to '/var/run/libvirt/libvirt-sock': Connection refused libvir: warning : Failed to find a secret storage driver: Is the daemon running ? org.libvirt.LibvirtException: Failed to find a secret storage driver: Is the daemon running ? at org.libvirt.ErrorHandler.processError(ErrorHandler.java:28) at org.libvirt.Connect.<init>(Connect.java:195) at VBOX.main(VBOX.java:32) Otherwise, from virsh, I can correctly connect to the vbox hypervisor: $ export LIBVIRT_DEBUG=1 $virsh -c vbox:///session list --all 11:37:18.318: debug : virInitialize:336 : register drivers 11:37:18.318: debug : virRegisterDriver:837 : registering Test as driver 0 11:37:18.318: debug : virRegisterNetworkDriver:675 : registering Test as network driver 0 11:37:18.318: debug : virRegisterInterfaceDriver:706 : registering Test as interface driver 0 11:37:18.318: debug : virRegisterStorageDriver:737 : registering Test as storage driver 0 11:37:18.318: debug : virRegisterDeviceMonitor:768 : registering Test as device driver 0 11:37:18.318: debug : virRegisterSecretDriver:799 : registering Test as secret driver 0 11:37:18.318: debug : virRegisterDriver:837 : registering Xen as driver 1 11:37:18.318: debug : virRegisterDriver:837 : registering OPENVZ as driver 2 11:37:18.336: debug : vboxRegister:83 : VBoxCGlueInit found API version: 3.1.6 (3001006) 11:37:18.336: debug : vboxRegister:100 : VirtualBox API version: 3.1 11:37:18.336: debug : virRegisterDriver:837 : registering VBOX as driver 3 11:37:18.336: debug : virRegisterNetworkDriver:675 : registering VBOX as network driver 1 11:37:18.336: debug : virRegisterStorageDriver:737 : registering VBOX as storage driver 1 11:37:18.336: debug : virRegisterDriver:837 : registering remote as driver 4 11:37:18.336: debug : virRegisterNetworkDriver:675 : registering remote as network driver 2 11:37:18.336: debug : virRegisterInterfaceDriver:706 : registering remote as interface driver 1 11:37:18.336: debug : virRegisterStorageDriver:737 : registering remote as storage driver 2 11:37:18.336: debug : virRegisterDeviceMonitor:768 : registering remote as device driver 1 11:37:18.336: debug : virRegisterSecretDriver:799 : registering remote as secret driver 1 11:37:18.336: debug : virConnectOpenAuth:1337 : name=vbox:///session, auth=0x231638, flags=0 11:37:18.336: debug : do_open:1106 : name "vbox:///session" to URI components: scheme vbox opaque (null) authority (null) server (null) user (null) port 0 path /session 11:37:18.336: debug : do_open:1116 : trying driver 0 (Test) ... 11:37:18.336: debug : do_open:1122 : driver 0 Test returned DECLINED 11:37:18.336: debug : do_open:1116 : trying driver 1 (Xen) ... 11:37:18.336: debug : do_open:1122 : driver 1 Xen returned DECLINED 11:37:18.336: debug : do_open:1116 : trying driver 2 (OPENVZ) ... 11:37:18.336: debug : do_open:1122 : driver 2 OPENVZ returned DECLINED 11:37:18.336: debug : do_open:1116 : trying driver 3 (VBOX) ... 11:37:18.589: debug : vboxOpen:836 : in vboxOpen 11:37:18.589: debug : do_open:1122 : driver 3 VBOX returned SUCCESS 11:37:18.589: debug : do_open:1142 : network driver 0 Test returned DECLINED 11:37:18.589: debug : vboxNetworkOpen:5439 : network initialized 11:37:18.589: debug : do_open:1142 : network driver 1 VBOX returned SUCCESS 11:37:18.589: debug : do_open:1161 : interface driver 0 Test returned DECLINED 11:37:18.589: debug : doRemoteOpen:564 : proceeding with name = vbox:///session 11:37:18.590: debug : remoteIO:8455 : Do proc=66 serial=0 length=28 wait=(nil) 11:37:18.590: debug : remoteIO:8517 : We have the buck 66 0xb7516008 0xb7516008 11:37:18.595: debug : remoteIODecodeMessageLength:7939 : Got length, now need 64 total (60 more) 11:37:18.595: debug : remoteIOEventLoop:8381 : Giving up the buck 66 0xb7516008 (nil) 11:37:18.595: debug : remoteIO:8548 : All done with our call 66 (nil) 0xb7516008 11:37:18.596: debug : remoteIO:8455 : Do proc=1 serial=1 length=56 wait=(nil) 11:37:18.596: debug : remoteIO:8517 : We have the buck 1 0x95eb908 0x95eb908 11:37:18.659: debug : remoteIOEventLoop:8402 : Giving up the buck due to I/O error 1 0x95eb908 (nil) 11:37:18.660: debug : do_open:1161 : interface driver 1 remote returned ERROR 11:37:18.660: debug : do_open:1181 : storage driver 0 Test returned DECLINED 11:37:18.660: debug : vboxStorageOpen:6191 : vbox storage initialized 11:37:18.660: debug : do_open:1181 : storage driver 1 VBOX returned SUCCESS 11:37:18.660: debug : do_open:1201 : node driver 0 Test returned DECLINED 11:37:18.660: debug : doRemoteOpen:564 : proceeding with name = vbox:///session 11:37:18.661: debug : do_open:1201 : node driver 1 remote returned ERROR 11:37:18.661: debug : do_open:1228 : secret driver 0 Test returned DECLINED 11:37:18.661: debug : doRemoteOpen:564 : proceeding with name = vbox:///session 11:37:18.661: debug : do_open:1228 : secret driver 1 remote returned ERROR 11:37:18.661: debug : virConnectNumOfDomains:1714 : conn=0x95a1910 11:37:18.663: debug : virConnectNumOfDefinedDomains:4554 : conn=0x95a1910 11:37:18.664: debug : virConnectListDefinedDomains:4593 : conn=0x95a1910, names=0x95e9b58, maxnames=1 Id Name State ---------------------------------- 11:37:18.666: debug : virDomainLookupByName:1974 : conn=0x95a1910, name=tty 11:37:18.669: debug : virGetDomain:345 : New hash entry 0x95dad48 11:37:18.669: debug : virDomainGetInfo:2825 : domain=0x95dad48, info=0xbfeca708 - tty shut off 11:37:18.673: debug : virDomainFree:2062 : domain=0x95dad48 11:37:18.673: debug : virUnrefDomain:422 : unref domain 0x95dad48 tty 1 11:37:18.673: debug : virReleaseDomain:376 : release domain 0x95dad48 tty 11:37:18.673: debug : virReleaseDomain:392 : unref connection 0x95a1910 2 11:37:18.673: debug : virConnectClose:1355 : conn=0x95a1910 11:37:18.673: debug : virUnrefConnect:259 : unref connection 0x95a1910 1 11:37:18.673: debug : vboxNetworkClose:5448 : network uninitialized 11:37:18.673: debug : vboxStorageClose:6200 : vbox storage uninitialized 11:37:18.673: debug : vboxClose:843 : VBOX: in vboxClose 11:37:18.681: debug : virReleaseConnect:216 : release connection 0x95a1910 even if with some warnings/errors. Do you have any hint? Thank you -- Andrea Turli Ricercatore Direzione Ricerca e Innovazione andrea.turli(a)eng.it Engineering Ingegneria Informatica spa Via Riccardo Morandi, 32 00148 Roma (RM) Tel. +39 06 8307 4710 Fax +39 06 8307 4200 www.eng.it

3 3

[libvirt-users] ESX(i) implemented functions
by Sherif Nagy 15 Nov '10

15 Nov '10

Dear All, I would like to know what functions and classes are implemented in the ESX(i) driver ? i am trying to use virsh to retrieve some simple information such as vcpuinfo domain, but it is not working, so I would like to know what functions are implemented in libvirt ESX(i) driver. Also i checked the http://libvirt.org/drvesx.html and nothing is mentioned there. Thank You, Regards, Sherif

3 2

[libvirt-users] libvirtio version compatibility...
by Erik Brakkee 14 Nov '10

14 Nov '10

Hi, I intend to run a server with about 4 VMs with KVM and would like to use virtio for performance. However, one thing that is holding me back is compatibility. In the past I have seen with Xen that the paravirtualized drivers of one version in the host (dom0) would not always be compatible with a version in the client. If I would run into compatibility problems than I would like to continue to use full virtualization despite the performance impact. Therefore my question. In case I am running a setup with a host and a number of domains, is it guaranteed that I can do the following: * upgrade the host independent of the guests * upgrade a guest independent of the host Cheers Erik -- Nonsense and other useful things: http://brakkee.org MountainHoppers: http://mountainhoppers.nl Track Detective: http://trackdetective.com Twitter: http://twitter.com/ErikBrakkee

1 0

[libvirt-users] java binding and virtualbox-ose
by Andrea Turli 14 Nov '10

14 Nov '10

I'm trying to connect to vbox hypervisor on an Ubuntu 10.04 machine through libvirt java binding (libvirt-java-0.4.6) by simply invoking: Connect conn = new Connect("vbox:///session", false); but I got this exception: libvir: warning : Failed to find the interface: Is the daemon running ? libvir: Remote error : unable to connect to '/var/run/libvirt/libvirt-sock': Connection refused libvir: warning : Failed to find a node driver: Is the libvirtd daemon running ? libvir: Remote error : unable to connect to '/var/run/libvirt/libvirt-sock': Connection refused libvir: warning : Failed to find a secret storage driver: Is the daemon running ? org.libvirt.LibvirtException: Failed to find a secret storage driver: Is the daemon running ? at org.libvirt.ErrorHandler.processError(ErrorHandler.java:28) at org.libvirt.Connect.<init>(Connect.java:195) at VBOX.main(VBOX.java:32) Otherwise, from virsh, I can correctly connect to the vbox hypervisor: $ export LIBVIRT_DEBUG=1 $virsh -c vbox:///session list --all 11:37:18.318: debug : virInitialize:336 : register drivers 11:37:18.318: debug : virRegisterDriver:837 : registering Test as driver 0 11:37:18.318: debug : virRegisterNetworkDriver:675 : registering Test as network driver 0 11:37:18.318: debug : virRegisterInterfaceDriver:706 : registering Test as interface driver 0 11:37:18.318: debug : virRegisterStorageDriver:737 : registering Test as storage driver 0 11:37:18.318: debug : virRegisterDeviceMonitor:768 : registering Test as device driver 0 11:37:18.318: debug : virRegisterSecretDriver:799 : registering Test as secret driver 0 11:37:18.318: debug : virRegisterDriver:837 : registering Xen as driver 1 11:37:18.318: debug : virRegisterDriver:837 : registering OPENVZ as driver 2 11:37:18.336: debug : vboxRegister:83 : VBoxCGlueInit found API version: 3.1.6 (3001006) 11:37:18.336: debug : vboxRegister:100 : VirtualBox API version: 3.1 11:37:18.336: debug : virRegisterDriver:837 : registering VBOX as driver 3 11:37:18.336: debug : virRegisterNetworkDriver:675 : registering VBOX as network driver 1 11:37:18.336: debug : virRegisterStorageDriver:737 : registering VBOX as storage driver 1 11:37:18.336: debug : virRegisterDriver:837 : registering remote as driver 4 11:37:18.336: debug : virRegisterNetworkDriver:675 : registering remote as network driver 2 11:37:18.336: debug : virRegisterInterfaceDriver:706 : registering remote as interface driver 1 11:37:18.336: debug : virRegisterStorageDriver:737 : registering remote as storage driver 2 11:37:18.336: debug : virRegisterDeviceMonitor:768 : registering remote as device driver 1 11:37:18.336: debug : virRegisterSecretDriver:799 : registering remote as secret driver 1 11:37:18.336: debug : virConnectOpenAuth:1337 : name=vbox:///session, auth=0x231638, flags=0 11:37:18.336: debug : do_open:1106 : name "vbox:///session" to URI components: scheme vbox opaque (null) authority (null) server (null) user (null) port 0 path /session 11:37:18.336: debug : do_open:1116 : trying driver 0 (Test) ... 11:37:18.336: debug : do_open:1122 : driver 0 Test returned DECLINED 11:37:18.336: debug : do_open:1116 : trying driver 1 (Xen) ... 11:37:18.336: debug : do_open:1122 : driver 1 Xen returned DECLINED 11:37:18.336: debug : do_open:1116 : trying driver 2 (OPENVZ) ... 11:37:18.336: debug : do_open:1122 : driver 2 OPENVZ returned DECLINED 11:37:18.336: debug : do_open:1116 : trying driver 3 (VBOX) ... 11:37:18.589: debug : vboxOpen:836 : in vboxOpen 11:37:18.589: debug : do_open:1122 : driver 3 VBOX returned SUCCESS 11:37:18.589: debug : do_open:1142 : network driver 0 Test returned DECLINED 11:37:18.589: debug : vboxNetworkOpen:5439 : network initialized 11:37:18.589: debug : do_open:1142 : network driver 1 VBOX returned SUCCESS 11:37:18.589: debug : do_open:1161 : interface driver 0 Test returned DECLINED 11:37:18.589: debug : doRemoteOpen:564 : proceeding with name = vbox:///session 11:37:18.590: debug : remoteIO:8455 : Do proc=66 serial=0 length=28 wait=(nil) 11:37:18.590: debug : remoteIO:8517 : We have the buck 66 0xb7516008 0xb7516008 11:37:18.595: debug : remoteIODecodeMessageLength:7939 : Got length, now need 64 total (60 more) 11:37:18.595: debug : remoteIOEventLoop:8381 : Giving up the buck 66 0xb7516008 (nil) 11:37:18.595: debug : remoteIO:8548 : All done with our call 66 (nil) 0xb7516008 11:37:18.596: debug : remoteIO:8455 : Do proc=1 serial=1 length=56 wait=(nil) 11:37:18.596: debug : remoteIO:8517 : We have the buck 1 0x95eb908 0x95eb908 11:37:18.659: debug : remoteIOEventLoop:8402 : Giving up the buck due to I/O error 1 0x95eb908 (nil) 11:37:18.660: debug : do_open:1161 : interface driver 1 remote returned ERROR 11:37:18.660: debug : do_open:1181 : storage driver 0 Test returned DECLINED 11:37:18.660: debug : vboxStorageOpen:6191 : vbox storage initialized 11:37:18.660: debug : do_open:1181 : storage driver 1 VBOX returned SUCCESS 11:37:18.660: debug : do_open:1201 : node driver 0 Test returned DECLINED 11:37:18.660: debug : doRemoteOpen:564 : proceeding with name = vbox:///session 11:37:18.661: debug : do_open:1201 : node driver 1 remote returned ERROR 11:37:18.661: debug : do_open:1228 : secret driver 0 Test returned DECLINED 11:37:18.661: debug : doRemoteOpen:564 : proceeding with name = vbox:///session 11:37:18.661: debug : do_open:1228 : secret driver 1 remote returned ERROR 11:37:18.661: debug : virConnectNumOfDomains:1714 : conn=0x95a1910 11:37:18.663: debug : virConnectNumOfDefinedDomains:4554 : conn=0x95a1910 11:37:18.664: debug : virConnectListDefinedDomains:4593 : conn=0x95a1910, names=0x95e9b58, maxnames=1 Id Name State ---------------------------------- 11:37:18.666: debug : virDomainLookupByName:1974 : conn=0x95a1910, name=tty 11:37:18.669: debug : virGetDomain:345 : New hash entry 0x95dad48 11:37:18.669: debug : virDomainGetInfo:2825 : domain=0x95dad48, info=0xbfeca708 - tty shut off 11:37:18.673: debug : virDomainFree:2062 : domain=0x95dad48 11:37:18.673: debug : virUnrefDomain:422 : unref domain 0x95dad48 tty 1 11:37:18.673: debug : virReleaseDomain:376 : release domain 0x95dad48 tty 11:37:18.673: debug : virReleaseDomain:392 : unref connection 0x95a1910 2 11:37:18.673: debug : virConnectClose:1355 : conn=0x95a1910 11:37:18.673: debug : virUnrefConnect:259 : unref connection 0x95a1910 1 11:37:18.673: debug : vboxNetworkClose:5448 : network uninitialized 11:37:18.673: debug : vboxStorageClose:6200 : vbox storage uninitialized 11:37:18.673: debug : vboxClose:843 : VBOX: in vboxClose 11:37:18.681: debug : virReleaseConnect:216 : release connection 0x95a1910 even if with some warnings/errors. Do you have any hint? Thank you -- Andrea Turli Ricercatore Direzione Ricerca e Innovazione andrea.turli(a)eng.it Engineering Ingegneria Informatica spa Via Riccardo Morandi, 32 00148 Roma (RM) Tel. +39 06 8307 4710 Fax +39 06 8307 4200 www.eng.it

1 0

[libvirt-users] Updating Multiple VM Guests?
by Kenneth Stailey 12 Nov '10

12 Nov '10

Hi, The libvirt.org FAQ says that "virsh edit" is the recommended way of updating the libvirt xml. If a change has to be made to many VMs "virsh edit" is tedious, time-consuming and likely to be prone to careless errors. Is there a command line approach to updating multiple VMs? Thanks, Ken

4 8