All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacob Gorm Hansen <jacobg@diku.dk>
To: Tom Hibbert <tom@nsp.co.nz>
Cc: Tim Freeman <tfreeman@mcs.anl.gov>, xen-devel@lists.sourceforge.net
Subject: Re: Xen and VMware
Date: Wed, 16 Feb 2005 14:50:23 -0800	[thread overview]
Message-ID: <4213CE2F.9040300@diku.dk> (raw)
In-Reply-To: <31F19452BA8B2042A359D849B74B1BF00C02B0@aklexch01.nsp.local>

Tom Hibbert wrote:
> Typical corporate talking head blah. Interesting that he talks about
> Vmotion as a 'killer technology' when Xen is already doing it. 
> If you read the interview there's quite a bit of Xen-bashing. The guy
> rags on the requirement for modification of the host kernel. He is
> comparing the two products as if they took the same approach, failing to
> mention that Xen's paravirtualisation architecture eliminates all of the
> costly performance overhead his company's product is famous for...

I still think you need to respect VMWare for breathing new life into 
virtual machine research. And I still think Xen can be improved (as is 
happening now) with regards to memory footprint etc. VMWare ESX is also 
likely to have some performance benefits from having the drivers in the 
kernel, even though that comes at the cost of them having to implement 
the drivers themselves. And the fact that they can host Windows is a big 
win with lots of customers.

VMWare does some amount of paravirtualization, with all the VMWare tools 
that you need to install. In fact, Xen seems to be going in VMWare's 
direction (shadow page tables, writable page tables, binary rewriting, 
Vanderpool support) in some areas.

The fact that I seem to have prior art for their 'killer technology' I 
just find kind of funny ;-)

Jacob


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  reply	other threads:[~2005-02-16 22:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-16 22:05 Xen and VMware Tom Hibbert
2005-02-16 22:50 ` Jacob Gorm Hansen [this message]
2005-02-17  2:40   ` aq
2005-02-17  3:01     ` Jacob Gorm Hansen
2005-02-17  9:14   ` Steven Hand
2005-02-17  9:36     ` Jacob Gorm Hansen
2005-02-17 15:51     ` Ronald G. Minnich
2005-02-17 16:32       ` B.G. Bruce
  -- strict thread matches above, loose matches on Subject: below --
2005-02-16 15:08 Tim Freeman

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=4213CE2F.9040300@diku.dk \
    --to=jacobg@diku.dk \
    --cc=tfreeman@mcs.anl.gov \
    --cc=tom@nsp.co.nz \
    --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.