This bug was fixed in the package lxc - 0.7.4-0ubuntu7.1
---
lxc (0.7.4-0ubuntu7.1) natty-proposed; urgency=low
[ Serge Hallyn ]
* debian/patches/0009-templates-dont-use-devpts-in-fstab: remove devpts
entry from $confdir/container/fstab, as it is not needed, and can
cause
Accepted lxc into natty-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Tags added: verification-needed
--
You
** Branch linked: lp:ubuntu/natty-proposed/lxc
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/607636
Title:
chardev: opening backend pty failed
--
Ubuntu-server-bugs mailing list
Hi!
I just installed the proposed package and it seems to work (I created a
lucid container). Starting kvm domains (with virsh start) after the lxc
container, works too.
Thank you!
$ dpkg -l | grep lxc
ii lxc 0.7.4-0ubuntu7.1
** Tags added: verification-done
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/607636
Title:
chardev: opening backend pty failed
--
** Also affects: libvirt (Ubuntu Natty)
Importance: Undecided
Status: New
** Also affects: lxc (Ubuntu Natty)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu Natty)
Status: New = Invalid
** Changed in: lxc (Ubuntu Natty)
Status: New = Triaged
** Attachment added: Here is the trivial debdiff to fix. I want to test a bit
but will push later today.
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/607636/+attachment/2116896/+files/debdiff
** Changed in: lxc (Ubuntu)
Status: Triaged = In Progress
--
You received this
This bug was fixed in the package lxc - 0.7.4-0ubuntu8
---
lxc (0.7.4-0ubuntu8) oneiric; urgency=low
* debian/patches/0009-templates-dont-use-devpts-in-fstab: remove devpts
entry from $confdir/container/fstab, as it is not needed, and can
cause the host devpts mount options
** Changed in: lxc (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
https://bugs.launchpad.net/bugs/607636
Title:
chardev: opening backend pty failed
--
Ubuntu-server-bugs
Hello,
I had qemu-kvm working flawless and then I installed lxc.
I can reproduce this bug *always* in maverick doing this:
start lxc domain
start kvm guest
$ virsh start kvm-windsurf
chardev: opening backend pty failed
Does it work if you remount the directory?
$ sudo mount -o remount
What's the status of your apparmor? Do you have it active?
I'm not certain it was the mount options on /dev/pts that was the
problem, but it could be.
Does it work if you remount the directory?
--
chardev: opening backend pty failed
https://bugs.launchpad.net/bugs/607636
You received this bug
I hit the same problem after installing and trying to use lxc. It was
previously working properly on the same host machine. Could it be that
lxc changes the mount options on the host's /dev/pts? (I'm not sure
that was precisely the cause though.)
** Also affects: lxc (Ubuntu)
Importance:
Problem solved, I think.
/dev/pts was wrongly mounted as:
none on /dev/pts type devpts (rw,mode=620,mode=620)
... when it should be:
none on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
This could now be an initramfs issue - I installed dropbear recently and
it starts up udev and
I'm not sure where the bug is. If you can determine what file caused it
to be mounted this way, you can use 'dpkg -S file' to determine what
package did this. Marking Invalid for now. Feel free to reopen and
change to the package causing the error when you determine the cause.
** Changed in:
14 matches
Mail list logo
