[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] pool and VM disk/image connection
by Zdenek Styblik
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
13 years, 12 months
[libvirt-users] libvirt filters
by Anton Gorlov
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?
14 years
[libvirt-users] libvirtd & dnsmasq
by Mark Foster
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/
14 years
[libvirt-users] migration failure
by Mark Foster
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/
14 years
[libvirt-users] driver type for .vdi images?
by Benjamin Hagemann
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
14 years
[libvirt-users] Changing default nic and storage types
by Chris Phillips
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
14 years
[libvirt-users] network filtering
by Anton Gorlov
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
14 years
