nested=1 not taking effect

Bug #1155177 reported by Serge Hallyn
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
qemu (Ubuntu)
Fix Released
High
Serge Hallyn

Bug Description

Because kvm_intel is being auto-loaded early on, then KVM_NESTED argument in /etc/init/qemu-kvm is being ignored.

Perhaps we should always install a /etc/modprobe.d/qemu-kvm.conf file which has

options kvm_intel nested=1

Related branches

Changed in qemu (Ubuntu):
status: New → Confirmed
importance: Undecided → High
Changed in qemu (Ubuntu):
assignee: nobody → Serge Hallyn (serge-hallyn)
Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

Turns out this is actually a regression from quantal, where we installed a /etc/modprobe.d file to set the nested option. Testing a fix now.

Changed in qemu (Ubuntu):
status: Confirmed → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package qemu - 1.4.0+dfsg-1expubuntu4

---------------
qemu (1.4.0+dfsg-1expubuntu4) raring; urgency=low

  * re-add qemu-system-x86.modprobe to set nesting=1 (LP: #1155177)
  * qemu-system-x86.qemu-kvm.upstart:
    - remove NESTED workarounds from upstart file.
    - remove loading of modules which is now always done
    - remove TAPR define which is no longer used
  * move customizable defines back to qemu-kvm.default
  * copy creation of group kvm to preinst - the group must exist when the
    kvm udev rule is installed (LP: #1103022) (LP: #1092715)
  * add adduser to qemu-system-common Pre-Depends for use by preinst.
 -- Serge Hallyn <email address hidden> Thu, 14 Mar 2013 14:21:53 -0500

Changed in qemu (Ubuntu):
status: In Progress → Fix Released
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.