kvm brings Oneiric host to a grinding halt
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
qemu-kvm (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
I'm running a Windows7 guest in KVM via libvirt/
More information attached, let me know what other info I should collect, the next time the machine is in that state.
---
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
DistroRelease: Ubuntu 11.10
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
KvmCmdLine:
UID PID PPID C SZ RSS PSR STIME TTY TIME CMD
116 2892 1 13 327807 1062024 0 07:34 ? 00:49:31 /usr/bin/kvm -S -M pc-0.14 -enable-kvm -m 1024 -smp 1,sockets=
MachineType: Hewlett-Packard HP EliteBook 8530w
NonfreeKernelMo
Package: qemu-kvm 0.14.1+
PackageArchitec
PccardctlIdent:
Socket 0:
product info: "RICOH", "Bay8Controller", "", ""
manfid: 0x0000, 0x0000
function: 254 (unknown)
PccardctlStatus:
Socket 0:
3.3V 16-bit PC Card
Subdevice 0 (function 0) bound to driver "pata_pcmcia"
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
Tags: oneiric running-unity
Uname: Linux 3.0.0-17-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout libvirtd lpadmin mock plugdev sambashare
dmi.bios.date: 12/08/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PDV Ver. F.11
dmi.board.name: 30E7
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 90.26
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: HP EliteBook 8530w
dmi.product.
dmi.sys.vendor: Hewlett-Packard
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
Changed in qemu-kvm (Ubuntu): | |
status: | Incomplete → Confirmed |
tags: | added: bios-outdated-f.20 needs-upstream-testing |
Changed in linux (Ubuntu): | |
status: | Incomplete → Invalid |
tags: | added: cscc |
Thanks for reporting this bug.
After this happens, do you have to reset the system, or does it get better after awhile?
Is it kvm itself, or libvirt, which is taking the cpu time?
Do you usually have only one vm up when this is happening?
Is there anything interesting in syslog?