after installing a fresh debian jessie and installing virt-manager (with every
packages it depends on) VM can't start because of wrong permissions on /dev/kvm
: the group has no rw permissions on this file.

actually, this bug has been entirely described here :
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1057024

After a reboot, permissions are correctly set up, and vm can start properly.

19.09.2014 16:36, Mathieu Rohon wrote:

I need some more info about this.  I know what permissions _should_ be,
but you didn't specify which permissions do you see.  qemu-system-common
postinst script especially tries to fix wrong permissions.

I also tried to reproduce this here to no avail.

That bug says about "stray" group ACL entry which is apparently added
by udev-acl (which is part of consolekit package).  Jessie ships with
systemd by default iirc, and when systemd is used, consolekit skips
whole its udev-acl tweaking.  So it can't be the same bug.

So why you've choosen `important' severity?

Thanks,

/mjt

19.09.2014 17:30, Michael Tokarev wrote:

Even if I detest bug report(ers) who run in fire and forget mode, but I was
able to reproduce it with default jessie install.

The bug is in udev or libacl, it creates wrong ACL on /dev/kvm, which I submitted
as #762339.

Lowering severity to minor, as the issue does not affect normal operations of
the package.

Thanks,

/mjt

Sorry about that, I checked my mailbox, and I didn't receive your
first comment on this bug.

Thanks for your deep investigation.

This was the time when qemu-system-common managed permissions for
/dev/kvm node.  For a long time now, this device is managed by
default udev rules, and qemu does not touch it in any way.  So
this bug has become irrelevant.

Ubuntu added a fixup for this issue (using setfacl in postinst to
fix wrong ACL), - it too is irrelevant these days.

Closing this bug report now.

Thanks,

/mjt