I agree this bug is stale. Unfortunately I have lost access to the
data/system with this broken container on it, so I will be unable to
be of any assistance. Probably best to mark the but
invalid/unresolved.
On Wed, Aug 25, 2010 at 3:56 AM, Dave Walker davewal...@ubuntu.com wrote:
@David, This
Thanks, David. Hopefully we can leverage some of the lxc templating work to
make it easier to create usable libvirt-lxc containers, which would ease
testing.
Marking this invalid.
** Changed in: libvirt (Ubuntu)
Status: Incomplete = Invalid
--
virsh unable to open console
@David, This bug is starting to become stale - would you be able to
provide the additional information that Serge has requested?
Thanks :)
--
virsh unable to open console
https://bugs.launchpad.net/bugs/594836
You received this bug notification because you are a member of Ubuntu
Server Team,
Hi,
thanks for filing this bug.
Can you tell me how you populated /lxc/rootfs.dbryson ? Did you
do a debootstrap, manually populate it with busybox, or some other
way?
Is /dev/ptmx on the host a device, or a link to /dev/pts/ptmx?
--
virsh unable to open console
** Changed in: libvirt (Ubuntu)
Status: New = Incomplete
--
virsh unable to open console
https://bugs.launchpad.net/bugs/594836
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
Ubuntu-server-bugs mailing list
I installed a fresh lucid VM under kvm, installed libvirt-bin,
then took your xml file, replaced /sbin/init with /bin/init.
I created /lxc/rootfs.dbryson, and did
cd /lxc/rootfs.dbryson
mkdir bin
cd bin
cp /bin/busybox .
ln busybox init
ln busybox sh
