[Bug 863629] Re: libvirt-lxc: virFileOpenTtyAt can't be called on /some/other/dev/pts

[Serge Hallyn]

I am going to upload libvirt to precise with this fix (which also tests
fine on my systems).  Upstream has indicated it will prefer this simpler
approach.

** Patch added: "libvirt-lxc-pty-noglibc.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/863629/+attachment/2544737/+files/libvirt-lxc-pty-noglibc.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/863629

Title:
  libvirt-lxc: virFileOpenTtyAt can't be called on /some/other/dev/pts

Status in “libvirt” package in Ubuntu:
  Fix Released

Bug description:
  lxcControllerRun() is calling virFileOpenTtyAt() with a slave opened
  on /the/container/chroot/dev/pts.  While it is not documented in the
  manpages, glibc's grantpt does a first check (ensuring that the passed
  in fd is a pty slave) with '/dev/pts' as the hardcoded path, appending
  the pty#.

  lxcControllerRun always calls this on the first slave opened after
  creating the new /dev/pts, so grantpt is always checking /dev/pts/0.
  Therefore, if your host does not have /dev/pts/0 (easy to reproduce
  using screen), then grantpt will fail, and the container creation will
  subsequently also fail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/863629/+subscriptions