From: Bill Davidsen <davidsen@tmr.com>
To: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>
Cc: linux-kernel@vger.kernel.org, Keir.Fraser@cl.cam.ac.uk,
Christian.Limpach@cl.cam.ac.uk, Steven.Hand@cl.cam.ac.uk
Subject: Re: Xen 2.0 VMM patches
Date: Thu, 18 Nov 2004 16:37:22 -0500 [thread overview]
Message-ID: <419D1612.4000702@tmr.com> (raw)
In-Reply-To: <E1CUZSs-000502-00@mta1.cl.cam.ac.uk>
Ian Pratt wrote:
> Original Xen 2.0 release annoucement:
>
> The Xen team are pleased to announce the release of Xen 2.0, the
> open-source Virtual Machine Monitor. Xen enables you to run
> multiple operating systems images concurrently on the same
> hardware, securely partitioning the resources of the machine
> between them. Xen uses a technique called 'para-virtualization'
> to achieve very low performance overhead -- typically just a few
I wasn't about to mention this, but since you reposted it I will. I
shared the original post with a number of people and at least three
mentioned it.
The term "low performance overhead" just seems to make people thinks
it's slow, and they don't read past it. I highly suggest either "low
overhead" or "low performance impact" would avoid this.
Perhaps I just know a lot of other people who suffer from literalism.
> percent relative to native. This new release provides kernel
> support for Linux 2.4.27/2.6.9, NetBSD and FreeBSD.
>
> Xen 2.0 runs on almost the entire set of modern x86 hardware
> supported by Linux, and is easy to 'drop-in' to an existing Linux
> installation. The new release has a lot more flexibility in how
> guest OS virtual I/O devices are configured. For example, you can
> configure arbitrary firewalling, bridging and routing of guest
> virtual network interfaces, and use copy-on-write LVM volumes or
> loopback files for storing guest OS disk images. Another new
> feature is 'live migration', which allows running OS images to be
> moved between nodes in a cluster without having to stop
> them. Visit http://xen.sf.net for downloads and documentation.
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
next prev parent reply other threads:[~2004-11-18 21:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-17 23:43 Ian Pratt
2004-11-18 6:59 ` Pekka Enberg
2004-11-18 7:03 ` Pekka Enberg
2004-11-18 21:37 ` Bill Davidsen [this message]
[not found] <31IYf-4Y-5@gated-at.bofh.it>
2004-11-18 4:50 ` Andi Kleen
2004-11-18 10:23 ` Ian Pratt
2004-11-18 13:22 ` Andi Kleen
2004-11-18 17:26 ` Roland Dreier
2004-11-18 17:38 ` Ian Pratt
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=419D1612.4000702@tmr.com \
--to=davidsen@tmr.com \
--cc=Christian.Limpach@cl.cam.ac.uk \
--cc=Ian.Pratt@cl.cam.ac.uk \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=Steven.Hand@cl.cam.ac.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome