Bug#890892: lxc: Fail to create and run CentOS 6 container with kernel >= 4.11 due to segfaults

[Salvatore Bonaccorso <carnil@debian.org>]

Hi Chris,

On Wed, Apr 24, 2019 at 12:31:02PM +0200, Chris Hofstaedtler wrote:
> Control: reassign -1 linux-image-amd64
> Control: affects -1 lxc
> 
> * Andrii Senkovych <andrii@senkovych.com> [190424 10:23]:
> [..]
> [Centos6 binaries crash on Linux 4.11+]
> [..]
> > Adding "vsyscall=emulate" to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub
> > and restarting host resolves the issue.
> > 
> [..]
> > 
> > https://github.com/docker/for-linux/issues/58#issuecomment-315133361
> 
> The only thing to be done here about this is a release notes entry;
> this could come from either the linux or lxc teams.
> 
> Still reassigning to (probably the wrong) linux-image-* package, as
> lxc didn't do anything here.

This is already documented in
/usr/share/doc/linux-image-amd64/NEWS.Debian.gz:

linux-latest (81) unstable; urgency=medium

  * From Linux 4.10, the old 'virtual syscall' interface on 64-bit PCs
    (amd64) is disabled.  This breaks chroot environments and containers
    that use (e)glibc 2.13 and earlier, including those based on Debian 7
    or RHEL/CentOS 6.  To re-enable it, set the kernel parameter:
    vsyscall=emulate

 -- Ben Hutchings <ben@decadent.org.uk>  Fri, 30 Jun 2017 23:50:03 +0100

Not sure if it would be worth of an additional entry in for instances
issues.dbk of the release-notes though (maybe yes).

Regards,
Salvatore