[Bug 1680997] Re: Container file system corruption on libvirtd restart
Closed by upstream for insufficient data :-/ Setting incomplete here as well ** Changed in: libvirt (Ubuntu) Status: Triaged => Incomplete -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680997] Re: Container file system corruption on libvirtd restart
Upstream bug report is at https://bugzilla.redhat.com/show_bug.cgi?id=1452701 ** Bug watch added: Red Hat Bugzilla #1452701 https://bugzilla.redhat.com/show_bug.cgi?id=1452701 -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1680997] Re: Container file system corruption on libvirtd restart
Note, the last I heard it was not deprecated by *upstream*, but by redhat. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680997] Re: Container file system corruption on libvirtd restart
[...] > 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680997] Re: Container file system corruption on libvirtd restart
Yet given that upstream deprecated it even their interest might diminish :-/ -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680997] Re: Container file system corruption on libvirtd restart
The steps outlined in the initial bug report reliably (100%) reproduce the problem for me on Ubuntu 16.04, it is tested in different Environments (1xAMD, ca. 10xIntel). Here's the short way to get there: - Install a basic Ubuntu 16.04 Server - apt-get install virt-manager (installing the GUI pulls in the heavy lifting components) - create a libvirt/lxc container of something like AnyName 2097152 2097152 4 /machine exe /sbin/init destroy restart restart /dev/net/tun (I have experimented quite a lot, and it boils down to the loop-mounted file system) - Start the container via virsh or virt-manager - Restart libvirtd - Examine state of the container in virsh or virt-manager vs. the state of the loop device via losetup The important parts are: - The container is shown as stopped - The container dosen't reply to network requests or console connection requests (i.e. it seems truly dead) - The loop device doesn't show up in host-side "mount | grep loop" - libvirtd allows to (re-)start the container, ending up with a double- mounted file system 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. 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. 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. Please let me know, if and when I can be of further help - I am willing to test and have quite a few testbeds at hand, where I can easily create throw-away containers and ruin them. Since I tripped over this, I migrated around to have one node running no containers at every single customer, just to do exactly that. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680997] Re: Container file system corruption on libvirtd restart
Hi, this would be deemed a high priority bug for upstream libvirt, but Ubuntu has always, back to 2010, supported lxc, then lxd, instead of libvirt-lxc. (So it's not that libvirt-lxc is deprecated, rather it was never supported in Ubuntu) Which version of Ubuntu are you using? Can you reliably reproduce it? If you can give a recipe for "start with a clean ubuntu cloud VM image; set up a container "like this", do that, then it dies", then we may be able to nail down the cause and/or talk to upstream. If at all possible to migrate you to using lxd containers, that would be ideal, but I assume you have control software written around libvirt's api making that untenable. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680997] Re: Container file system corruption on libvirtd restart
** Changed in: libvirt (Ubuntu) Status: New => Triaged ** Changed in: libvirt (Ubuntu) Importance: Undecided => High -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
