Quoting Parameswaran Sivatharman (<email address hidden>):
> So I did a fresh quantal install and then (after installing kvm and
> virtual machine manager and then adding user to the libvirtd group) .
> The issue was present and when i checked getfacl /dev/kvm it had
> group:---
>
> Then after the reboot i checked getfacl again it had group:rw-
> When i tried booting the vm using the Virtual Machine manager it worked!
>
> So apparently a reboot solved the issue.
But, to be clear, on the other machine a reboot did *not* solve the
issue, right?
I have a feeling the permissions bug (which I can't yet explain)
should be a separate launchpad bug, and the original bug should
be marked invalid until it can be reproduced elsewhere.
Quoting Parameswaran Sivatharman (<email address hidden>):
> So I did a fresh quantal install and then (after installing kvm and
> virtual machine manager and then adding user to the libvirtd group) .
> The issue was present and when i checked getfacl /dev/kvm it had
> group:---
>
> Then after the reboot i checked getfacl again it had group:rw-
> When i tried booting the vm using the Virtual Machine manager it worked!
>
> So apparently a reboot solved the issue.
But, to be clear, on the other machine a reboot did *not* solve the
issue, right?
I have a feeling the permissions bug (which I can't yet explain)
should be a separate launchpad bug, and the original bug should
be marked invalid until it can be reproduced elsewhere.