| 2012-08-22 18:31:41 |
Jamie Strandboge |
bug |
|
|
added bug |
| 2012-08-22 18:33:18 |
Jamie Strandboge |
description |
On 12.10, when I boot my host, guests are not able to load the kvm_intel because the kvm_intel module is loaded without nested=1. I presume this is happening because the module is loading before the qemu-kvm upstart job runs. The upstart job works correctly in that if after a fresh reboot I do:
$ sudo stop qemu-kvm
$ sudo start qemu-kvm
I am then able to load kvm_intel in guests (ie, nested=1 was honored).
WORKAROUND:
Add the following to /etc/modprobe.d/qemu-kvm.conf:
options kvm_intel nested=1 |
On 12.10, when I boot my host, guests are not able to load the kvm_intel module because the kvm_intel module on the host is loaded without nested=1 (ie, nested virtualization is broken). I presume this is happening because the module is loading before the qemu-kvm upstart job runs. The upstart job works correctly in that if after a fresh reboot I do:
$ sudo stop qemu-kvm
$ sudo start qemu-kvm
I am then able to load kvm_intel in guests (ie, KVM_NESTED=" nested=1" was honored in /etc/default/qemu-kvm).
WORKAROUND:
Add the following to /etc/modprobe.d/qemu-kvm.conf:
options kvm_intel nested=1 |
|
| 2012-08-22 18:40:10 |
Jamie Strandboge |
description |
On 12.10, when I boot my host, guests are not able to load the kvm_intel module because the kvm_intel module on the host is loaded without nested=1 (ie, nested virtualization is broken). I presume this is happening because the module is loading before the qemu-kvm upstart job runs. The upstart job works correctly in that if after a fresh reboot I do:
$ sudo stop qemu-kvm
$ sudo start qemu-kvm
I am then able to load kvm_intel in guests (ie, KVM_NESTED=" nested=1" was honored in /etc/default/qemu-kvm).
WORKAROUND:
Add the following to /etc/modprobe.d/qemu-kvm.conf:
options kvm_intel nested=1 |
On 12.10, when I boot my host, guests are not able to load the kvm_intel module because the kvm_intel module on the host is loaded without nested=1 (ie, nested virtualization is broken). I presume this is happening because the module is loading before the qemu-kvm upstart job runs. The upstart job works correctly in that if after a fresh reboot I do:
$ sudo stop qemu-kvm
$ sudo start qemu-kvm
I am then able to load kvm_intel in guests (ie, KVM_NESTED=" nested=1" was honored in /etc/default/qemu-kvm).
WORKAROUND:
Add the following to /etc/modprobe.d/qemu-kvm.conf:
options kvm_intel nested=1
I should note that because of bug #1040033, I am running 12.04's qemu. I verified that /etc/default/qemu-kvm between 12.04 and 12.10 are identical and that the upstart jobs should be equivalent (the 12.10 one adds '|| true' to the end of all modprobe lines). |
|
| 2012-08-22 18:52:12 |
Jamie Strandboge |
nominated for series |
|
Ubuntu Quantal |
|
| 2012-08-22 18:52:12 |
Jamie Strandboge |
bug task added |
|
qemu-kvm (Ubuntu Quantal) |
|
| 2012-08-22 18:52:59 |
Jamie Strandboge |
tags |
|
rls-q-incoming |
|
| 2012-08-23 14:52:24 |
Serge Hallyn |
qemu-kvm (Ubuntu Quantal): importance |
Undecided |
High |
|
| 2012-08-23 14:52:29 |
Serge Hallyn |
qemu-kvm (Ubuntu Quantal): status |
New |
Triaged |
|
| 2012-08-23 14:52:33 |
Serge Hallyn |
qemu-kvm (Ubuntu Quantal): assignee |
|
Serge Hallyn (serge-hallyn) |
|
| 2012-08-23 16:25:11 |
Launchpad Janitor |
qemu-kvm (Ubuntu Quantal): status |
Triaged |
Fix Released |
|
