*** This bug is a duplicate of bug 599450 ***
https://bugs.launchpad.net/bugs/599450
** This bug has been marked a duplicate of bug 599450
[apparmor] getattr handled incorrectly in 2.6.35-6.7
--
virt-manager cannot start VMs on lucid with v2.6.35 maverick kernel
https://bugs.launchpad.net
*** This bug is a duplicate of bug 599450 ***
https://bugs.launchpad.net/bugs/599450
looks like a dupe of #599450
--
virt-manager cannot start VMs on lucid with v2.6.35 maverick kernel
https://bugs.launchpad.net/bugs/602308
You received this bug notification because you are a member of Ubunt
Here is the tail of my audit log:
type=AVC msg=audit(1278430265.975:423): operation="getattr" pid=1369 parent=1
profile="/usr/sbin/libvirtd" name="/" pid=1369 comm="libvirtd"
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
type=SYSCALL msg=audit(1278430265.975:423): arch=c03e syscall=4 su
** Changed in: libvirt (Ubuntu)
Status: New => Confirmed
--
virt-manager cannot start VMs on lucid with v2.6.35 maverick kernel
https://bugs.launchpad.net/bugs/602308
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu
** Package changed: virt-manager (Ubuntu) => libvirt (Ubuntu)
--
virt-manager cannot start VMs on lucid with v2.6.35 maverick kernel
https://bugs.launchpad.net/bugs/602308
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
