Bug#766233: LXC breakage and workarounds when upgrading VMs to jessie

[Antonio Terceiro]

On Mon, Nov 24, 2014 at 07:48:28AM +0100, Tomas Pospisek wrote:
> On Mon, 24 Nov 2014, Marco d'Itri wrote:
> 
> >On Nov 24, Tomas Pospisek <tpo_deb at sourcepole.ch> wrote:
> >
> >>My first proposed text for the release-notes is below. Please let me
> >>know if you prefer me to submit a proper patch against a SVN checkout of
> >>ddp.
> >
> >Please also clarify that LXC containers *can* use systemd with no
> >troubles if correctly configured.
> 
> Could you please clarify what needs to be done to correctly configure a LXC
> container?

This:
https://lists.linuxcontainers.org/pipermail/lxc-devel/2014-November/010900.html

I am interacting with Daniel (Debian maintainer) to also get that into
jessie.

> * Is it sufficient to set: "lxc.autodev = 1" in /var/lib/lxc/myvm/config?

Definitively not.

> * Does an upgrade also automatically switch to journald?
> 
>   * In which case one *must* also set "lxc.kmsg=0" in
>     "/var/lib/lxc/myvm/config" and remove "/dev/kmsg" inside the VM?
> 
> * Is it possible to switch a system configured in such a way back and
>   forth between systemd and sysvinit without having to change anything
>   but the package selection? Or does that imply removing the configuration
>   changes, i.e. removing "lxc.autodev = 1" and "lxc.kmsg=0" and recreating
>   /dev/kmsg?
> 
> * Is it possible to run the upgraded VM, that is correctly configured as
>   you suggest on a normal wheezy host? Does the wheezy host need any
>   special configuration?

I don't have answers for these questions yet.

-- 
Antonio Terceiro <terceiro at debian.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20141124/9a075e61/attachment-0002.sig>