Re: [Xen-devel] Xen+coLinux / coXen - Digital Infra, Inc. - com.xensource.lists.xen-devel

16 messages in com.xensource.lists.xen-develRe: [Xen-devel] Xen+coLinux / coXen

From	Sent On	Attachments
Digital Infra, Inc.	19 Mar 2004 04:29
Digital Infra, Inc.	19 Mar 2004 04:40
Jacob Gorm Hansen	19 Mar 2004 07:01
Digital Infra, Inc.	19 Mar 2004 07:27
Dan Aloni	09 Apr 2004 12:09
Steven Hand	10 Apr 2004 05:49
Jacob Gorm Hansen	13 Apr 2004 03:29
Digital Infra, Inc.	15 Apr 2004 07:17
Digital Infra, Inc.	27 Apr 2004 10:04
Digital Infra, Inc.	27 Apr 2004 10:07
Jacob Gorm Hansen	27 Apr 2004 10:24
Digital Infra, Inc.	27 Apr 2004 10:34
Digital Infra, Inc.	27 Apr 2004 10:35
Brian Wolfe	28 Apr 2004 10:59
Ian Pratt	28 Apr 2004 11:13
Kip Macy	07 Jun 2004 17:11

Subject:	Re: [Xen-devel] Xen+coLinux / coXen
From:	Digital Infra, Inc. (okaj...@digitalinfra.co.jp)
Date:	04/27/2004 10:07:59 AM
List:	com.xensource.lists.xen-devel

Hello Aloni, Hansen.

a lecture of terminology ended. so far is Okay? and we can go to actual discussion.

I had been browsing the Xen code and I found that it is not so difficult to combine Xen( not Xeno) and coLinux. I call it coXen as a working title. In other words, Xen can run on Windows and unmodified Linux with a little hack. this means you have four layers.

coXen architecture overview:

----------------------------------------------------------------------- Apps | guest (Xeno) | hacked Xen (coXen) | linux.sys/ko | real host

-----------------------------------------------------------------------

this architecture increase an overhead comparing from normal Xen, but I estimate that it is not serious. because most overhead of coLinux comes from virtual I/O, but Xen already suffers from it.

and the biggest point is, I think this can make very same suspending image as normal Xen.

and this hack adds isolation. it can solve only fundamental problem of coLinux -- it lacks isolation between VMs.

is this really possible?, everyone. I hope your opinion.

--- Okajima.