[arch-general] libvirt and VirtualBox
Hello On an up-to-date Arch x86-64 system, I fail to manage VirtualBox VMs with libvirt virsh: $ virsh -c vbox:///session error: failed to connect to the hypervisor error: internal error: unable to initialize VirtualBox driver API Is this supposed to work out of the box? Both VirtualBox (5.0.14-1) and libvirt (1.3.2-1) are installed from the community repository, and VirtualBox support seems to be compiled in: $ virsh -V Virsh command line tool of libvirt 1.3.2 [...] Compiled with support for: Hypervisors: QEMU/KVM LXC UML OpenVZ VMware PHYP VirtualBox ESX Test [...] Furthermore, both VirtualBox alone (i.e. when managed by VBoxManage or similar) and libvirt when used to manage QEMU/KVM sessions work fine. Any hints about what I'm missing? TIA & cheers, Jukka -- This email fills a much-needed gap in the archives.
since the update of libvirt to 1.3.2, it seems the sd_notify support is broken, and the daemon is killed. is the daemon even running for you? On 3 March 2016 at 14:37, Jukka Salmi <j+arch@salmi.ch> wrote:
Hello
On an up-to-date Arch x86-64 system, I fail to manage VirtualBox VMs with libvirt virsh:
$ virsh -c vbox:///session error: failed to connect to the hypervisor error: internal error: unable to initialize VirtualBox driver API
Is this supposed to work out of the box?
Both VirtualBox (5.0.14-1) and libvirt (1.3.2-1) are installed from the community repository, and VirtualBox support seems to be compiled in:
$ virsh -V Virsh command line tool of libvirt 1.3.2 [...] Compiled with support for: Hypervisors: QEMU/KVM LXC UML OpenVZ VMware PHYP VirtualBox ESX Test [...]
Furthermore, both VirtualBox alone (i.e. when managed by VBoxManage or similar) and libvirt when used to manage QEMU/KVM sessions work fine.
Any hints about what I'm missing?
TIA & cheers,
Jukka
-- This email fills a much-needed gap in the archives.
-- damjan
Damjan Georgievski --> arch-general (2016-03-03 14:43:03 +0100):
since the update of libvirt to 1.3.2, it seems the sd_notify support is broken, and the daemon is killed.
is the daemon even running for you?
Hmm, this seems to be another issue, because the issue I was talking about (`virsh -c vbox:///session' failing) already existed with libvirt 1.3.1-2 (and before IIRC). But yes, I probably also see the issue you mention -- at least libvirt 1.3.2-1 behaves oddly here: at first I wasn't able to start a VM (qemu:///system), and then (with no qemu:///session VM running), virt-manager complained about Error polling connection 'qemu:///session': internal error: client socket is closed Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/engine.py", line 385, in _handle_tick_queue conn.tick_from_engine(**kwargs) File "/usr/share/virt-manager/virtManager/connection.py", line 1319, in tick_from_engine raise e # pylint: disable=raising-bad-type libvirtError: internal error: client socket is closed However, libvirtd is still running (assuming this is "the daemon" you were talking about). Cheers, Jukka
On 3 March 2016 at 14:37, Jukka Salmi <j+arch@salmi.ch> wrote:
Hello
On an up-to-date Arch x86-64 system, I fail to manage VirtualBox VMs with libvirt virsh:
$ virsh -c vbox:///session error: failed to connect to the hypervisor error: internal error: unable to initialize VirtualBox driver API
Is this supposed to work out of the box?
Both VirtualBox (5.0.14-1) and libvirt (1.3.2-1) are installed from the community repository, and VirtualBox support seems to be compiled in:
$ virsh -V Virsh command line tool of libvirt 1.3.2 [...] Compiled with support for: Hypervisors: QEMU/KVM LXC UML OpenVZ VMware PHYP VirtualBox ESX Test [...]
Furthermore, both VirtualBox alone (i.e. when managed by VBoxManage or similar) and libvirt when used to manage QEMU/KVM sessions work fine.
Any hints about what I'm missing?
TIA & cheers,
Jukka
-- This email fills a much-needed gap in the archives.
-- damjan
-- This email fills a much-needed gap in the archives.
Jukka Salmi --> arch-general (2016-03-03 16:11:01 +0100):
Damjan Georgievski --> arch-general (2016-03-03 14:43:03 +0100):
since the update of libvirt to 1.3.2, it seems the sd_notify support is broken, and the daemon is killed.
is the daemon even running for you?
Hmm, this seems to be another issue, because the issue I was talking about (`virsh -c vbox:///session' failing) already existed with libvirt 1.3.1-2 (and before IIRC).
But yes, I probably also see the issue you mention -- at least libvirt 1.3.2-1 behaves oddly here [...]
"behaves oddly" in probably the same way as describe [1]here and as reported [2]here. [1] https://bbs.archlinux.org/viewtopic.php?id=209588 [2] https://bugs.archlinux.org/task/48399 -- This email fills a much-needed gap in the archives.
participants (2)
-
Damjan Georgievski
-
Jukka Salmi