FS#70174 - libvirt unable to start lxc-containters after update from 7.0.0-3 to 7.1.0-3

Attached to Project: Community Packages
Opened by Robin Rosenberger (robinrosenberger) - Friday, 26 March 2021, 11:28 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 04 May 2021, 06:34 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Robin Broda (coderobe)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

Starting a lxc via
virsh -c lxc:// start some-container
or graphical via virt-manager results in this error message:

error from service: GDBus.Error:org.freedesktop.machine1.NoMachineForPID: PID 2331 does not belong to any known machine

While shutting down systemd tries to stop a process lxc-2331-some-container until it times out.

The error appears in 7.1.0-3, a downgrade to 7.0.0-3 solves the problem

Additional info:
* package version(s)
7.1.0-3

Steps to reproduce:
- install libvirt 7.1.0-3 and lxc
- try to start a container
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Tuesday, 04 May 2021, 06:34 GMT
Reason for closing:  Fixed
Comment by loqs (loqs) - Friday, 26 March 2021, 15:14 GMT
There is a workaround in the link from [1] [2] boot with the kernel parameter systemd.unified_cgroup_hierarchy. This is the default in systemd 248rc4-1.
This is not a solution but does seem to avoid triggering the issue.

[1] https://bugs.archlinux.org/task/64789#comment198092
[2] https://bugzilla.opensuse.org/show_bug.cgi?id=1183247
Comment by Robin Rosenberger (robinrosenberger) - Friday, 26 March 2021, 17:27 GMT
The kernel parameter works, thanks a lot. So this will be solved (or not be happening anymore) with systemd 248?
P.S.: sorry if this is a duplicate, I saw the other bugreport but didn't realize its the same issue. Different version, different error message, didnt read all the comments...
Comment by Robin Rosenberger (robinrosenberger) - Saturday, 03 April 2021, 15:03 GMT
Fixed by updating to systemd 248

Loading...