qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Elefterios Stamatogiannakis <estama@dblab.ece.ntua.gr>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] KQEMU on Win32 (+patch)
Date: Thu, 28 Jul 2005 03:33:29 +0300	[thread overview]
Message-ID: <42E827D9.5060609@dblab.ece.ntua.gr> (raw)
In-Reply-To: <42E804E2.8000605@reactos.com>



Filip Navara wrote:
>  > I'm trying to find out why qvm86 crashes the host (instant reboot 
> when right clicking on some icons on the guest desktop).
>  > So i thought if it is possible to use some code from kqemu-win32.c to 
> update qvm86-win32.c
> 
> No, I wrote both of the files and I can honestly tell you that copying 
> between them will not help. There is one known case where QVM86 on WinNT 
> platforms crashes the host machine and that's when NOEXECUTE support is 
> enabled (see boot.ini). The method QVM86 uses for executing the code 
> involves copying executable code into an allocated page which 
> unfortunately has the NX bit set. I have an experimental fix for this, 
> but I need someone with adequate environment (AMD64 and Win XP SP2+) to 
> test it... Of course host crash can be caused by other bug.
> 

I knew you wrote them both (who else could?). I was (wrongly) thinking 
that the qvm86 version is older than kqemu but apparently they work 
differently (thanks for the clarification).

As for the NOEXECUTE, i'm testing kqemu and qvm86 on a Athlon XP 
(regular 32bit, without NX). So the instant reboots must be from 
something else.

> You can compile it yourself on either Windows machine with MinGW or on 
> linux machine with MinGW cross-compiler. 

I tried to compile kqemu with MinGW without luck (although i didn't push 
it much). The error was:

kqemu-win32.o(.text+0x217):kqemu-win32.c: undefined reference to 
`_imp__MmMapIoSpace@16'

Probably it is that i don't have the windows driver development kit.

I'm temporary hosting a set of
> QEMU / KQEMU 0.7.1 for Windows binaries here: 
> http://www.volny.cz/xnavara/qemu-0.7.1.zip.

Do these binaries include your latest patches?

teris.

ps I cannot imagine how a man can know that much about the windows 
internals and at the same time be comfortable working with linux device 
drivers stuff.

  parent reply	other threads:[~2005-07-28  0:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-27 22:04 [Qemu-devel] KQEMU on Win32 (+patch) Filip Navara
2005-07-27 22:18 ` Hetz Ben Hamo
2005-07-28  0:33 ` Elefterios Stamatogiannakis [this message]
2005-07-28  9:26   ` Filip Navara
2005-07-28 10:24     ` 姚春林
2005-07-28 12:30       ` Christian MICHON
2005-07-28 12:40         ` Filip Navara
2005-07-28 13:18         ` 姚春林
2005-07-28 13:29           ` Christian MICHON
2005-07-28 13:42             ` Cirrus Emulation (was: [Qemu-devel] KQEMU on Win32 (+patch)) Hetz Ben Hamo
2005-07-28 14:52               ` Christian MICHON
2005-07-29  7:23                 ` Christian MICHON
2005-07-28 14:44             ` [Qemu-devel] KQEMU on Win32 (+patch) Doctor Bill
2005-07-28 15:08               ` Johannes Schindelin
2005-07-28 16:26                 ` Joshua Kugler

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=42E827D9.5060609@dblab.ece.ntua.gr \
    --to=estama@dblab.ece.ntua.gr \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).