From: Doug McNaught <doug@mcnaught.org>
To: John Bradford <john@grabjohn.com>
Cc: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>,
karim@opersys.com, linux-kernel@vger.kernel.org
Subject: Re: [Xen-devel] Re: [ANNOUNCE] Xen high-performance x86 virtualization
Date: 03 Oct 2003 09:14:08 -0400 [thread overview]
Message-ID: <m3ad8iihun.fsf@varsoon.wireboard.com> (raw)
In-Reply-To: John Bradford's message of "Fri, 3 Oct 2003 11:47:28 +0100"
John Bradford <john@grabjohn.com> writes:
> I think we might be talking about different things - what I meant was
> if you run a kernel compiled to support Xen on X86 natively without
> Xen, is there a big performance penalty, not if you run a single VM in
> Xen?
My understanding from reading the paper is that you can't do
this--'x86-xen' is a separate "architecture" and won't boot on the
bare metal.
-Doug
next prev parent reply other threads:[~2003-10-03 13:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-02 9:17 [ANNOUNCE] Xen high-performance x86 virtualization Ian Pratt
2003-10-02 10:12 ` Lars Marowsky-Bree
2003-10-02 13:21 ` Oliver M. Bolzer
2003-10-02 14:25 ` Karim Yaghmour
2003-10-02 14:37 ` [Xen-devel] " Keir Fraser
2003-10-02 14:45 ` Karim Yaghmour
2003-10-02 14:48 ` Keir Fraser
2003-10-02 15:15 ` John Bradford
2003-10-02 15:30 ` Keir Fraser
2003-10-02 16:39 ` Theodore Ts'o
2003-10-02 17:23 ` Keir Fraser
2003-10-02 18:42 ` Karim Yaghmour
2003-10-02 18:53 ` Keir Fraser
2003-10-03 1:59 ` Herbert Poetzl
2003-10-03 8:13 ` Ian Pratt
2003-10-03 10:12 ` Andreas Hauser
2003-10-03 10:29 ` Ian Pratt
2003-10-03 11:53 ` Andreas Hauser
2003-10-03 12:40 ` Ian Pratt
2003-10-03 8:19 ` John Bradford
2003-10-03 9:19 ` Keir Fraser
2003-10-03 10:47 ` John Bradford
2003-10-03 13:14 ` Doug McNaught [this message]
[not found] <CA95C29D57188841ABB072EA7357C00D02C13377@orsmsx402.jf.intel.com>
2003-10-03 1:50 ` Paul Brett
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=m3ad8iihun.fsf@varsoon.wireboard.com \
--to=doug@mcnaught.org \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=john@grabjohn.com \
--cc=karim@opersys.com \
--cc=linux-kernel@vger.kernel.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.