libvirt users - Jul 2011 - with current libvirt git virsh expects vbox, refuses kvm define

Okay, just installed libvirt from today's git on two Ubuntu systems. The
first one went fine (except for continuation of the problem that virsh and
virt-manager cannot connect to 0.8.3 systems that's been there in the 0.9.x
libvirts) ... but on the second, after install, "virsh list --all"
presents
nothing. And:

  # virsh define tu1004.xml 
  error: Failed to define domain from tu1004.xml
  error: internal error unexpected domain type kvm, expecting vbox

These are _exactly_ the same xml files as are still working on the first
system. And in both cases the new libvirt was built with defaults. Long ago
the second system did have VirtualBox on it, so that may have been found
while it was setting up config, but that's no good reason for KVM to fail
here, right?

Must be a thing with the git. Ran the 0.9.3 release built on this system
previously without this problem.

Whit

? 2011?07?27? 08:04, Whit Blauvelt ??:
> Okay, just installed libvirt from today's git on two Ubuntu systems.
The
> first one went fine (except for continuation of the problem that virsh and
> virt-manager cannot connect to 0.8.3 systems that's been there in the
0.9.x
> libvirts) ... but on the second, after install, "virsh list
--all" presents
> nothing. And:
>
>    # virsh define tu1004.xml
>    error: Failed to define domain from tu1004.xml
>    error: internal error unexpected domain type kvm, expecting vbox
>
> These are _exactly_ the same xml files as are still working on the first
> system. And in both cases the new libvirt was built with defaults. Long ago
> the second system did have VirtualBox on it, so that may have been found
> while it was setting up config, but that's no good reason for KVM to
fail
> here, right?
>
> Must be a thing with the git. Ran the 0.9.3 release built on this system
> previously without this problem.
>
> Whit
>
> _______________________________________________
> libvirt-users mailing list
> libvirt-users at redhat.com
> https://www.redhat.com/mailman/listinfo/libvirt-users
Hi, Whit

What's the output of "# virsh -V" on your second ubuntu box? I
guess
your libvirt on that box might not be compiled with qemu driver.

Another possiablity is the libvirt is compiled with both qemu driver and 
vbox
driver, but when you try to creat a new connection, vbox was the first
succesfully connected one. In this case, you can try like below:

# virsh -c qemu:///sytem list --all

Or you can set the ENV variable VIRSH_DEFAULT_CONNECT_URI or
LIBVIRT_DEFAULT_URI to the URI of the hypervisor you want to connect to.

Osier