public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "André Weidemann" <Andre.Weidemann@web.de>
To: kvm@vger.kernel.org
Subject: Windows7 crashes inside the VM when starting a certain program
Date: Thu, 07 Jul 2011 07:26:08 +0200	[thread overview]
Message-ID: <4E154370.5090101@web.de> (raw)

Hi,
I am running Windows7 x64 in a VM which crashes after starting a certain 
game. Actually there are two games both from the same company, that make 
the VM crash after starting them.
Windows crashes right after starting the game. With the 1st game the 
screen goes black as usual and the cursor keeps spinning for 3-5 seconds 
until Windows crashes. With the second game I get to 3D the login 
screen. The game then crashes after logging in.
Windows displays this error message on the first crash:
http://pastebin.com/kMzk9Jif
Windows then finishes writing the crash dump and restarts.
I can reproduce Windows crashing every time I start the game while the 
VM keeps running without any problems.
When Windows reboots after the first crash and the game is started 
again, the message on the following blue screen changes slightly and 
stays the same(except for the addresses) for every following crash:
http://pastebin.com/jVtBc4ZH

I first thought that this might be related to a certain feature in 3D 
acceleration being used, but Futuremark 3DMark Vantage or 3DMark 11 run 
without any problems. They run a bit choppy on some occasions, but do 
that without crashing Windows7 or the VM.

How can I proceed to investigate what is going wrong?

I am using a qemu-kvm git clone from a few days ago 
(d58931037dbb4fbc2fbb33858629d3fabfd1b0d4).

This is my command line:
/usr/local/bin/qemu-system-x86_64 -boot order=ncd -cpu host -vnc 
192.168.3.1:0 -k de -smp 2,cores=1,threads=2,sockets=1 -drive 
file=/mnt/ntfs/Windows7_120G.img,if=ide,index=0,cache=writeback -m 4096 
-drive file=/dev/cdrom1,if=ide,index=3,media=cdrom,cache=none -device 
pci-assign,host=03:00.0,id=radeon6950,addr=0x11 -net 
nic,model=e1000,macaddr=DE:AD:BE:EF:42:42 -net 
tap,script=/usr/local/bin/qemu-ifup -rtc base=localtime -parallel none 
-soundhw hda -usb -device usb-ehci,id=ehci -usbdevice host:045e:00f9 
-chardev stdio,id=seabios -device 
isa-debugcon,iobase=0x402,chardev=seabios -watchdog ib700 
-watchdog-action debug -monitor telnet:127.0.0.1:11111,server,nowait,nodelay

Regards
  André

             reply	other threads:[~2011-07-07  5:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-07  5:26 André Weidemann [this message]
2011-07-26  5:29 ` Windows7 crashes inside the VM when starting a certain program André Weidemann
2011-07-26  6:42   ` Jan Kiszka
2011-07-26 10:08   ` Gleb Natapov
2011-07-26 10:57     ` André Weidemann
2011-07-27  8:56       ` Gleb Natapov
2011-07-29  7:20         ` André Weidemann
2011-07-29 11:37           ` Gleb Natapov
2011-07-30 12:29             ` André Weidemann
2011-07-31  8:16               ` Avi Kivity
2011-07-31  8:34                 ` Gleb Natapov
2011-07-28 12:01 ` Paolo Bonzini
2011-07-28 12:11   ` Gleb Natapov
2011-07-28 13:16   ` André Weidemann
2011-07-28 13:21     ` Avi Kivity
2011-07-28 13:49       ` Paolo Bonzini
2011-07-28 17:44         ` André Weidemann
2011-07-29  7:11           ` Paolo Bonzini

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=4E154370.5090101@web.de \
    --to=andre.weidemann@web.de \
    --cc=kvm@vger.kernel.org \
    /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