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

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

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
From:	Digital Infra, Inc. (okaj...@digitalinfra.co.jp)
Date:	04/15/2004 07:17:54 AM
List:	com.xensource.lists.xen-devel

Hello Aloni, Hansen.

I think coXenoLinux, which can run on both XEN and Windows, has its place. if it comes, we can make "multi host distribution" which same distribution can run on XEN and Windows and normal Linux. Good. and this hack would be not so difficult. good. good. but this way has one drawback - it is difficult to do "live migration" between XEN server and Windows , except you invent a very funny technic like "suspend image converter" or such.

So, yes, basically Hansen's opinion is right.

our ULTIMATE goal (not milestones on the development) should be adding these functionality to linux.sys/linux.ko. and making XEN gesut OS ( e.g. XenoLinux) runnable on Windows.

1. XEN API. I mean, linux.sys should accept both coLinux API and XEN API. 2. ring 1. using ring 1 has a little performance penalty, but it offers resource isolation which coLinux lacks and is the biggest ( and probably only) fault of coLinux as its fundamental algorithm. of course, linux.sys can accepct coLinux API, if you love performace, you can run your VM on ring0. the problem of current coLinux implementation is, you have to choose only performance and never security.

and if these two functionality comes, I think we can do "live migration" between Windows PC and virtual server.

I believe that someday this new computing style is possible.

when we go out, we can migrate a VM from Windows desktop PC to virtual server on the net. of course, you dont shut it down. everything is done by "live". and we can use the VM from mobile phone with remote protocol like VNC. and when you go back, you bring the VM back to your PC.

dont you think this is very good?

--- Okajima.

On Fri, 2004-04-09 at 21:10, Dan Aloni wrote:

On Fri, Mar 19, 2004 at 04:01:38PM +0100, Jacob Gorm Hansen wrote:

According to what I understand, a machine running Xen, runs using a Xen-patched Linux kernel, right? So, if the coLinux patch doesn't conflict much with the Xen patch, you'd be able to easily create a coXenoLinux that runs under Windows just like the regular coLinux does.

I think what you would do would be either a) revive the existing port of XP to run within Xen, or b) port Xen to run as a driver in ring0 just as coLinux does, and then run multiple XenoLinuxes on top of that. There is probably not much point in running XenoLinux without Xen.