Bug#770776: release-notes: Bug#770776: LXC breakage and workarounds when upgrading VMs to jessie
On Sun, 7 Dec 2014, Adam D. Barratt wrote:
Is this still relevant after the upload of lxc 1.0.6-5?
Yes, it still is. There are still manual steps needed during upgrade.
Attached you'll find my second try at a patch to the release notes.
If my suggested addition is acceptable and not too far off the mark, then
I suggest to apply it *now*. Changes and improvements can be incorporated
into the patched release-notes. The reason is, that it took me one month
to come back to this issue and I don't know when I'll have the next
opportunity to work on this. And I'd rather have the problem documented in
the interest of the users.
That said, please do criticise, if there's something to improve.
So please check, if required criticise and please apply the patch.
Thanks you all for contributing and considering and have a wonderful 2015!
*t
PS: Many thanks to Niels and Holger for their kind and supportive words!
This patch is dedicated to you guys!!
PPS: Adam and Niels and Daniel, could you please have a look at #774204.
If you don't object Daniel, I'd propose to NMU that and ask you
release team to have it included in jessie. Please follow up in
#774204!diff --git en/upgrading.dbk en/upgrading.dbk
index 13b1a30..f7dc09c 100644
--- en/upgrading.dbk
+++ en/upgrading.dbk
@@ -1136,6 +1136,79 @@ entries. You should use <command>visudo</command> for this:
</screen>
</section>
+<section id="issues-lxc">
+<title>LXC</title>
+
+<para>
+The upgrade from wheezy to jessie will migrate your system to
+the systemd init system.
+</para>
+<para>
+When upgrading a LXC container, respectively a LXC virtual
+machine, this will have different consequences depending on
+whether the <emphasis>host system</emphasis> has allready
+been upgraded to jessie or not.
+</para>
+
+<section id="issues-lxc-wheezy-host">
+<title>Upgrading LXC guests running on wheezy hosts</title>
+
+<para>
+If you are upgrading a LXC guest container that is running on a
+<emphasis>wheezy host</emphasis> system, then you will need to
+prevent the guest from being automatically migrated to systemd.
+</para>
+<para>
+If you don't prevent the system from migrating to systemd, then
+you will risk, that your guest system will not be able to boot.
+</para>
+<para>
+This is due to functionality missing in wheezy hosts, that are
+required to boot a jessie system with systemd.
+</para>
+<para>
+You prevent the migration via pinning, as described in chapter
+<xref linked="#systemd-upgrade-default-init-system"/>.
+</para>
+<para>
+You should be able to switch over to systemd inside the LXC guest
+once you have upgraded the <emphasis>host</emphasis> system to jessie. See the next
+paragraph for things that need to be adapted on jessie hosts.
+</para>
+</section>
+
+<section id="issues-lxc-jessie-host">
+<title>Upgrading LXC guests running on jessie hosts</title>
+
+<para>
+In order to be able to boot LXC guests with systemd, you need
+to adapt your LXC container configuration.
+</para>
+<para>
+The container configuration can usually be found in
+</para>
+<screen>
+/var/lib/lxc/<replaceable>CONTAINER_NAME</replaceable>/config
+</screen>
+<para>
+You need to add the following two setting to the configuration:
+</para>
+<screen>
+lxc.autodev = 1
+lxc.kmsg = 0
+</screen>
+</section>
+
+<section id="issues-lxc-further-docu">
+<title>Further information</title>
+<para>
+You can find further information on LXC in Debian
+<ulink url="&url-wiki;LXC">in the Debian wiki</ulink>.
+</para>
+</section>
+
+</section>
+
</section>
<!-- End of 'trouble' section -->
</section>
Reply to: