* [ kvm-Bugs-2517725 ] Windows 7 CPU Runaway
@ 2009-03-30 20:36 SourceForge.net
0 siblings, 0 replies; 4+ messages in thread
From: SourceForge.net @ 2009-03-30 20:36 UTC (permalink / raw)
To: noreply
Bugs item #2517725, was opened at 2009-01-18 12:44
Message generated for change (Comment added) made by martyg7
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.
----------------------------------------------------------------------
>Comment By: Martin Gallant (martyg7)
Date: 2009-03-30 15:36
Message:
Still present, and easily reproducible, on 2.6.29/kvm-84.
----------------------------------------------------------------------
Comment By: Martin Gallant (martyg7)
Date: 2009-01-18 14:35
Message:
I can reproduce this problem at will using -nic model=e1000
So this has nothing to do with virtio network drivers
I am attaching a gdb log showing backtrace of all 3 process threads
----------------------------------------------------------------------
Comment By: Technologov (technologov)
Date: 2009-01-18 13:24
Message:
VirtIO drivers will not be supported in Windows 7 BETA -- only in Final.
-Alexey
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2517725&group_id=180599
^ permalink raw reply [flat|nested] 4+ messages in thread
* [ kvm-Bugs-2517725 ] Windows 7 CPU Runaway
@ 2009-01-18 20:35 SourceForge.net
0 siblings, 0 replies; 4+ messages in thread
From: SourceForge.net @ 2009-01-18 20:35 UTC (permalink / raw)
To: noreply
Bugs item #2517725, was opened at 2009-01-18 12:44
Message generated for change (Comment added) made by martyg7
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.
----------------------------------------------------------------------
Comment By: Martin Gallant (martyg7)
Date: 2009-01-18 14:35
Message:
I can reproduce this problem at will using -nic model=e1000
So this has nothing to do with virtio network drivers
I am attaching a gdb log showing backtrace of all 3 process threads
----------------------------------------------------------------------
Comment By: Technologov (technologov)
Date: 2009-01-18 13:24
Message:
VirtIO drivers will not be supported in Windows 7 BETA -- only in Final.
-Alexey
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2517725&group_id=180599
^ permalink raw reply [flat|nested] 4+ messages in thread
* [ kvm-Bugs-2517725 ] Windows 7 CPU Runaway
@ 2009-01-18 19:24 SourceForge.net
0 siblings, 0 replies; 4+ messages in thread
From: SourceForge.net @ 2009-01-18 19:24 UTC (permalink / raw)
To: noreply
Bugs item #2517725, was opened at 2009-01-18 20:44
Message generated for change (Comment added) made by technologov
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.
----------------------------------------------------------------------
>Comment By: Technologov (technologov)
Date: 2009-01-18 21:24
Message:
VirtIO drivers will not be supported in Windows 7 BETA -- only in Final.
-Alexey
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2517725&group_id=180599
^ permalink raw reply [flat|nested] 4+ messages in thread
* [ kvm-Bugs-2517725 ] Windows 7 CPU Runaway
@ 2009-01-18 18:44 SourceForge.net
0 siblings, 0 replies; 4+ messages in thread
From: SourceForge.net @ 2009-01-18 18:44 UTC (permalink / raw)
To: noreply
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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2009-03-30 20:36 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-03-30 20:36 [ kvm-Bugs-2517725 ] Windows 7 CPU Runaway SourceForge.net
-- strict thread matches above, loose matches on Subject: below --
2009-01-18 20:35 SourceForge.net
2009-01-18 19:24 SourceForge.net
2009-01-18 18:44 SourceForge.net
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).