From: Anthony Liguori <aliguori@us.ibm.com>
To: Jacob Gorm Hansen <jacobg@diku.dk>
Cc: xen-devel@lists.xensource.com
Subject: Re: VMWare standards
Date: Tue, 31 Jan 2006 10:03:40 -0600 [thread overview]
Message-ID: <43DF8A5C.9020506@us.ibm.com> (raw)
In-Reply-To: <e08041f30601310224v89f0196ob5ff1bd4782ce2eb@mail.gmail.com>
Jacob Gorm Hansen wrote:
>hi,
>
>Sorry if this is old news, but it seems some of the larger players,
>lead by VMWare, are trying to define a standard for paravirtualized
>VMM's, see:
>
>http://www.vmware.com/standards/
>
>
VMware first brought this up last year during OLS. There has been
patches floating to the osdl-virtualization list.
>Should the Xen community be part of this effort?
>
>
So far there hasn't been any real public discussion (AFAIK) about VMI.
There certainly are merits to it but I'm not convinced that those merits
justify major changes in Xen. Also, since they already support this in
their product, I'm not sure how much the spec is up for discussion and
there definitely are some key aspects that I'd like to see change (for
instance, reliance on PCI bus emulation for device discovery).
I'd be really interested to here what the Cambridge guys thought about
it (or anyone else for that matter).
Regards,
Anthony Liguori
>Jacob
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com
>http://lists.xensource.com/xen-devel
>
>
>
next prev parent reply other threads:[~2006-01-31 16:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-31 10:24 VMWare standards Jacob Gorm Hansen
2006-01-31 12:12 ` Hans-Joerg Hoexer
2006-01-31 12:18 ` Jacob Gorm Hansen
2006-01-31 12:25 ` Hans-Joerg Hoexer
2006-01-31 16:03 ` Anthony Liguori [this message]
2006-01-31 17:01 ` Anthony Liguori
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=43DF8A5C.9020506@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=jacobg@diku.dk \
--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.