KVM module handling different per Architecture - s390x

Bug #1657733 reported by Christian Ehrhardt 
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Hi,
the Intel KVM module is build as a module, yet OTOH the s390 one is not.
I asked around and we discussed, quoting the core of the discussion that I'd like to be continued here:

<xnox> cpaelzer, we want kvm to be available. on x86 there are two modules depending on ones cpu features (amd vs intel vs whatever). thus cannot be compiled in, as either/or are loaded.
...
<xnox> infinity, the problem on s390x was that unlike on x86 nothing would autoload the module
<infinity> xnox: That sounds like a bug to take back to IBM and say "plz fix".
<xnox> and it was counter intuitive for millenials like me to do $ sudo modprobe kvm; to get libvirt+qemu working
[...]
<cpaelzer> the place to autoload would be /usr/share/qemu/init/qemu-kvm-init that is where the others do it
<infinity> cpaelzer: Yeah, that's a gross hack because there's no proper autoloading.
<cpaelzer> true
<infinity> cpaelzer: Since that init job only exists if you install qemu, modular everywhere would save a tiny bit of boot time on pure guests. So maybe it's worth evaluating
[...]
<infinity> But I'm all for kernel configs being as normalized as possible across arches.

I'm not saying we "should" change anything, but since I wondered about that arch difference more people will do so as well.
So we should consciously evaluate, do we want to:
1. keep it built-in as it is now
2. change it to a module and rely on qemu-kvm to load it
3. change it to a module and let IBM upstream do autoload where it is supported

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1657733

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Hi Brad(bot) o/,
this won't need an apport-collect so setting confirmed now.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: bot-stop-nagging kernel-da-key
Revision history for this message
Tim Gardner (timg-tpi) wrote :

Building in the KVM drivers for s390x was a direct request from IBM.

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Thanks Tim, if that was the case it is fine IMHO.

I neither need nor want to overrule them - it is good to have the bug thou as a document hopefully somebody will remember or a search engine will find next time the question comes up.

Therefore setting to Won't Fix.

Changed in linux (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Actually invalid matches the case better, so I chose that.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.