From: Hetz Ben Hamo <hetzbh@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] KQEMU on Win32 (+patch)
Date: Thu, 28 Jul 2005 00:18:29 +0200 [thread overview]
Message-ID: <41e41e7a05072715181794615a@mail.gmail.com> (raw)
In-Reply-To: <42E804E2.8000605@reactos.com>
I've updated my QEMU download section: http://qemu.dad-answers.com/download/
Your binaries are there now (under the win32 directory)
Thanks,
Hetz
On 7/28/05, Filip Navara <navaraf@reactos.com> wrote:
> Hi,
>
> as there were recently few questions about KQEMU I decided to dedicate
> few minutes at answering them and to post a few comments.
>
> > 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.
>
> (Also note that this may apply to KQEMU too though I have no proof.)
>
> > The changelog mentions that the KQEMU accelerator is now available as
> > a preliminary executable for Windows. I've not been able to find a
> > link to that version anywhere. Should I pull down the sources and
> > compile on my Linux machine, or is there a pre-compiled version about?
>
> You can compile it yourself on either Windows machine with MinGW or on
> linux machine with MinGW cross-compiler. 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. If anyone can offer me
> hosting for these binaries I would be glad.
>
> As a final note (especially for Fabrice), attached are patches for KQEMU
> for easier driver installation (quite not there yet, but a bit closer)
> and implementation of kqemu_schedule (as requested). I'm planing to port
> this to QVM86 shortly.
>
> Best regards,
> Filip
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
>
>
>
next prev parent reply other threads:[~2005-07-27 22:21 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 [this message]
2005-07-28 0:33 ` Elefterios Stamatogiannakis
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=41e41e7a05072715181794615a@mail.gmail.com \
--to=hetzbh@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.