kernel-packages team mailing list archive

[James Hunt <1208455@xxxxxxxxxxxxxxxxxx>]

What we know so far:

- the issue is not related to cloud-init.
- the very high CPU load was atleast partly caused by byobu bug 1208853. To disable byobu...

=== modified file 'bin/prepare-testbed'
--- bin/prepare-testbed 2013-08-06 08:05:16 +0000
+++ bin/prepare-testbed 2013-08-06 14:01:42 +0000
@@ -227,7 +227,7 @@
 
 apt_update: true
 apt_upgrade: true
-byobu_by_default: system
+byobu_by_default: disable
 
 packages:
  - eatmydata

- smb/apw noticed that nested=1 for the kvm_intel driver was not being
set in the 1st and 2nd level nested VMs but was being set on the host.
However, forcing nested=1 on the host system, the autopkgtest system
*and* the pristine nested VM (2nd-level nesting) does not stop the
kernel panic.

Now trying with linux-image-3.11.0-0-generic to see if that helps...


** No longer affects: cloud-init (Ubuntu)

** Summary changed:

- general protection fault running apt-get inside nested kvm VM
+ general protection fault running apt-get inside double nested kvm VM

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1208455

Title:
  general protection fault running apt-get inside double nested kvm VM

Status in “linux” package in Ubuntu:
  Incomplete
Status in “qemu-kvm” package in Ubuntu:
  New

Bug description:
  Attempting to run apt-get in a nested vm hosted in OpenStack results
  in a  general protection fault in the kernel in the nested VM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208455/+subscriptions