Comment 0 for bug 843892

On linux-image-2.6.38-11-generic, destroying a container causes a kernel OOPS and an immediate reboot. This is totally repeatable. This is on XUbuntu (but I doubt that makes any difference as we've done it on a headless Ubuntu server too).

Procedure to repeat:
  lxc-create -n foo
  lxc-start -n foo
Press ^C

This happens with containers created otherwise than using lxc, so it is not a bug in lxc.

The oops is in general not possible to catch as the reboot is immediate. However, I have attached an Oops from a marginally different kernel (2.6.38-10-server on Lucid) which is created in a different way, but Oopses at the same time and I believe is the same bug.

Bug information as required

1. System information.

lsb_release -rd gives:

Description: Ubuntu 11.04
Release: 11.04

2. apt-cache policy linux-image-2.6.38-11-generic

linux-image-2.6.38-11-generic:
 Installed: 2.6.38-11.49
 Candidate: 2.6.38-11.49
 Version table:
*** 2.6.38-11.49 0
       500 http://gb.archive.ubuntu.com/ubuntu/ natty-proposed/main amd64 Packages
       100 /var/lib/dpkg/status
    2.6.38-11.48 0
       500 http://gb.archive.ubuntu.com/ubuntu/ natty-updates/main amd64 Packages
       500 http://security.ubuntu.com/ubuntu/ natty-security/main amd64 Packages

3) What I expected to happen:

Container deleted, command prompt returns.

4) What actually happened:

Immediate machine reboot, all data lost

5) We currently do not believe this to be a security vulnerability as containers cannot be created as non-root.