xen-devel
[Xen-devel] Re: [RFC, PATCH 0/24] VMI i386 Linux virtualization interfac
To: |
Joshua LeVasseur <jtl@xxxxxxxxxx> |
Subject: |
[Xen-devel] Re: [RFC, PATCH 0/24] VMI i386 Linux virtualization interface proposal |
From: |
Andrew Morton <akpm@xxxxxxxx> |
Date: |
Wed, 15 Mar 2006 12:02:57 -0800 |
Cc: |
zach@xxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, pratap@xxxxxxxxxx, wim.coekaerts@xxxxxxxxxx, chrisw@xxxxxxxx, jlo@xxxxxxxxxx, dhecht@xxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, jbeulich@xxxxxxxxxx, chrisl@xxxxxxxxxx, hch@xxxxxxxxxxxxx, virtualization@xxxxxxxxxxxxxx, torvalds@xxxxxxxx, leendert@xxxxxxxxxxxxxx, anne@xxxxxxxxxx, jreddy@xxxxxxxxxx, kmacy@xxxxxxxxxxx, ksrinivasan@xxxxxxxxxx, arai@xxxxxxxxxx, arjan@xxxxxxxxxxxxx |
Delivery-date: |
Fri, 17 Mar 2006 10:33:46 +0000 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
In-reply-to: |
<F032F3F4-00DB-43AF-A67B-E82673883303@xxxxxxxxxx> |
List-help: |
<mailto:xen-devel-request@lists.xensource.com?subject=help> |
List-id: |
Xen developer discussion <xen-devel.lists.xensource.com> |
List-post: |
<mailto:xen-devel@lists.xensource.com> |
List-subscribe: |
<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
List-unsubscribe: |
<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
References: |
<200603131758.k2DHwQM7005618@xxxxxxxxxxxxxxxxxxx> <1142273346.3023.38.camel@xxxxxxxxxxxxxxxxxxxxx> <4415B857.9010902@xxxxxxxxxx> <20060315102522.GA5926@xxxxxxxxxxxxx> <F032F3F4-00DB-43AF-A67B-E82673883303@xxxxxxxxxx> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
Joshua LeVasseur <jtl@xxxxxxxxxx> wrote:
>
> As part of our pre-virtualization work, we developed a virtualization
> solution similar to VMI. We support Xen v2 and v3 with high
> performance. We added support for the first generation of VMI to our
> project, and are currently adding support for the latest VMI patch.
> Our work is open source. We'll announce when we finish the VMI updates.
Who is "we" and what product are you referring to?
(I think an important part of this discussion is getting an understanding
of which virtualisation products (current or planned) could use a VMI).
Thanks.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] Re: [RFC, PATCH 0/24] VMI i386 Linux virtualization interface proposal, (continued)
- [Xen-devel] VMI interface documentation, Zachary Amsden
- [Xen-devel] Re: [RFC, PATCH 0/24] VMI i386 Linux virtualization interface proposal, Joshua LeVasseur
- [Xen-devel] Re: [RFC, PATCH 0/24] VMI i386 Linux virtualization interface proposal, Jan Engelhardt
- [Xen-devel] Re: [RFC, PATCH 0/24] VMI i386 Linux virtualization interface proposal, Christoph Hellwig
- [Xen-devel] Re: [RFC, PATCH 0/24] VMI i386 Linux virtualization interface proposal, Zachary Amsden
- [Xen-devel] Re: [RFC, PATCH 0/24] VMI i386 Linux virtualization interface proposal, Joshua LeVasseur
- [Xen-devel] Re: [RFC, PATCH 0/24] VMI i386 Linux virtualization interface proposal,
Andrew Morton <=
- [Xen-devel] Re: [RFC, PATCH 0/24] VMI i386 Linux virtualization interface proposal, Joshua LeVasseur
[Xen-devel] Re: [RFC, PATCH 0/24] VMI i386 Linux virtualization interface proposal, Sam Vilain
[Xen-devel] Re: [RFC, PATCH 0/24] VMI i386 Linux virtualization interface proposal, Anthony Liguori
[Xen-devel] Re: [RFC, PATCH 0/24] VMI i386 Linux virtualization interface proposal, Anthony Liguori
|
|
|