Ah! Sorry, I thought this had been fixed, but this appears to be due to bug 1236455. Using an older raring kernel should fix it for you. What
happens is qemu gets started, then libvirt updates its profile to allow
the access to the new path. The running qemu should get automatically
get the new permissions, but that's not happening.
Ah! Sorry, I thought this had been fixed, but this appears to be due to
bug 1236455. Using an older raring kernel should fix it for you. What
happens is qemu gets started, then libvirt updates its profile to allow
the access to the new path. The running qemu should get automatically
get the new permissions, but that's not happening.
duplicate: 1236455