kernel-packages team mailing list archive

[James Hunt <1208455@xxxxxxxxxxxxxxxxxx>]

The latest advice for running on Canonistack (kvm guest instance where
nested=Y is to):

- Only run on a 64-bit Canonistack guest instance.
- Modify bin/prepare-testbed and bin/run-adt-test to start the autopkgtest VM using 'qemu-system-x86_64 -enable-kvm'.
- Have the DEP8 test running inside the autopkgtest VM start its VM using 'qemu -enable-kvm'.

Using the above but appending '-nographic >/tmp/kvm.log 2>&1' to each
kvm command-line to allow console log capture results in the first
created VM (the one created by prepare-testbed/bin/run-adt-test) locking
up. Unfortunately, there is no output in kvm.log.

I'll retry without '-nographic' as smb has noticed this seems to affect
the stability of the overall kvm stack. Even if this does work, it is
clearly not ideal to discard console output (unless there is another
magic qemu option we can try?)

-- 
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:
  In Progress
Status in “qemu-kvm” package in Ubuntu:
  New
Status in “linux” source package in Saucy:
  In Progress
Status in “qemu-kvm” source package in Saucy:
  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