From: Harry Butterworth <harry@hebutterworth.freeserve.co.uk>
To: Al Boldi <a1426z@gawab.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Questioning the Xen Design of the VMM
Date: Tue, 08 Aug 2006 10:17:13 +0100 [thread overview]
Message-ID: <1155028633.7709.2.camel@localhost.localdomain> (raw)
In-Reply-To: <200608071801.23845.a1426z@gawab.com>
On Mon, 2006-08-07 at 18:01 +0300, Al Boldi wrote:
> Greetings!
>
> The Xen project caught my attention on LKML discussing hypervisors, so I took
> a look at Xen and read the README, where it says:
>
> This install tree contains source for a Linux 2.6 guest
>
> This immediately turned me off, as I hoped Xen would be a bit more
> transparent, by simply exposing native hw tunneled thru some multiplexed Xen
> patched host-kernel driver.
>
> I maybe missing something, but why should the Xen-design require the guest to
> be patched?
Xen runs with high performance without binary translation on hardware
without virtualization support. This requires patching the guest.
With hardware virtualization support Xen can run the guest unmodified.
next prev parent reply other threads:[~2006-08-08 9:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-07 15:01 Questioning the Xen Design of the VMM Al Boldi
2006-08-08 9:10 ` Keir Fraser
2006-08-08 9:17 ` Harry Butterworth [this message]
2006-08-08 9:20 ` Petersson, Mats
2006-08-08 14:10 ` Al Boldi
2006-08-08 15:07 ` Petersson, Mats
2006-08-08 16:39 ` Steven Rostedt
2006-08-08 17:14 ` Petersson, Mats
2006-08-08 18:22 ` Steven Rostedt
2006-08-09 12:53 ` Al Boldi
2006-08-09 13:28 ` Petersson, Mats
2006-08-10 14:55 ` Al Boldi
2006-08-10 15:42 ` Petersson, Mats
2006-08-10 11:20 ` Daniel Stodden
2006-08-09 12:49 ` Daniel Stodden
2006-08-10 14:57 ` Al Boldi
2006-08-10 15:53 ` Daniel Stodden
2006-08-10 16:34 ` Petersson, Mats
2006-08-10 18:07 ` Daniel Stodden
2006-08-11 8:41 ` Petersson, Mats
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=1155028633.7709.2.camel@localhost.localdomain \
--to=harry@hebutterworth.freeserve.co.uk \
--cc=a1426z@gawab.com \
--cc=xen-devel@lists.xensource.com \
/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.