Description of problem: I have defined an LXC domain for Fedora 15, which works. However, I've defined a similar LXC domain for Exherbo Linux, created just by unpacking the tarball at http://dev.exherbo.org/stages/exherbo-x86-current.tar.xz - and this one just keeps dying immediately before I can get a console, even though I'm only specifying /bin/bash or /bin/sh as the init command to be executed. I have enabled full debug logging for libvirt but I can't see what the problem is. Version-Release number of selected component (if applicable): libvirt-0.8.3-4.fc14.i686 How reproducible: Always Steps to Reproduce: 0. Set up domain root as described above 1. virsh --connect lxc:// define exherbo.xml 2. virsh --connect lxc:// start exherbo 3. virsh --connect lxc:// list --all Actual results: Exherbo domain is shown as "shut off" Expected results: Domain should be started Additional info: kernel-PAE-2.6.35.11-83.fc14.i686 Rebooting doesn't help. Replacing /bin/bash in the domain root with Fedora's /bin/bash, or Fedora's /usr/bin/yes, doesn't seem to make any difference. Adding or removing nodes in /dev in the domain root doesn't help (they are supposed to be created by libvirt anyway). If I instead do chroot /media/temp/exherbo /bin/bash, that works. For the Fedora domain, the domain root coincides with a pre-existing mount point (the domain root is the root directory of an LVM volume). For the Exherbo domain, it's just an ordinary subdirectory. But that shouldn't matter - it's worked this way on a previous Fedora release.
Created attachment 490927 [details] config file
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
LXC support should be much better in recent fedora, so please try there. F14 is EOL anyways