qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Nathan Froyd <froydnj@codesourcery.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: "Frédéric Pétrot" <Frederic.Petrot@imag.fr>,
	"François Revol" <revol@free.fr>,
	"wolfgang mueller" <wolfgang@acm.org>,
	"Alexander Graf" <agraf@suse.de>,
	"QEMU-devel Developers" <qemu-devel@nongnu.org>
Subject: Re: Windows host support [was: Re: [Qemu-devel] CFP: 1st International QEMU Users Forum]
Date: Mon, 29 Nov 2010 07:00:25 -0800	[thread overview]
Message-ID: <20101129150024.GV8544@codesourcery.com> (raw)
In-Reply-To: <4CF3B9F4.9090807@codemonkey.ws>

On Mon, Nov 29, 2010 at 08:34:28AM -0600, Anthony Liguori wrote:
> On 11/28/2010 04:56 AM, Alexander Graf wrote:
>> On 28.11.2010, at 01:17, Nathan Froyd wrote:
>>> We (CodeSourcery) are very interested in Windows host support.  (We
>>> distribute QEMU with our commerical development products for
>>> ARM/PowerPC/MIPS/SH/ColdFire/x86.)  Unfortunately, we've mostly been
>>> backporting patches lately and haven't done a full merge from upstream
>>> in some time, so we haven't noticed any potential breakage.  If somebody
>>> wanted to point out to me what the (potential) Windows issues are, we
>>> could take a look.
>>>      
>> Redirecting you to Anthony here for the specifics. The main problem
>> is that we don't have anyone who takes the lead on Windows
>> support. _If_ something breaks of _if_ we need someone to take over
>> the windows specific parts, there's this huge gap.
>
> Uh, Windows system simulation has never worked reliably.  It doesn't  
> even have proper AIO support.
>
> If someone is building a product based on it, I'm amazed.

Well, technically we only support QEMU as a simple instruction set
simulator in our products, and the bits present work well enough for
that.  (It is of course possible those bits have been broken in the time
since our last upstream merge.)  If you want to venture into system
simulation and it breaks, then you get to keep both pieces.

It would, however, be better to eventually support full system
simulation, and making Windows hosts work right would be a necessary
precondition to that.

-Nathan

  reply	other threads:[~2010-11-29 15:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20101125235615.157DC28C0F@zimbra14-e2.priv.proxad.net>
2010-11-26  0:26 ` [Qemu-devel] CFP: 1st International QEMU Users Forum François Revol
2010-11-28  0:17   ` Windows host support [was: Re: [Qemu-devel] CFP: 1st International QEMU Users Forum] Nathan Froyd
2010-11-28 10:56     ` Alexander Graf
2010-11-29 14:34       ` Anthony Liguori
2010-11-29 15:00         ` Nathan Froyd [this message]
2011-01-28 18:45         ` [Qemu-devel] X86 Debian <== guest ... ARM based Linux <== host ? AGSCalabrese
2011-02-04 20:14           ` Aurelien Jarno

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=20101129150024.GV8544@codesourcery.com \
    --to=froydnj@codesourcery.com \
    --cc=Frederic.Petrot@imag.fr \
    --cc=agraf@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=qemu-devel@nongnu.org \
    --cc=revol@free.fr \
    --cc=wolfgang@acm.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).