On Tue, Jan 17, 2012 at 12:21:22PM +0100, Samuel Hassine, Another Service wrote:
Hi,
I tried to create a fresh container with a minimal configuration :
Here is the configuration:
http://paste.debian.net/152553/
I built a minimal rootfs with busybox as descriped in:
http://berrange.com/posts/2011/09/27/getting-started-with-lxc-using-libvirt/
And I also have the same problem:
root@PAR-SRV-01-002:/etc# virsh --connect lxc:/// start simple
error: Failed to start domain simple
error: internal error guest failed to start: 2012-01-17
11:20:35.212+0000: 13808: info : libvirt version: 0.9.8
2012-01-17 11:20:35.212+0000: 13808: warning : lxcCapsInit:77 : Failed
to get host power management capabilities
PATH=/bin:/sbin TERM=linux
LIBVIRT_LXC_UUID=3d477435-fd58-11a4-2d4e-49092034871e
LIBVIRT_LXC_NAME=simple /init
2012-01-17 11:20:35.229+0000: 1: info : libvirt version: 0.9.8
2012-01-17 11:20:35.229+0000: 1: error : lxcContainerMountDevFS:518 :
Failed to mount /dev/pts in container: No such file or directory
2012-01-17 11:20:35.229+0000: 13809: info : libvirt version: 0.9.8
2012-01-17 11:20:35.229+0000: 13809: error : lxcControllerRun:1445 :
error receiving signal from container: Input/output error
For the benefit of the mailing list archives, this turned to be caused
by the filesystem path containing a component that was an absolute
symbolic link. Debian's LXC package likes to create directories like
this for containers by default, so it is surprising we've not seen it
before. Fix proposed here
https://www.redhat.com/archives/libvir-list/2012-January/msg00660.html
Daniel
--
|:
http://berrange.com -o-
http://www.flickr.com/photos/dberrange/ :|
|:
http://libvirt.org -o-
http://virt-manager.org :|
|:
http://autobuild.org -o-
http://search.cpan.org/~danberr/ :|
|:
http://entangle-photo.org -o-
http://live.gnome.org/gtk-vnc :|