On Wed, Jul 27, 2011 at 08:42:59AM -0400, Whit Blauvelt wrote: [..] > 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!" Virsh first opens a connection to an hypervisor, and then tries to run the commands (can be multiple one for example in shall mode). What you're suggestion is to do some introspection on the XML, and then change the way virsh works just for that command, that's not that trivial nor very clean. > > 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? On the other hand what was improved recently is that if a command like create uses the "wrong" hypervisor type in the XML we are now reporting the expected hypervisor type instead of just failing the operation as you got. If you try with 0.9.4-rc1 it should have that improvement, Daniel -- Daniel Veillard | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ daniel@xxxxxxxxxxxx | Rpmfind RPM search engine http://rpmfind.net/ http://veillard.com/ | virtualization library http://libvirt.org/
