It looks like the bug still exists in 'trusty', qemu-kvm 2.0, however,
it's not clear why.
Aftre installation /dev/kvm have wrong permissions:
---
crw--- 1 root root 10, 232 Jan 20 02:09 /dev/kvm
---
Reinstalling qemu-system-common fixes the problem.
I did a simple research, and here is
Hi Dmitry,
it sounds like you're saying there is a new bug (regression). Could
you open a new bug with the relevant information? Thanks!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
This bug was fixed in the package qemu-kvm - 1.2.0+noroms-
0ubuntu2.12.10.5
---
qemu-kvm (1.2.0+noroms-0ubuntu2.12.10.5) quantal-proposed; urgency=low
* debian/control and qemu-kvm.postinst: remove any g:--- acl on /dev/kvm
(left over from udev-acl). (LP: #1057024)
-- Serge
This bug was fixed in the package qemu-kvm - 1.0+noroms-0ubuntu14.11
---
qemu-kvm (1.0+noroms-0ubuntu14.11) precise-proposed; urgency=low
* debian/control and qemu-kvm.postinst: remove any g:--- acl on /dev/kvm
(left over from udev-acl). (LP: #1057024)
-- Serge Hallyn
Quantal verification passed with the 1.2.0+noroms-0ubuntu2.12.10.5 .
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1057024
Title:
kvm kernel module always loaded, without setting
Precise verification also passed with the version 1.0+noroms-
0ubuntu14.11 .
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
Hello Parameswaran, or anyone else affected,
Accepted qemu-kvm into quantal-proposed. The package will build now and
be available at http://launchpad.net/ubuntu/+source/qemu-kvm/1.2.0
+noroms-0ubuntu2.12.10.5 in a few hours, and then in the -proposed
repository.
Please help us by testing this
Pushed proposed packages for precise and quantal.
** Changed in: qemu-kvm (Ubuntu Precise)
Status: Triaged = In Progress
** Changed in: qemu-kvm (Ubuntu Quantal)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team,
After a reboot, I see the following:
: linux13 1#; getfacl /dev/kvm
getfacl: Removing leading '/' from absolute path names
# file: dev/kvm
# owner: root
# group: kvm
user::rw-
user:daly:rw-
group::rw-
mask::rw-
other::---
If I understood the thread correctly, these permissions should have been
I'm seeing this bug just after installing the following on a new 12.04
(64bit) install... I have not rebooted my system...
: linux13 24#; dpkg-query -W qemu-kvm
qemu-kvm1.0+noroms-0ubuntu14.8
: linux13 25#; getfacl /dev/kvm
getfacl: Removing leading '/' from absolute path names
# file:
Thanks, Ryan.
Indeed - there were several problems affecting /dev/kvm after a fresh
install, and while raring got all the fixes, precise and quantal did not
get one (presumably because I did not think they were affected).
We will need to do the following in both precise and quantal:
1. add acl
Sure thing. Thanks for your support.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1057024
Title:
kvm kernel module always loaded, without setting /dev/kvm permissions
To
This bug was fixed in the package qemu-kvm - 1.2.0+noroms-
0ubuntu2.12.10.1
---
qemu-kvm (1.2.0+noroms-0ubuntu2.12.10.1) quantal-proposed; urgency=low
[ Serge Hallyn ]
* debian/qemu-kvm.postinst: use udevadm trigger to change /dev/kvm perms as
recommended by Steve Langasek
This bug was fixed in the package qemu-kvm - 1.0+noroms-0ubuntu14.6
---
qemu-kvm (1.0+noroms-0ubuntu14.6) precise-proposed; urgency=low
* Fix qemu-kvm.upstart: just don't run in a container. Otherwise we'll
still try to load/unload kernel modules. Also undo the || true after
Hello Parameswaran, or anyone else affected,
Accepted qemu-kvm into precise-proposed. The package will build now and
be available at http://launchpad.net/ubuntu/+source/qemu-kvm/1.0+noroms-
0ubuntu14.6 in a few hours, and then in the -proposed repository.
Please help us by testing this new
Re-verified.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1057024
Title:
kvm kernel module always loaded,
The fix in quantal-proposed is currently complicated by a udev bug
#1092715. The udev trigger from the postinst doesn't seem to pick up
the new rules file in /lib/udev/rules.d, and permissions are not updated
by the trigger.
--
You received this bug notification because you are a member of
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1057024
Title:
kvm kernel module always loaded, without
(Re-verified in precise)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1057024
Title:
kvm kernel module always loaded, without setting /dev/kvm permissions
To manage
Hello Parameswaran, or anyone else affected,
Accepted qemu-kvm into precise-proposed. The package will build now and
be available at http://launchpad.net/ubuntu/+source/qemu-kvm/1.0+noroms-
0ubuntu14.5 in a few hours, and then in the -proposed repository.
Please help us by testing this new
I just upgraded a server from 11.10 to 12.04 and I got a gnome-keyring
error [1] when trying to start a guest. There is some other bug about
it and strangely a workaround was to install the 'gnome-keyring'
package. I did so in haste and the majority of the error remains, even
after upgrading
After loading the module I was able to start my guest:
$ sudo modprobe kvm_intel
The main question is why this did not occur automatically after
rebooting (after I upgraded to the -proposed version of qemu-kvm)?
Note that everything worked very well on 11.10.
--
You received this bug
@Peter,
could you please open a new bug for your issue?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1057024
Title:
kvm kernel module always loaded, without setting /dev/kvm
Failure to start kvm can also be caused by VirtualBox running on the
host - watch out for dmesg like:
kvm: enabling virtualization on CPU3 failed
kvm: enabling virtualization on CPU0 failed
kvm: enabling virtualization on CPU2 failed
kvm: enabling virtualization on CPU1 failed
to fix it:
#
Tested for verification on a 20121016 (12.04.1) install fully updated
amd64 system.
The original bug could not be reproduced in this. With the version 1.0
+noroms-0ubuntu14.3 the following is the output of getfacl /dev/kvm
getfacl: Removing leading '/' from absolute path names
# file: dev/kvm
#
** Changed in: qemu-kvm (Ubuntu Quantal)
Status: Triaged = In Progress
** Changed in: qemu-kvm (Ubuntu Precise)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
Hello Parameswaran, or anyone else affected,
Accepted qemu-kvm into precise-proposed. The package will build now and
be available at http://launchpad.net/ubuntu/+source/qemu-kvm/1.0+noroms-
0ubuntu14.4 in a few hours, and then in the -proposed repository.
Please help us by testing this new
** Changed in: qemu-kvm (Ubuntu Raring)
Assignee: (unassigned) = Serge Hallyn (serge-hallyn)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1057024
Title:
kvm kernel module
The change that's been uploaded to precise for this is:
diff -u qemu-kvm-1.0+noroms/debian/qemu-kvm.postinst
qemu-kvm-1.0+noroms/debian/qemu-kvm.postinst
--- qemu-kvm-1.0+noroms/debian/qemu-kvm.postinst
+++ qemu-kvm-1.0+noroms/debian/qemu-kvm.postinst
@@ -16,2 +16,15 @@
-exit 0
+# if we just
** Tags removed: rls-q-incoming
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1057024
Title:
kvm kernel module always loaded, without setting /dev/kvm permissions
To manage
Thanks for bringing the laptop.
We took a look. After installing qemu-kvm and libvirt (and virt-
manager) /dev/kvm has the right permissions and ownership. User ubuntu
is able to run kvm. However when doing
sudo -u libvirt-qemu strace -f -o/tmp/outout kvm -vnc :1
you see that when it
At last, the cause is found. /lib/udev/rules.d/70-udev-acl.rules adds
an acl to /dev/kvm denying group write perms. (qemu-kvm installs its
own /lib/udev/rules.d/40-qemu-kvm.rules when qemu-kvm is installed) The
qemu-kvm.postinst does chgrp and chmod /dev/kvm, but chmod g+rw does
not remove the
** Description changed:
+ =
+ SRU Justification:
+ 1. Impact: libvirt cannot start VMs immediately after qemu-kvm install.
+ 2. Development fix: remove the acl which is preventing libvirt-qemu from
opening /dev/kvm.
+ 3. Stable fix: same as development fix
+ 4.
This bug was fixed in the package qemu-kvm - 1.2.0+noroms-0ubuntu3
---
qemu-kvm (1.2.0+noroms-0ubuntu3) raring; urgency=low
* debian/qemu-kvm.postinst: remove the g::--- acl which udev may have
inserted. (LP: #1057024)
-- Serge Hallyn serge.hal...@ubuntu.com Thu, 01 Nov 2012
Root cause found: udev automatically loads kvm_intel even when qemu-kvm
is not installed. The kvm group and udev file causing /dev/kvm to be
chgrp'd to kvm and set its permissions are installed by qemu-kvm.
If it were only a question of permissions I'd say the udev package
should be setting
No, I was looking in the wrong place - qemu-kvm.postinst already does
exactly that!
In fact, I'm starting to wonder whether the way to reproduce this would
be to not 'apt-get install kvm' before installing libvirt-bin. The kvm
kernel module will be loaded, but won't be configured for use by
If kvm is not configured, then virt-manager tells me at the first 'New
virtual machine screen that:
Error: No hypervisor options were found for this connection.
This usually means that QEMU or KVM is not installed on your machine, or the
KVM kernel modules are not loaded.
So I simply cannot
@Serge,
I will be at the UDS and Ill bring the machine there.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1057024
Title:
kvm kernel module always loaded, without setting
38 matches
Mail list logo
