[Bug 1680997] Re: Container file system corruption on libvirtd restart

2018-06-26 Thread  Christian Ehrhardt 
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

[Bug 1680997] Re: Container file system corruption on libvirtd restart

2017-05-19 Thread Eugen Rieck
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.

Re: [Bug 1680997] Re: Container file system corruption on libvirtd restart

2017-04-18 Thread Serge Hallyn
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

[Bug 1680997] Re: Container file system corruption on libvirtd restart

2017-04-18 Thread ChristianEhrhardt
[...] > 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. >

[Bug 1680997] Re: Container file system corruption on libvirtd restart

2017-04-18 Thread ChristianEhrhardt
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

[Bug 1680997] Re: Container file system corruption on libvirtd restart

2017-04-10 Thread Eugen Rieck
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

[Bug 1680997] Re: Container file system corruption on libvirtd restart

2017-04-10 Thread Serge Hallyn
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

[Bug 1680997] Re: Container file system corruption on libvirtd restart

2017-04-10 Thread Joshua Powers
** 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: