kvm modules not autoloaded on ppc64el
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | qemu (Ubuntu) |
High
|
Unassigned | ||
| | Trusty |
High
|
Jorge Niedbalski | ||
Bug Description
[Impact]
on ppc64el, the kvm modules are not autoloaded. The qemu-system-x86 package contains an init script that loads the kvm modules for the platform, but there is no corresponding init script for ppc64el, where the kvm-hv module needs to be loaded.
[Test Case]
Install qemu, reboot and ensure kvm-hv module is loaded.
[Regression Potential]
This adjusts the upstart scripts to do what a user would have to normally do manually.
| Serge Hallyn (serge-hallyn) wrote : | #1 |
| Changed in qemu (Ubuntu): | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
On Tue, Sep 16, 2014 at 02:43:08PM -0000, Serge Hallyn wrote:
> Seems like the best thing would be to move qemu-system-
> kvm.upstart to qemu-system-
> .default and .init) and have the jobs check for the right architectures.
Note that currently qemu-system-x86 ships an init script named
qemu-system-x86 and an upstart job named qemu-kvm. These need to be made
consistent. On Ubuntu, we're currently running *both* of them at boot time.
I'm not convinced that it's better to name it qemu-kvm and put it in a
common package, than to have each native arch-specific package to ship its
own. These startup scripts are dead weight on other architectures, better
to optimize them out at package build time.
| Changed in qemu (Ubuntu): | |
| importance: | Medium → High |
| Serge Hallyn (serge-hallyn) wrote : | #3 |
We can become more clever about the packaging later, but this proposed debdiff should
1. clean up the old qemu-system-x86 sysvinit job
2. install a qemu-kvm upstart job on ppcc64le
| tags: | added: patch |
| Launchpad Janitor (janitor) wrote : | #4 |
This bug was fixed in the package qemu - 2.1+dfsg-4ubuntu4
---------------
qemu (2.1+dfsg-4ubuntu4) utopic; urgency=medium
* debian/
container. (LP: #1370199)
* load kvm module on ppc64le at boot (LP: #1369785)
- debian/rules: install qemu-kvm on ppc64el
- add debian/
kvm-hv module if available
* qemu-system-
/etc/
* rename qemu-system-x86 init script to qemu-kvm so it gets installed in
ubuntu.
-- Serge Hallyn <email address hidden> Wed, 17 Sep 2014 14:20:12 -0500
| Changed in qemu (Ubuntu): | |
| status: | Triaged → Fix Released |
| description: | updated |
| Changed in qemu (Ubuntu Utopic): | |
| status: | New → Won't Fix |
| Launchpad Janitor (janitor) wrote : | #5 |
Status changed to 'Confirmed' because the bug affects multiple users.
| Changed in qemu (Ubuntu Trusty): | |
| status: | New → Confirmed |
| Changed in qemu (Ubuntu Trusty): | |
| importance: | Undecided → High |
| assignee: | nobody → Jorge Niedbalski (niedbalski) |
| no longer affects: | qemu (Ubuntu Utopic) |
| ChristianEhrhardt (paelzer) wrote : | #6 |
Hi Jorge,
I saw you updating this long dormant issue, also I saw smoser updating a dup to this on the same day. I assume there was something triggering this.
Please do mind that all the fixes that were made >=Utopic only are for the kvm-hv module.
It seems that second level kvm-pr based virtualization is always a bit "less encouraged" and for that no auto-loading is in place. This was before my time, but in some sense that serves a bit as a "please do know what you do" barrier and could be ok.
That said, are you working on backporting and preparing the fix for Trusty (since you assigned yourself)?
| ChristianEhrhardt (paelzer) wrote : | #7 |
Closing this old issue as it seems to be neither important nor active.
The kvm_hv is working and that is what people should use anyway.
I think it is ok'ish to need the extra step if you are in the unsupported second level virtualization.
| Changed in qemu (Ubuntu Trusty): | |
| status: | Confirmed → Won't Fix |


Seems like the best thing would be to move qemu-system- x86.qemu- kvm.upstart to qemu-system- common. qemu-kvm. upstart (and same with .default and .init) and have the jobs check for the right architectures.