This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Xen+coLinux

To: Jacob Gorm Hansen <jacob@xxxxxxxx>
Subject: Re: [Xen-devel] Xen+coLinux
From: "Digital Infra, Inc." <okajima@xxxxxxxxxxxxxxxxxx>
Date: Thu, 15 Apr 2004 23:18:16 +0900
Cc: Dan Aloni <da-x@xxxxxxxxxxx>, Xen list <xen-devel@xxxxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 15 Apr 2004 15:27:48 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: <1081852170.15566.15.camel@jacobg>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
References: <1081852170.15566.15.camel@jacobg>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
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.

This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>