- 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 07 Dec '10

07 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] How to set image format to 'qcow2'
by 姜晓东 05 Dec '10

05 Dec '10

Hi, all My xml 'dom1.xml' is as following: <domain type='kvm' id='1'> <name>kvm-xp</name> <description>xp kvm</description> <memory>524288</memory> <currentMemory>524288</currentMemory> <os> <type>hvm</type>  <boot dev="hd"/> </os> <devices> <disk type='file'> <source file='/home/eucalyptus/imgs/xp.img'/> <target dev='hda' bus='ide'/> </disk> <driver name='qemu' type='qcow2'/>   <graphics type='vnc' port='5904'/> </devices> </domain> In this xml file, I don't know how to set disk file format to 'qcow2'. When I create domain using this command: virsh create dom1.xml I cannot boot the image file. The log file /var/log/libvirt/qemu/kvm-xp.log is as following: LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/sbin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.4.3 HOME=/root USER=root QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc -m 512 -smp 1 -name kvm-xp -uuid a8cbae31-59a0-0bc5-4416-65ba63aa4231 -monitor unix:/var/lib/libvirt/qemu/kvm-xp.monitor,server,nowait -no-acpi -boot c -drive file=/home/eucalyptus/imgs/xp.img,if=ide,bus=0,unit=0,format=raw -net none -serial none -parallel none -usb -vnc 127.0.0.1:4 -vga cirrus -balloon virtio I don't know how to set format argument to 'qcow2' ---------------- Xiaodong Jiang jxd431(a)gmail.com

2 1

[libvirt-users] added second virtio-disk: disk order detected wrong
by Stefan G. Weichinger 04 Dec '10

04 Dec '10

Greets, I am unsure if it's a linux- or libvirt-issue: I added a 2nd virtio-disk to a kvm-based VM. The xml shows a correct "target": # first disk vda <disk type='file' device='disk'> <driver name='qemu' type='qcow2'/> <source file='/mnt/r0/vm1_vda-clone.img'/> <target dev='vda' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> # second disk vdb <disk type='file' device='disk'> <driver name='qemu' type='qcow2'/> <source file='/mnt/r0/www3_var.img'/> <target dev='vdb' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </disk> The VM contains Gentoo Linux, grub comes up fine, but then it flips the devices: The unpartitioned new disk is vda, therefore there is no root-fs etc ... I know my way to fix this via Live-CD or so, but I would really like to understand what happened! I'd like to keep vda as root etc. Could someone explain? libvirt-0.8.6 and qemu-kvm-0.13.0-r2 on a gentoo-host, btw. Thanks, Stefan

1 2

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

20 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 19 Nov '10

19 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