Error Failed To Initialize Hypervisor Driver
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Sun, 09 Oct 2016 23:25:41 GMT by s_ac5 (squid/3.5.20)
[ DST ] Get VirtualBox Forum powered by phpBB © phpBB Group By any use of this Website, you agree to be bound by these Policies and Terms of Use Sponsored by
libvirt-users redhat com Subject: Re: [libvirt-users] "failed to connect to the hypervisor" Date: Wed, 21 Oct 2015 08:41:21 +0200 On Tue, Oct 20, 2015 at 11:59:03AM https://www.redhat.com/archives/libvirt-users/2015-October/msg00048.html -0400, Ken D'Ambrosio wrote: On 2015-10-20 05:33, Martin Kletzander wrote: On Mon, Oct 19, 2015 at 03:57:39PM -0400, Ken D'Ambrosio wrote: Hi, all. Ubuntu host, attempting to get virsh working https://kb.vmware.com/kb/2003484 with VirtualBox... and failing. Here's what happens: root foobox:~# virsh -c vbox:///session list error: failed to connect to the hypervisor error: internal error: unable to initialize VirtualBox driver API What failed to version of VirtualBox do you have installed? The logging in that driver is not particularly loud, so this won't tell you much more than the fact that the initialization just failed. It's most probably something missing in your system or you have to new version installed. You're on the money: I do have the latest and greatest (5.0.6) from Oracle could not initialize installed. Despite some of its nifty features, I'm not wedded to it, if downgrading will fix my underlying issue. Is that the recommended course of action? Or is there something else I could do? Well, of course the best thing would be adding support for it into libvirt =) If it is backwards compatible with the latest version that has support in libvirt, then it shouldn't be a problem, I think, but I have very limited experience with the vbox driver in libvirt. Feel free to have a look at the code and let me know, I'm sure we'll come up with something. In the meantime I'll compile the 5.0.8 version (so I don't have to agree with the PUEL license) and see what I can do. Thanks much! -Ken ------------------------------------------------------ Now, most of the docs I read about "failed to connect to the hypervisor" have other errors that happen *before* the "failed to connect" one, that are the root cause (e.g., unable to open socket, or bad cert, or whatever). But that's not the case, here. An