qemu upstart job should create /dev/kvm in a container
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
qemu (Ubuntu) |
Fix Released
|
High
|
Ryan Harper | ||
Trusty |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I have a host with kvm loaded and after creating a container and installing the qemu package, /dev/kvm doesn't exist. If I create it manually qemu runs fine.
The upstart job should detect that it's in a container and create /dev/kvm for use.
=======
Impact: /dev/kvm does not exist in containers after installing qemu-kvm
Test case:
sudo lxc-create -t download -n t1 -- -d ubuntu -r trusty -a amd64
sudo lxc-start -n t1 -d
sudo lxc-attach -n t1 -- apt-get update
sudo lxc-attach -n t1 -- apt-get -y install qemu-kvm
sudo lxc-attach -n t1 -- ls -l /dev/kvm
Regression potential: This can only be fixed for privileged containers on the real host, where root in the container can in fact create /dev/kvm. In that case there should be no regresison as we simply create the needed device. In the other case, package install should not fail since we do '|| true' to ignore failure.
=======
Changed in qemu (Ubuntu): | |
assignee: | nobody → Ryan Harper (raharper) |
importance: | Undecided → High |
status: | New → In Progress |
description: | updated |
tags: |
added: verification-done removed: verification-needed |
The attachment "proposed patch from Serge" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.]