Jamie,

sorry, I thought his latest comment mentioned that as a working
workaround, but I must have seen it in the description.

So yes, removing the tag seems good.

** Description changed:

  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)
+   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.
+ It was originally thought that turning off apparmor fixes it, and re-
+ enabling apparmor stops libvirt from creating VMs again.  Later reports
+ claim this is not the case.
  
  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
+  PATH=(custom, user)
+  LANG=en_US.utf8
+  SHELL=/bin/bash
  SourcePackage: libvirt

** Summary changed:

- libvirt won't start a VM with serial or console when apparmor is enabled
+ libvirt won't start a VM with serial or console

-- 
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/632696

Title:
  libvirt won't start a VM with serial or console

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

Reply via email to