From: G L <3ntr0p13@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: xen is not working with qemu0.7/kqemu
Date: Fri, 17 Jun 2005 15:43:27 +0200 [thread overview]
Message-ID: <9a8ae26c0506170643444f8a8e@mail.gmail.com> (raw)
In-Reply-To: <9a8ae26c050613092046628103@mail.gmail.com>
>> If qemu with the kqemu module can run under xen, this
>> alleviates part of the pressure of getting xen to run
>> windows under a linux host.
>
>but of course, it will also kill the good performance
>xen could have with a windows support (which already
>worked, but is very unlikely to work in the future, as
>it requires M$ to adapt their OS to the xen architecture)
>
>best,
>Herbert
Won't it be possible to adapt kqemu/qvm86/qemu to make it aware of the
Xen architecture (i-e, "porting Qemu to xen") Please note that this is
a purely rethorical question, as I don't know what it really involves.
On the other hand, Mark Williamson, one of the Xen dev pointed on Xen
devel ML on a very interesting document from Microsoft
(http://download.microsoft.com/download/9/8/f/98f3fe47-dfc3-4e74-92a3-088782200fe7/TWAR05013_WinHEC05.ppt)
It seems that MS will follow an approach similar to Xen for their
future virtualization technology (maybe because MS research was
involved in Xen's first steps)
We can dream and hope that it will be possible to adapt Xen to run MS
VM (though I believe MS will do whatever is possible to make this
impossible).
MH2C,
Gildas
next prev parent reply other threads:[~2005-06-17 13:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-10 15:02 [Qemu-devel] xen is not working with qemu0.7/kqemu G L
2005-06-13 13:23 ` [Qemu-devel] " G L
2005-06-13 14:28 ` Ishwar Rattan
2005-06-13 16:20 ` G L
2005-06-17 13:43 ` G L [this message]
2005-06-17 14:23 ` Mark Williamson
2005-06-16 5:33 ` John R. Hogerhuis
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=9a8ae26c0506170643444f8a8e@mail.gmail.com \
--to=3ntr0p13@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 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).