public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "SourceForge.net" <noreply@sourceforge.net>
To: noreply@sourceforge.net
Subject: [ kvm-Bugs-2517725 ] Windows 7 CPU Runaway
Date: Sun, 18 Jan 2009 18:44:53 +0000	[thread overview]
Message-ID: <E1LOcdh-0002Ni-Ng@565xhf1.ch3.sourceforge.com> (raw)

Bugs item #2517725, was opened at 2009-01-18 12:44
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2517725&group_id=180599

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Martin Gallant (martyg7)
Assigned to: Nobody/Anonymous (nobody)
Summary: Windows 7 CPU Runaway

Initial Comment:
After some uptime in the client, I have observed Windows7 going into a
CPU runaway lockup.

Host is Athlon x2 running Debian Lenny amd64
     + kernel.org 2.6.28 kernel
     + kvm-83
Client is Windows 7 beta 32-bit image, (UP or SMP) with virtio drivers.

This happens when running the guest either as UP or SMPx2.
When running as UP, only one of my host CPUs are affected.
When running as SMPx2, both of my host CPUs are affected.

This can be reproduced with reasonable reliability by either
    a) Commanding a restart in the guest machine
    b) Significant sustained disk IO traffic, e.g. 200+ MB/s

Invocation:
sudo $KVM -name kvm-windows7 -smp 2 -m 1024 -localtime \
    -drive file=/dev/vm/kvm-windows7 \
    -drive file=/dev/vm/usenet \
    -net nic,macaddr=00:ff:3e:a4:f4:20,model=virtio -net tap \
    -daemonize -vnc localhost:1,to=4 -usbdevice tablet

After lockup, here is the backtrace I am pulling from gdb
[Am I doing this right?  I am a little rusty]

(gdb) attach 12717

(gdb) bt
#0  0x00007f37b1496ce2 in select () from /lib/libc.so.6
#1  0x00000000004088cb in main_loop_wait (timeout=0)
    at /usr/src/kvm-83/qemu/vl.c:3637
#2  0x00000000005142ea in kvm_main_loop ()
    at /usr/src/kvm-83/qemu/qemu-kvm.c:600
#3  0x000000000040c952 in main (argc=<value optimized out>,
    argv=0x7fffba8f1f78, envp=<value optimized out>)
    at /usr/src/kvm-83/qemu/vl.c:3799

Detailed configuration information attached.
Nohing I can find in the logs I would consider relevant.



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2517725&group_id=180599

             reply	other threads:[~2009-01-18 18:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-18 18:44 SourceForge.net [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-01-18 19:24 [ kvm-Bugs-2517725 ] Windows 7 CPU Runaway SourceForge.net
2009-01-18 20:35 SourceForge.net
2009-03-30 20:36 SourceForge.net

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1LOcdh-0002Ni-Ng@565xhf1.ch3.sourceforge.com \
    --to=noreply@sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox