From: Nuno Silva <nuno.silva@vgertech.com>
To: "Scheer, Roque" <roque.scheer@hp.com>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: XEN and Windows
Date: Fri, 29 Oct 2004 04:19:58 +0100 [thread overview]
Message-ID: <4181B6DE.1000301@vgertech.com> (raw)
In-Reply-To: <8D41D1F60264314591FA7C0B012EB7BBCDA689@spbexc01.americas.cpqcorp.net>
Scheer, Roque wrote:
> Hello,
>
> I've already learned from this list that running Windows on top of XEN
> will not be possible soon (or ever).
>
> However, I would like to propose the idea of running XEN on top of
> Windows. That is, instead of having XEN being an hypervisor (a la VMWare
> ESX Server) one could have XEN working as a virtualization layer running
> on top of Windows (a la VMWare Workstation). One could then run multiple
> instances of the efficient (paravirtualized) ports of Linux or BSD on
> XEN, in parallel with windows applications.
>
> Would the new XEN 2.0 driver architecture ease the sharing of the
> windows drivers with the XEN domains (providing some driver conversion
> layer is provided)?
I don't think that XEN will run nicely (read: performance, xen's number
one advantage) on anything but bare metal. But the developers can answer
that better than me.
In the mean while you can check out Cooperative Linux at
http://colinux.org/ that does what you want.
Peace,
Nuno Silva
-------------------------------------------------------
This Newsletter Sponsored by: Macrovision
For reliable Linux application installations, use the industry's leading
setup authoring tool, InstallShield X. Learn more and evaluate
today. http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/
prev parent reply other threads:[~2004-10-29 3:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-28 21:27 XEN and Windows Scheer, Roque
2004-10-29 3:19 ` Nuno Silva [this message]
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=4181B6DE.1000301@vgertech.com \
--to=nuno.silva@vgertech.com \
--cc=roque.scheer@hp.com \
--cc=xen-devel@lists.sourceforge.net \
/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.