All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Aloni <da-x@colinux.org>
To: Jacob Gorm Hansen <jacob@melon.dk>
Cc: "Digital Infra, Inc." <okajima@digitalinfra.co.jp>,
	Xen list <xen-devel@lists.sourceforge.net>
Subject: Re: Xen+coLinux
Date: Fri, 9 Apr 2004 22:10:00 +0300	[thread overview]
Message-ID: <20040409191000.GA21745@callisto.yi.org> (raw)
In-Reply-To: <1079708498.24177.1.camel@jacobg>

On Fri, Mar 19, 2004 at 04:01:38PM +0100, Jacob Gorm Hansen wrote:
> On Fri, 2004-03-19 at 13:29, Digital Infra, Inc. wrote:
> > 
> > Hello Xen team.
> > 
> > I think Xen and coLinux have similarity in its algorithm.
> > How about combining two technologies?
> > I mean, for example, making XEN.SYS - which makes WindowsXP/2K as Xen host.
> > (coLinux has LINUX.SYS, which makes Windows as coLinux host.)
> 
> > The poing is, you can do it by "live migration".
> > you dont have to stop your VM.
> 
> I am currently working on live migration in Xen. I agree that getting
> Xen to run within/alongside Windows would be extremely useful. Are you
> involved with the coLinux project?

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.

-- 
Dan Aloni
da-x@colinux.org


-------------------------------------------------------
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

  parent reply	other threads:[~2004-04-09 19:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-19 12:29 Xen+coLinux Digital Infra, Inc.
2004-03-19 12:40 ` Xen+coLinux Digital Infra, Inc.
2004-03-19 15:01 ` Xen+coLinux Jacob Gorm Hansen
2004-03-19 15:28   ` Xen+coLinux Digital Infra, Inc.
2004-04-09 19:10   ` Dan Aloni [this message]
2004-04-10 12:49     ` Xen+coLinux Steven Hand
2004-04-13 10:29     ` Xen+coLinux Jacob Gorm Hansen
2004-04-15 14:18       ` Xen+coLinux Digital Infra, Inc.
2004-04-27 17:04       ` Xen+coLinux / terminology Digital Infra, Inc.
2004-04-28 18:00         ` Brian Wolfe
2004-04-28 18:14           ` Ian Pratt
2004-04-27 17:08       ` Xen+coLinux / coXen Digital Infra, Inc.
2004-04-27 17:25         ` Jacob Gorm Hansen
2004-04-27 17:34           ` Digital Infra, Inc.
2004-04-27 17:35           ` Digital Infra, Inc.
2004-06-08  0:11             ` pdb entered even when set to none Kip Macy
2004-06-08  7:39               ` Alex Ho

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040409191000.GA21745@callisto.yi.org \
    --to=da-x@colinux.org \
    --cc=jacob@melon.dk \
    --cc=okajima@digitalinfra.co.jp \
    --cc=xen-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.