From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jacob Gorm Hansen Subject: Re: Xen+coLinux Date: Tue, 13 Apr 2004 12:29:30 +0200 Sender: xen-devel-admin@lists.sourceforge.net Message-ID: <1081852170.15566.15.camel@jacobg> References: <200403191229.AA00764@winxp.digitalinfra.co.jp> <1079708498.24177.1.camel@jacobg> <20040409191000.GA21745@callisto.yi.org> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20040409191000.GA21745@callisto.yi.org> Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Dan Aloni Cc: "Digital Infra, Inc." , Xen list List-Id: xen-devel@lists.xenproject.org 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. Jacob ------------------------------------------------------- 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 administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click