Re: [libvirt-users] with current libvirt git virsh expects vbox, refuses kvm define
On Wed, Jul 27, 2011 at 09:21:08AM +0200, Matthias Bolte wrote:
The point is that libvirt autodetects the available hypervisors at
runtime when you don't specify a connection URI. For example, just
running virsh results in autodetecting VirtualBox because you have it
installed in a way that it's still working and due to the way libvirt
works internally VirtualBox comes before QEMU in the autodetection
list.
But shouldn't it autodetect _all_ available hypervisors and then, when an
xml file specifies kvm - which is available - use it rather than complain it
has a problem with it? You're describing the current behavior as if it's to
be accepted. Clearly having libvirt recognize that the kvm hypervisor is
available, and automatically using it when the xml file specifies it, does
not take some extraordinary level of clever programming. "The xml specifies
kvm. Do I have kvm? Why, yes I do!"
The initial "error: internal error unexpected domain type kvm,
expecting vbox" you saw was added recently to prevent incompatible
driver/config combinations. In you're case it highlighted that
autodetection didn't work for you as expected.
Fine, so when it recognizes it has the wrong driver for the config, it
should grab the right driver. No reason for it to complain to me about it.
It should simply do its job. Right? This is a bug that it doesn't?
Whit