2011/6/4 Richard Laager <rlaager@xxxxxxxxxx>: > On Fri, 2011-06-03 at 22:06 +0200, Ruben Kerkhof wrote: >> >> If I don't have the VirtualBox GUI running, virsh fails to connect: >> >> >> >> /usr/local/bin/virsh -c vbox:///session >> >> ... hangs for 10 or so seconds ... >> >> error: internal error nsIEventQueue object is null >> >> error: failed to connect to the hypervisor >> > >> > This is typically a sign of a COM object ID mismatch between >> > VirtualBox and libvirt. What versions of libvirt and VirtualBox are >> > you running? By any chance are you running a beta or release candidate >> > of VirtualBox? >> >> libvirt-0.9.2-rc2, and VirtualBox-4.0.8-SunOS-r71778.pkg from www.virtualbox.org > > I'm running libvirt-0.9.1 and the same VirtualBox > (VirtualBox-4.0.8-SunOS-r71778.pkg). > > Richard > Okay VirtualBox 4.0.8 work with libvirt on Windows too. So this seems to be a Solaris specific problem. Does an earlier version of VirtualBox work, for example 4.0.0 or 3.2.10, or did it never work? Matthias -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list