Public bug reported:

Binary package hint: lxc

r...@vmserver:/# lsb_release -rd
Description:    Ubuntu 10.04.1 LTS
Release:    10.04

I have a problem starting LXC Containers on an AMD64 Lucid installation.
This issue appears very similar to bug #566827 though  my conditions are
not as described in that bug. I have a single debian container that had
been running flawlessly for some weeks. The container was started and
stopped a number of times and always started successfully. My /var is
not a separately mounted file system. Following an unplanned power off
of the system (I have spoken to the wife and this will not happen again)
I now get the following as reported in #566827.

lxc-start: Device or resource busy - could not unmount old rootfs
lxc-start: failed to pivot_root to '/home/rpcarter/lxc/MusicServ01/rootfs'
lxc-start: failed to set rootfs for 'MusicServ01'
lxc-start: failed to setup the container 

I have made no changes to the system but automatic updates would have
occurred.  I have destroyed and recreated the container and also build a
new one with lxc-debian from scratch but this error is consistently
there.

If the solution is as described in #566827 and little more clarity on
how this is applied would be appreciated.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: lxc 0.6.5-1
ProcVersionSignature: Ubuntu 2.6.32-25.44-server 2.6.32.21+drm33.7
Uname: Linux 2.6.32-25-server x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Mon Oct  4 14:22:45 2010
InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 
(20100427)
ProcEnviron:
 LANG=en_GB.utf8
 SHELL=/bin/bash
SourcePackage: lxc

** Affects: lxc (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug lucid

-- 
Unable to start LXC Container
https://bugs.launchpad.net/bugs/654552
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to