Bug 16158 - winxp guest hangs after idle for ~30 minutes
Summary: winxp guest hangs after idle for ~30 minutes
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Virtualization
Classification: Unclassified
Component: kvm (show other bugs)
Hardware: All Linux
: P1 high
Assignee: Avi Kivity
URL:
Keywords:
Depends on:
Blocks: 15310
  Show dependency tree
 
Reported: 2010-06-08 17:52 UTC by brimhall
Modified: 2010-07-23 11:35 UTC (History)
5 users (show)

See Also:
Kernel Version: 2.6.34
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments

Description brimhall 2010-06-08 17:52:38 UTC
When I switched to 2.6.34 after being on 2.6.33.5 and below, my kvm-qemu winxp guest hanged consistently after being idle for ~30 minutes.

I thought it was the kvm-qemu 0.12.4 which had also been upgraded, but after downgrading to kvm-qemu 0.12.3 and 0.11.1 I still saw the same behavior, so guessing the issue is with the kernel module.

System details:
debian "testing" amd64, intel i7-920, 6 Gb memory.
Comment 1 Avi Kivity 2010-06-09 09:05:55 UTC
Any chance of a bisect to see what's the cause?

'git bisect start v2.6.34 v2.6.35 virt/kvm arch/x86/kvm' should get you there.

Also of interest

- 'info registers' of a hung guest
- 'x /30i $eip - 30 of same
Comment 2 Avi Kivity 2010-06-09 09:07:11 UTC
Sorry, the bisect command should be

  git bisect start v2.6.34 v2.6.33 virt/kvm arch/x86/kvm
Comment 3 brimhall 2010-06-14 01:28:08 UTC
Bug still open. Need to figure out how to do kvm-qemu console to get the output from the "info registers" above.

-geoffb
Comment 4 Avi Kivity 2010-06-15 18:42:05 UTC
Press alt-ctrl-2 in the qemmu window

or

start qemu-kvm with the option '-monitor stdio'

Note You need to log in before you can comment on or make changes to this bug.