Comment 14 for bug 1144873

The following are the results of from a an amd64 vm from a test which was running for more than 12 hours and still running
1) utah@utah-5695-raring-server-amd64:~$ ps -ef
   (attached as a text file)

2) utah@utah-5695-raring-server-amd64:~$ sudo lxc-ls --fancy
Cannot open network namespace: No such file or directory
Cannot open network namespace: No such file or directory
NAME STATE IPV4 IPV6 AUTOSTART
------------------------------------------
test-lucid RUNNING - - NO

3) utah@utah-5695-raring-server-amd64:~$ lxc-ps -n test-lucid -- -ef
CONTAINER UID PID PPID C STIME TTY TIME CMD

4) utah@utah-5695-raring-server-amd64:~$ dmesg | tail
[ 516.604721] lxcbr0: port 1(vethwO3MhE) entered forwarding state
[ 516.604725] lxcbr0: port 1(vethwO3MhE) entered forwarding state
[ 516.611279] lxcbr0: port 1(vethwO3MhE) entered disabled state
[ 516.611850] device vethwO3MhE left promiscuous mode
[ 516.611853] lxcbr0: port 1(vethwO3MhE) entered disabled state
[ 516.630860] init: Failed to spawn network-interface (vethwO3MhE) pre-start process: unable to change root directory: No such file or directory
[ 516.635524] init: Failed to spawn network-interface-security (network-interface/vethwO3MhE) pre-start process: unable to change root directory: No such file or directory
[ 516.637734] init: Failed to spawn network-interface (vethwO3MhE) post-stop process: unable to change root directory: No such file or directory
[ 516.649299] init: Failed to spawn network-interface-security (network-interface/vethxypKbH) pre-start process: unable to change root directory: No such file or directory
[ 516.650879] init: Failed to spawn network-interface (vethxypKbH) post-stop process: unable to change root directory: No such file or directory