Re: [PATCH] Check if systemd is the init before creating machines

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 02/28/2014 12:05 PM, Daniel P. Berrange wrote:
> On Thu, Feb 27, 2014 at 09:29:24PM +0100, Ján Tomko wrote:
>> If systemd is installed, but not the init system,
>> systemd-machined fails with an unhelpful error message:
>> Launch helper exited with unknown return code 1
>>
>> Fall back to manual cgroup creation if systemd is installed,
>> but it's not PID 1.
>>
>> [1] https://bugs.freedesktop.org/show_bug.cgi?id=69962
>> ---
> 
> Huh, that bug doesn't mention libvirt or systemd-machined
> at all ?

Sorry, I must've been writing faster than thinking.


Some libvirt users ([1][2]) have reported this error with installed but
inactive systemd, where system dbus is running and the machine1 service shows
up in ListActivatableNames output, but it's not actually usable.

Perhaps https://bugs.gentoo.org/show_bug.cgi?id=493246
would be a better bug for the commit message, but it seems to track multiple
issues and it only mentions the error in the comments.

Jan

[1] https://www.redhat.com/archives/libvirt-users/2014-January/msg00043.html
[2] https://www.redhat.com/archives/libvirt-users/2014-February/msg00128.html

Attachment: signature.asc
Description: OpenPGP digital signature

--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list

[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]