Ken D'Ambrosio
2015-Oct-19 19:57 UTC
[libvirt-users] "failed to connect to the hypervisor"
Hi, all. Ubuntu host, attempting to get virsh working 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
------------------------------------------------------
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. And what puzzles me more is
that -- while I don't know what the output *should* look like -- to my
eye, strace seems to say that we're getting information back:
1940 read(5, "Node 1 MemTotal: 33011680 kB\nNode 1 MemFree:
32565612 kB\nNode 1 MemUsed: 446068 kB\nNode 1 Active:
57948 kB\nNode 1 Inactive: 77036 kB\nNode 1 Active(anon):
27688 kB\nNode 1 Inactive(anon): 84 kB\nNode 1 Active(file):
30260 kB\nNode 1 Inactive(file): 76952 kB\nNode 1 Unevictable:
52 kB\nNode 1
[...]
------------------------------------------------------
In my googling, I see mention of per-VM XML files that... do something.
But what they do, and how they're generated, doesn't seem clear. (E.g.,
XML mentioned here: http://libvirt.org/drvvbox.html -- it just sort of
sits there, with no context.) Is that something I need?
Thanks for any enlightenment you might be able to offer me,
-Ken
Martin Kletzander
2015-Oct-20 09:33 UTC
Re: [libvirt-users] "failed to connect to the hypervisor"
On Mon, Oct 19, 2015 at 03:57:39PM -0400, Ken D'Ambrosio wrote:>Hi, all. Ubuntu host, attempting to get virsh working 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 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.>------------------------------------------------------ > >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. And what >puzzles me more is that -- while I don't know what the output *should* >look like -- to my eye, strace seems to say that we're getting >information back: > >1940 read(5, "Node 1 MemTotal: 33011680 kB\nNode 1 MemFree: >32565612 kB\nNode 1 MemUsed: 446068 kB\nNode 1 Active: >57948 kB\nNode 1 Inactive: 77036 kB\nNode 1 Active(anon): >27688 kB\nNode 1 Inactive(anon): 84 kB\nNode 1 Active(file): >30260 kB\nNode 1 Inactive(file): 76952 kB\nNode 1 Unevictable: >52 kB\nNode 1 >[...] > >------------------------------------------------------ > >In my googling, I see mention of per-VM XML files that... do >something. But what they do, and how they're generated, doesn't seem >clear. (E.g., XML mentioned here: http://libvirt.org/drvvbox.html -- >it just sort of sits there, with no context.) Is that something I >need? > >Thanks for any enlightenment you might be able to offer me, > >-Ken > >_______________________________________________ >libvirt-users mailing list >libvirt-users@redhat.com >https://www.redhat.com/mailman/listinfo/libvirt-users
Ken D'Ambrosio
2015-Oct-20 15:59 UTC
Re: [libvirt-users] "failed to connect to the hypervisor"
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 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 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 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? 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. And what >> puzzles me more is that -- while I don't know what the output *should* >> look like -- to my eye, strace seems to say that we're getting >> information back: >> >> 1940 read(5, "Node 1 MemTotal: 33011680 kB\nNode 1 MemFree: >> 32565612 kB\nNode 1 MemUsed: 446068 kB\nNode 1 Active: >> 57948 kB\nNode 1 Inactive: 77036 kB\nNode 1 Active(anon): >> 27688 kB\nNode 1 Inactive(anon): 84 kB\nNode 1 Active(file): >> 30260 kB\nNode 1 Inactive(file): 76952 kB\nNode 1 Unevictable: >> 52 kB\nNode 1 >> [...] >> >> ------------------------------------------------------ >> >> In my googling, I see mention of per-VM XML files that... do >> something. But what they do, and how they're generated, doesn't seem >> clear. (E.g., XML mentioned here: http://libvirt.org/drvvbox.html -- >> it just sort of sits there, with no context.) Is that something I >> need? >> >> Thanks for any enlightenment you might be able to offer me, >> >> -Ken >> >> _______________________________________________ >> libvirt-users mailing list >> libvirt-users@redhat.com >> https://www.redhat.com/mailman/listinfo/libvirt-users