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