booting to 2.6.32-22-generic prevents kvm machines from starting
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Last night's Lucid kernel update broke kvm. None of my vms (via virt-manager) start. The console goes black and that's it. I know it's not a vnc/console issue because the vms are never pingable or ssh-able. Host is an intel i7 920 running Lucid. Guests don't matter: debian, windows 7, une, fedora, ubuntu all stop at exactly the same place. Even booting lucid 64bit live desktop stops at the same place.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-
Regression: Yes
Reproducible: Yes
ProcVersionSign
Uname: Linux 2.6.32-22-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfbcf8000 irq 22'
Mixer name : 'Realtek ALC1200'
Components : 'HDA:10ec0888,
Controls : 38
Simple ctrls : 21
Card1.Amixer.info:
Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbefc000 irq 17'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,
Controls : 4
Simple ctrls : 1
Card1.Amixer.
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [off]
Date: Thu Jun 3 11:04:23 2010
HibernationDevice: RESUME=
MachineType: Dell Inc. Studio XPS 435MT
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageV
RfKill:
SourcePackage: linux
dmi.bios.date: 05/05/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.1
dmi.board.name: 0R849J
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Studio XPS 435MT
dmi.sys.vendor: Dell Inc.
barry see my bug raised a little while before yours today:
#589163
Note the important thing is that almost immediately on start the CPU(s) assigned to the VM peg at 100% utilisation and stay that way until a force off.
Only way I have got my VMs working is to revert to 2.6.32-21
The only KVM related thing between -21 and -22 is apparently the fix for CVE-2010-0419
Unfortunately I don't have a machine spare to build on debian to check the behaviour from upstream directly with no ubuntu packages...