Libvirt lxc kills guest containers on first restart
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| libvirt (Debian) |
Fix Released
|
Unknown
|
|||
| libvirt (Ubuntu) |
Triaged
|
Low
|
Unassigned | ||
Bug Description
On the Tail end of working on https:/
Effectively on the first restart of libvirt we loose all the guests.
I reported upstream and the soon emerging http://
Yet it is so close that the goup setup might be slightly different for us, but very likely this is the root-cause.
I'm opening this bug to track this, since we need a deeper check to be done why the upstream solution doesn't work for us.
While being a bad bug in terms of really breaking stuff, prio is only medium/low as to manage containers lxd is so much better and more recommended.
| Changed in libvirt (Ubuntu): | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| Changed in libvirt (Debian): | |
| status: | Unknown → Fix Committed |
| Changed in libvirt (Debian): | |
| status: | Fix Committed → Fix Released |
| Christian Ehrhardt (paelzer) wrote | #1 |
FYI - upstream fix 44f79a0b
Author: Daniel P. Berrange <email address hidden>
lxc: ensure libvirt_lxc and qemu-nbd move into systemd machine slice
Should be fixed completely when merging libvirt >=3.0
It seems no one bothered for quite a while - so I keep low prio.
The tests that trigger that have a band-aid for now that we can retest and drop when merging the newer libvirt (probably next cycle).