[...] > Migrating to lxd is not feasable in many environments, in addition to that i > am totally aware > > (and not critisizing!), that libvirt-lxc was/is unsupported.
To bad as lxd really is the great way to go in this case. But I want to state that I really appreciate your understanding. > For me the real bug is, that this scenario is possible: If Ubuntu were to > just exclude > libvirt's lxc driver, that would be not really fine, but at least fool-proof. Nobody was brave enough to do so yet, but there were discussions about doing exactly that last cycle and probably in a few weeks for the next release. We had other issues which ended up in the "well but it is not meant to be supported" track, having you as a users/admin voice in that is really helpful for those discussions. > The blocker to lxd adoption is not on the admin side (me), but on the end > user side: > Virt-manager is the favorite toy for SMB/NGO local admins, typically run via > XQuartz on a > Mac or XMing on Windows. Would that in your opinion more about being a graphical clicky solution or just about being simple in general. If it would be only the latter then lxd very much simplified the semantics and can manage remote LXDs - yet I fail to see to > Please let me know, if and when I can be of further help > [...] I really think as outlined by Serge the step you really could help is filing a bug with upstream libvirt and link it here. That can be driven separate to the "do we drop lxc support" discussion. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680997 Title: Container file system corruption on libvirtd restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1680997/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
