[libvirt-users] Create VMWare ESXi domain via virsh error(error: this function is not supported by the connection driver: virDomainCreateXML)
by mop amg
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!
13 years, 11 months
[libvirt-users] How to set image format to 'qcow2'
by 姜晓东
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>
<!--loader>/usr/lib/xen/boot/hvmloader</loader-->
<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="sdl" display=':0.0'/-->
<!--graphics type="desktop" fullscreen='yes'/-->
<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
13 years, 11 months
[libvirt-users] added second virtio-disk: disk order detected wrong
by Stefan G. Weichinger
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
13 years, 11 months
