November 2010 - Users - libvirt List Archives

[libvirt-users] Create VMWare ESXi domain via virsh error(error: this function is not supported by the connection driver: virDomainCreateXML)
by mop amg 06 Dec '10

06 Dec '10

Hi, Dear Mr/Mrs. I have two questions ask for help: my virt-manager and libvirt version is : linux-vaan:~ # rpm -q libvirt libvirt-0.8.5-1.2.i586 linux-vaan:~ # uname -a Linux linux-vaan 2.6.34-12-desktop #1 SMP PREEMPT 2010-06-29 02:39:08 +0200 i686 i386 GNU/Linux linux-vaan:~ # rpm -q virt-manager virt-manager-0.8.5-3.1.i586 linux-vaan:~ # cat /etc/SuSE-release openSUSE 11.3 (i586) VERSION = 11.3 virsh # version Compiled against library: libvir 0.8.5 Using library: libvir 0.8.5 Using API: ESX 0.8.5 Running hypervisor: ESX 4.1.0 *question 1 : * When I try to create a vmware esxi domain from virsh like this : create --file /work/dom1.x there is a error message : error: Failed to create domain from /work/dom1.xml error: this function is not supported by the connection driver: virDomainCreateXML it seems dosen't support create esxi domain, but the http://libvirt.org/hvsupport.html show that is supported after ≥ 0.7.0 or create via virt-install linux-vaan:~ # virt-install --connect=esx:// root(a)192.168.8.162/?no_verify=1 -n rhel5 -r 512 --vcpus=1 --nodisks bridge=vmk0 --network bridge=vmk0 --pxe Enter root's password for 192.168.8.162: Starting install... ERROR this function is not supported by the connection driver: virDomainCreateXML how to fix it ? *dom1.xml* <domain type='vmware'> <name>dom1</name> <memory>524288</memory> <currentMemory>524288</currentMemory> <vcpu>1</vcpu> <os> <type arch='i686'>hvm</type> </os> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <disk type='file' device='disk'> <source file='[datastore1] rhel5/rhel5_2.vmdk'/> <target dev='sda' bus='scsi'/> <address type='drive' controller='0' bus='0' unit='0'/> </disk> <controller type='scsi' index='0' model='lsilogic'/> <interface type='bridge'> <mac address='00:0c:29:51:f1:1c'/> <source bridge='VM Network'/> </interface> </devices> </domain> *question 2:* vol-clone failed virsh # vol-clone --pool datastore1 rhel5/rhel5.vmdk rhel5/rhel5_2.vmdk error: Failed to clone vol from rhel5/rhel5.vmdk error: this function is not supported by the connection driver: virStorageVolCreateXMLFrom thanks for help! best regards!

2 1

[libvirt-users] pool and VM disk/image connection
by Zdenek Styblik 29 Nov '10

29 Nov '10

Dear list, I had a need to migrate pool resp. images in pool from /some/where/ to /some/where/else/. To my surprise, I just found out editing pool wasn't enough as each and every VM has full path to disk image not just "link" or "connection" to pool. I don't want to say this is bug or wrong doing; I don't want to say it isn't my fault, because it is and I should have study more carefully. What I'm asking for is an explanation of connection between images in pool, pool and VMs (or something like that). Just 1+1=? You see, my expectation was just to edit pool and it's all going to work-out. It didn't :) Thank you, Zdenek -- Zdenek Styblik Net/Linux admin OS TurnovFree.net email: stybla(a)turnovfree.net jabber: stybla(a)jabber.turnovfree.net

1 0

[libvirt-users] Anyone knows when is the next release for libvirt java bindings?
by Ravi Pawar 25 Nov '10

25 Nov '10

-- Thanks & Regards Ravi Pawar

1 1

[libvirt-users] libvirt filters
by Anton Gorlov 22 Nov '10

22 Nov '10

I used filters like clean-traffic. The filters are working, but I can not see the rules in iptables -L. How can I look through the rules?

4 4

[libvirt-users] libvirt dns-masq, enlarge max lease time?
by Денис Барышев 21 Nov '10

21 Nov '10

Hello! Is there any way conrol dnsmasq which is started by libvirt? For example, i want to enlarge max lease time. Thanks.

1 0

[libvirt-users] libvirtd & dnsmasq
by Mark Foster 20 Nov '10

20 Nov '10

libvirtd is starting dnsmasq! This is on RHEL5.5 I don't see it mentioned in /etc/init.d/libvirtd or /etc/libvirt/* or /etc/sysconfig/libvirtd 4337 ? S 0:00 /usr/sbin/dnsmasq --strict-order --bind-interfaces --pid-file=/var/run/libvirt/network/default.pid --conf-file= --listen-address 192.168.122.1 --except-interface lo --dhcp-range 192.168.122.2,192.168.122.254 --dhcp-lease-max=253 How can I properly disable this funcationality? (I'm running dnsmasq for other purposes on the host, and the libvirtd incantation conflicts). Thanks. -- Mark D. Foster <mark(a)foster.cc> http://mark.foster.cc/ | http://www.freegeekseattle.org/

4 4

[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 14 Nov '10

14 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

[libvirt-users] New wiki pages with libvirt SSH setup instructions
by Justin Clift 09 Nov '10

09 Nov '10

Hi all, Just added some new pages to the wiki, this time covering how to configure remote access to libvirt through SSH, not using root: http://wiki.libvirt.org/page/SSHSetup <--- entry page http://wiki.libvirt.org/page/SSHPolicyKitSetup This has details for several different Linux distributions: * RHEL 5 & 6 * Fedora 11-13 * Centos 5 & 6 * Ubuntu 10.04 Server & Desktop * openSUSE 11.2 onwards Does anyone have info they'd like to include for other distributions? :) Regards and best wishes, Justin Clift

2 7

[libvirt-users] Problem booting Microsoft Windows KVM virtual machine
by RaSca 04 Nov '10

04 Nov '10

Hi all, I'm having problems with a vm's startup, I cloned the entire disk of a Windows 2000 with dd on a drbd device, that disk was configured with two partitions. I'm able to see all the partitions contents by using kpartx and mount them: # kpartx -l /dev/drbd0 drbd0p1 : 0 202751488 /dev/drbd0 32 drbd0p2 : 0 285567360 /dev/drbd0 202751520 The problem is that when i try to startup the vm with virsh it hangs on boot by saying "error on operating system load". Here are the details and the vm conf: # cat /etc/libvirt/qemu/vm-sophos.xml <domain type='kvm'> <name>vm-sophos</name> <uuid>213a464c-73ad-8122-3647-7ff6b78d9e07</uuid> <memory>262144</memory> <currentMemory>262144</currentMemory> <vcpu>1</vcpu> <os> <type arch='i686' machine='pc-0.12'>hvm</type> <boot dev='cdrom'/> <boot dev='hd'/> </os> <features> <acpi/> <apic/> <pae/> </features> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/kvm</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/dev/drbd0'/> <target dev='hda' bus='ide'/> <address type='drive' controller='0' bus='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <target dev='hdc' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='1' unit='0'/> </disk> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <interface type='bridge'> <mac address='52:54:00:15:0d:68'/> <source bridge='br0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <input type='mouse' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' keymap='en-us'/> <video> <model type='cirrus' vram='9216' heads='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </memballoon> </devices> </domain> Note that I've tried to change "source file" parameter with /dev/dm-0p1, /dev/drbd0p1, but virsh don't let me boot the machine saying it is unable to find the disk. The kvm command launched by virsh is this one: /usr/bin/kvm -S -M pc-0.12 -cpu qemu32 -enable-kvm -m 256 -smp 1,sockets=1,cores=1,threads=1 -name vm-sophos -uuid 213a464c-73ad-8122-3647-7ff6b78d9e07 -nodefaults -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/vm-sophos.monitor,server,nowait -mon chardev=monitor,mode=readline -rtc base=utc -boot dc -drive file=/dev/drbd0,if=none,id=drive-ide0-0-0,boot=on,format=raw -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -drive if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -device rtl8139,vlan=0,id=net0,mac=52:54:00:15:0d:68,bus=pci.0,addr=0x3 -net tap,fd=44,vlan=0,name=hostnet0 -chardev pty,id=serial0 -device isa-serial,chardev=serial0 -usb -vnc 0.0.0.0:0 -k en-us -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 I'd also followed the steps described here: http://www.brandonturner.net/blog/2010/01/convert-windows-to-xen-guest/ to use fixmbr and the operation succeed, but the error on the vm is still the same. What should else i check? -- Raoul Scarazzini Mia Mamma Usa Linux: Niente è impossibile da capire, se lo spieghi bene! mobile: +393281776712 rasca(a)miamammausalinux.org http://www.miamammausalinux.org

1 0

[libvirt-users] controlling VM access to different tap devices
by Ryan Haggerty 03 Nov '10

03 Nov '10

Sorry if this off-topic but I have a qemu related question I was going to send to the qemu users mailing list but that list appears to have vanished. I thought this community might have some insight. I am interested in controlling VM access to different tap devices so I want to have different qemu processes bound to different tun devices. I've created new tun devices (eg. /dev/net/tun_low) followed by the use of tunctl to create new tap devices based off of the new device nodes (ie tunctl -t tap0 -f /dev/net/tun_low). This also did not seem to work as the VM's seemed to still be accessing /dev/net/tun (running strace on qemu-spice I found it was still doing an open on /dev/net/tun) and not my new device /dev/net/tun_low. Any suggestions on forcing qemu to use alternative tun devices?

1 0

[libvirt-users] controlling VM access to different tap devices
by Ryan Haggerty 02 Nov '10

02 Nov '10

Sorry if this off-topic but I have a qemu related question I was going to send to the qemu users mailing list but that list appears to have vanished. I thought this community might have some insight. I am interested in controlling VM access to different tap devices so I want to have different qemu processes bound to different tun devices. I've created new tun devices (eg. /dev/net/tun_low) followed by the use of tunctl to create new tap devices based off of the new device nodes (ie tunctl -t tap0 -f /dev/net/tun_low). This also did not seem to work as the VM's seemed to still be accessing /dev/net/tun (running strace on qemu-spice I found it was still doing an open on /dev/net/tun) and not my new device /dev/net/tun_low. Any suggestions on forcing qemu to use alternative tun devices?

1 0

[libvirt-users] Does current libvirt ruby support ruby 1.9.2? Or when will it support it?
by 李文兵 02 Nov '10

02 Nov '10

I'm using ruby 1.8.7 and going to port to ruby 1.9. I'd like to confirm whether the libvirt ruby support the latest ruby 1.9. Thanks.

3 2

[libvirt-users] Libvirt and LXC
by Mohd Izhar Firdaus Ismail 02 Nov '10

02 Nov '10

(oops accidentally sent to -owners) Hi, i'm trying to start a LXC guest on a F14 computer .. followed the examples in http://libvirt.org/drvlxc.html, but got stuck when starting it .. 03:07:23.706: debug : virCgroupNew:542 : New group / 03:07:23.707: debug : lxcControllerRun:563 : Setting up private /dev/pts 03:07:23.711: debug : lxcControllerRun:589 : Mouting 'devpts' on /var/lxc/f14/dev/pts 03:07:23.711: debug : lxcControllerRun:604 : Opening tty on private /var/lxc/f14/dev/pts/ptmx 03:07:23.714: debug : lxcContainerAvailable:897 : clone call returned Invalid argument, container support is not enabled 03:07:23.714: debug : lxcContainerStart:848 : Enable network namespaces 03:07:23.718: debug : lxcContainerStart:854 : clone() completed, new container PID is -1 03:07:23.718: error : lxcContainerStart:858 : Failed to run clone container: Invalid argument 03:07:23.718: debug : vethDelete:141 : veth: veth1 03:07:23.718: debug : virRunWithHook:820 : ip link del veth1 LXC config: <domain type='lxc'> <name>f14</name> <uuid>2dcd3cac-47e6-2915-554a-9713edf6ffd1</uuid> <memory>256000</memory> <currentMemory>256000</currentMemory> <vcpu>1</vcpu> <os> <type arch='x86_64'>exe</type> <init>/sbin/init</init> </os> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/libexec/libvirt_lxc</emulator> <filesystem type='mount'> <source dir='/var/lxc/f14'/> <target dir='/'/> </filesystem> <interface type='network'> <mac address='52:54:00:b0:de:18'/> <source network='default'/> </interface> <console type='pty'> <target type='serial' port='0'/> </console> </devices> </domain> I dont know what the invalid arguments are... 03:07:23.718: error : lxcContainerStart:858 : Failed to run clone container: Invalid argument thanks -- Mohd Izhar Firdaus Bin Ismail / KageSenshi Inigo Consulting (FOSS/Plone Development, Training & Services) http://www.inigo-tech.com Fedora Malaysia Contributor & Ambassador http://blog.kagesenshi.org 92C2 B295 B40B B3DC 6866 5011 5BD2 584A 8A5D 7331

2 1

[libvirt-users] SCSI tape drive device
by Tom Stave 01 Nov '10

01 Nov '10

I have a SCSI tape backup unit attached to a kvm host managed by libvirt. Is there a way to expose the SCSI device in libvirt so I could pass the device to a virtual machine and have the virtual machine control the tape backup? Defining the device as a SCSI disk does not appear to work. In this situation, live migration is not an issue. The VM would always be tied to this host.

3 2

[libvirt-users] libvirt problems. Create bridged network via cmdline?
by Денис Барышев 01 Nov '10

01 Nov '10

Hello! I've faced a weird problem. And I totally can't understand how libvirt handles networks. The thing that i need to do is simple. I create a bridge in my ubuntu host, the following config: *iface eth0 inet manual* * * *auto br0* *iface br0 inet dhcp* * bridge_ports eth0* * bridge_stp on* * bridge_maxwait 0* That's OK, and my bridge turns up automatically. But I don't understand why libvirt can't use it, it always want to create bridge on its own. So that when I try to create bridged network with the command: virsh virsh net-create net.xml net.xml contents: * <network>* * <name>virbreth0</name>* * <bridge name='br0' stp='on' delay='0' />* * </network>* I always get error ===> error: Failed to create network from net.xml error: cannot create bridge 'br0': File exists That's pretty obvious that libvirt wants to create bridge on its own. But what should I do in my specific situation. May be there is a workaround. I appreciate any help and ideas... Thanks for your answers. Best regards, Denis Barishev.

2 1

[libvirt-users] qemu sdl parameters via libvirt
by Bruce Hohl 01 Nov '10

01 Nov '10

Hello List, I run a few VMs via libvirt using '--sdl'. I would like to use qemu parameters -no-quit, -no-frame and -ctrl-grab with libvirt. Does libvirt support a way to use these qemu parameters? Does libvirt provide a way to add these options under <graphics/> in the domain.xml using 'virsh edit domain.xml'? My current <graphics/> is as follows: <graphics type='sdl' display=':0' xauth='/home/admin1/.Xauthority'/> I know I could just create a regular kvm start-up script and include these parameters but I would like to manages all VMs via libvirt & virt-manager.

2 1