From: Darryl Dixon <esrever_otua@pythonhacker.is-a-geek.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] coLinux and Qemu? --was-- Plex86 and Qemu
Date: Mon, 14 Feb 2005 13:05:38 +1300 [thread overview]
Message-ID: <1108339538.1601.5.camel@localhost.localdomain> (raw)
In-Reply-To: <000e01c51222$8f893890$254d21d1@computername>
[-- Attachment #1: Type: text/plain, Size: 1723 bytes --]
Just a thought, but coLinux (www.colinux.org) has a low-level Windows
driver to give the Linux kernel access to the CPU. Perhaps this could
be modified to simply allow Qemu to execute user-space code (a la kqemu)
on Windows?
I'm afraid I'm not nearly enough of an uber-hacker to even assess the
viability...
Cheers,
D
On Sun, 2005-02-13 at 17:20 -0600, jeebs@yango.us wrote:
> From: "Jim C. Brown" <jma5@umd.edu>
>
[snip]
>
> Fabrice mentioned long ago that his module would only work with Linux hosts. I don't know why. Whether its his familiarity with Linux, or if it's something that can only be done under Linux and not Windows. (I have no idea how vmware & virtualPC do their stuff, or what method kqemu uses.)
>
> So when he did finally release it, it was no surprise. I was already resigned to the fact that it wasn't going to help me in the slightest. And therefor I don't care what license it is released under. If it ever works under Windows, then I'll care.
>
> When you announced your plans, I was hoping that it might be something that I and 95% of the rest of the world could actually use. You weren't clear in your original message, so I asked.
>
> Turns out I was wrong though.
>
> Since it's not going to help us, I have no further interest in your project.
>
> Your project sounds like it falls into the exact same category as qemu-fast and now kqemu... Mildly worth knowing they exist, but of no practical value for me. No reason to get excited or upset.
>
>
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
--
Darryl Dixon <esrever_otua@pythonhacker.is-a-geek.net>
[-- Attachment #2: Type: text/html, Size: 2678 bytes --]
next prev parent reply other threads:[~2005-02-14 0:25 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-12 9:18 [Qemu-devel] FreeOSZoo will stop March 1, 2005 Jean-Michel POURE
2005-02-12 10:15 ` Magnus Damm
2005-02-12 10:18 ` Brad Campbell
2005-02-12 12:19 ` Antti-Juhani Kaijanaho
2005-02-12 12:20 ` Daniel Egger
2005-02-12 13:42 ` Brad Campbell
2005-02-12 16:15 ` Daniel Egger
2005-02-12 17:00 ` Fabrice Bellard
2005-02-12 18:11 ` Jernej Simončič
2005-02-12 21:18 ` Daniel Egger
2005-02-12 23:01 ` Darrin Ritter
2005-02-13 0:06 ` Jernej Simončič
2005-02-13 11:28 ` Daniel Egger
2005-02-13 17:01 ` Jim C. Brown
2005-02-13 17:40 ` [Qemu-devel] Plex86 and Qemu jeebs
2005-02-13 18:27 ` Jim C. Brown
2005-02-13 19:35 ` jeebs
2005-02-13 22:06 ` Jim C. Brown
2005-02-13 23:20 ` jeebs
2005-02-14 0:05 ` Darryl Dixon [this message]
2005-02-14 0:37 ` [Qemu-devel] coLinux and Qemu? --was-- " Jim C. Brown
2005-02-14 0:58 ` Mark Williamson
2005-02-14 0:34 ` [Qemu-devel] " Jim C. Brown
2005-02-14 10:39 ` Andreas Bollhalder
2005-02-13 22:18 ` Adrian Smarzewski
2005-02-13 23:04 ` Martin Koniczek
2005-02-14 14:18 ` Phil Krylov
2005-02-15 23:32 ` Old version support. Was: Re: [Qemu-devel] FreeOSZoo will stop March 1, 2005 Gregory Alexander
2005-02-16 18:51 ` Fabrice Bellard
2005-02-13 0:18 ` Jim C. Brown
2005-02-13 4:42 ` James Mastros
2005-02-13 5:26 ` Jim C. Brown
2005-02-13 6:21 ` James Mastros
2005-02-13 10:02 ` Darryl Dixon
2005-02-13 16:53 ` Jim C. Brown
2005-02-13 13:32 ` [Qemu-devel] " Robert Wittams
2005-02-12 22:41 ` [Qemu-devel] " Grzegorz Kulewski
2005-02-17 21:53 ` Herbert Poetzl
2005-02-17 22:18 ` Grzegorz Kulewski
2005-02-17 23:25 ` Fabrice Bellard
2005-02-18 4:29 ` John R. Hogerhuis
2005-02-18 8:23 ` Asko Kauppi
2005-02-18 11:05 ` Elefterios Stamatogiannakis
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=1108339538.1601.5.camel@localhost.localdomain \
--to=esrever_otua@pythonhacker.is-a-geek.net \
--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).