[Bug 632696] [NEW] libvirt won't start a VM when apparmor is enabled

Serge Hallyn 632696 at bugs.launchpad.net
Tue Sep 7 22:08:42 BST 2010


Public bug reported:

I get the error:

Error starting domain: internal error Process exited while reading
console log output: chardev: opening backend "pty" failed


Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/engine.py", line 814, in run_domain
    vm.startup()
  File "/usr/share/virt-manager/virtManager/domain.py", line 1296, in startup
    self._backend.create()
  File "/usr/lib/python2.6/dist-packages/libvirt.py", line 333, in create
    if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: internal error Process exited while reading console log output: chardev: opening backend "pty" failed


Turning off apparmor fixes it.  Re-enabling it stops libvirt from creating VMs again.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: libvirt-bin 0.8.3-1ubuntu9
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Tue Sep  7 16:05:19 2010
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100820)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: libvirt

** Affects: libvirt (Ubuntu)
     Importance: High
     Assignee: Jamie Strandboge (jdstrand)
         Status: Incomplete

** Affects: libvirt (Ubuntu Maverick)
     Importance: High
     Assignee: Jamie Strandboge (jdstrand)
         Status: Incomplete


** Tags: amd64 apparmor apport-bug maverick

-- 
libvirt won't start a VM when apparmor is enabled
https://bugs.launchpad.net/bugs/632696
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.



More information about the Ubuntu-server-bugs mailing list