Bug#770776: release-notes: Bug#770776: LXC breakage and workarounds when upgrading VMs to jessie
Control: tags -1 pending
On 2014-12-30 16:59, Tomas Pospisek wrote:
> On Sun, 7 Dec 2014, Adam D. Barratt wrote:
>
> [...]
>
> So please check, if required criticise and please apply the patch.
>
Applied with modifications (please see attached patch). The summary:
* Some minor wording changes / sentence movements.
* Move section to issues rather than upgrading
* (More) Cross-linking between LXC section and systemd migration
section.
* Add a note that the LXC section does *not* apply to "normal"
end-user systems.
> 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!!
>
Same to you and you are welcome :)
> 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!
Ok, will follow up.
~Niels
>From 8c90bfcdccee633689895828084637cf5cb2e682 Mon Sep 17 00:00:00 2001
From: nthykier <nthykier@313b444b-1b9f-4f58-a734-7bb04f332e8d>
Date: Thu, 1 Jan 2015 12:20:39 +0000
Subject: [PATCH] en/issues: Document LXC migration issues
Amendments by nthykier:
* Some minor wording changes / sentence movements.
* Move section to issues rather than upgrading
* (More) Cross-linking between LXC section and systemd migration
section.
* Add a note that the LXC section does *not* apply to "normal"
end-user systems.
Signed-off-by: Niels Thykier <niels@thykier.net>
git-svn-id: svn+ssh://svn.debian.org/svn/ddp/manuals/trunk/release-notes@10573 313b444b-1b9f-4f58-a734-7bb04f332e8d
---
en/issues.dbk | 83 +++++++++++++++++++++++++++++++++++++++++++++++++++++++----
1 file changed, 78 insertions(+), 5 deletions(-)
diff --git a/en/issues.dbk b/en/issues.dbk
index b9dcf29..fd35ba7 100644
--- a/en/issues.dbk
+++ b/en/issues.dbk
@@ -210,11 +210,15 @@ $ echo 'openssh-server openssh-server/permit-root-login boolean true' | debconf-
preference for another init such as <systemitem
role="package">sysvinit-core</systemitem> or <systemitem
role="package">upstart</systemitem>, it is recommended to setup
- APT pinning prior to the upgrade. As an example, to prevent
- <systemitem role="package">systemd</systemitem> from being
- installed during the upgrade, you can create a file called
- <filename>/etc/apt/preferences.d/local-pin-init</filename> with
- the following contents:
+ APT pinning prior to the upgrade. This may also be required if
+ you are upgrading LXC containers before the host. In this case,
+ please refer to <xref linkend="issues-lxc-wheezy-host" />
+ </para>
+ <para>As an example, to prevent <systemitem
+ role="package">systemd</systemitem> from being installed during the
+ upgrade, you can create a file called
+ <filename>/etc/apt/preferences.d/local-pin-init</filename> with the
+ following contents:
</para>
<screen>
Package: systemd-sysv
@@ -300,6 +304,75 @@ ProtectSystem=yes
</para>
</section>
+<section id="issues-lxc">
+<!-- Wheezy to Jessie -->
+<title>Upgrade considerations for LXC hosts and containers</title>
+
+<note>
+ <para>
+ This section only applies to systems that has LXC containers and
+ hosts. Normal end user systems usually do not have these.
+ </para>
+</note>
+<para>
+The upgrade from wheezy to jessie will migrate your system to the
+systemd init system by default (see <xref
+linkend="systemd-upgrade-default-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 already
+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. You
+ prevent the migration via pinning, as described in <xref
+ linkend="systemd-upgrade-default-init-system" />.
+</para>
+<para>
+ This is required as the Wheezy host lacks functionality to boot a
+ system running systemd.
+</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. The container configuration
+ can usually be found in
+ <filename>/var/lib/lxc/<replaceable>CONTAINER_NAME</replaceable>/config</filename>
+ You need to add the following two settings 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 id="cryptsetup-luks-whirlpool">
<!-- Wheezy to Jessie -->
--
2.1.4
Reply to: