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
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
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 wrote:
> Hello
>
> On an up-to-date Arch x86-64 system, I fail to manage VirtualBox VMs
> with libvirt virsh:
>
> $
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
4 matches
Mail list logo
