Unable to start lxc container after update to 2.6.32-32
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Lucid |
Fix Released
|
High
|
Tim Gardner | ||
Precise |
Fix Released
|
High
|
Unassigned | ||
vsftpd (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Lucid |
Fix Released
|
High
|
Jamie Strandboge | ||
Precise |
Fix Released
|
High
|
Unassigned |
Bug Description
Starting a container with 2.6.32-32 leads to the errors below, container will not start:
lxc-start 1306854843.605 ERROR lxc_namespace - failed to clone(0x6c020000): Invalid argument
lxc-start 1306854843.605 ERROR lxc_start - Bad file descriptor - failed to fork into a new namespace
When booting 2.6.32-31 again the container works fine.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-
Regression: Yes
Reproducible: Yes
ProcVersionSign
Uname: Linux 2.6.32-
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
dmi.sys.vendor: LENOVO
description: | updated |
tags: | added: kernel-key |
tags: | added: patch |
Changed in vsftpd (Ubuntu Lucid): | |
status: | Triaged → Fix Committed |
Changed in linux (Ubuntu Lucid): | |
assignee: | nobody → Tim Gardner (timg-tpi) |
status: | Confirmed → In Progress |
Changed in linux (Ubuntu Lucid): | |
status: | Fix Committed → Fix Released |
tags: | removed: kernel-key needs-upstream-testing |
Thanks very much for reporting this bug.
This has unfortunately been caused by the resolution to bug 788602. I'm not sure how feasible it is to do a more complete solution which fixes bug 788602 with CONFIG_NET_NS enabled, but it seems important to me to find it.
If noone else wants to tackle that, please assign this bug to me and I'll take a look.