From: "Yuzhong Sun" <yuzhongsun@ict.ac.cn>
To: 'Vincent Hanquez' <tab@snarc.org>
Cc: xen-devel@lists.xensource.com
Subject: 答复: [Xen-devel] Kernel 2.4?
Date: Fri, 19 May 2006 23:11:34 +0800 [thread overview]
Message-ID: <009001c67b56$842f8af0$9929e29f@IBMSYZH> (raw)
In-Reply-To: <20060519135853.GA10674@snarc.org>
[-- Attachment #1.1: Type: text/plain, Size: 1115 bytes --]
In fact, we are trying to build a virtual cluster on a set of VMs on top of
Xen. OpenMosix or Open SSI are available open-source cluster management
tools. Do you know the better guys?
Thanks
-Yuzhong
-----邮件原件-----
发件人: Vincent Hanquez [mailto:tab@snarc.org]
发送时间: 2006年5月19日 21:59
收件人: Yuzhong Sun
抄送: xen-devel@lists.xensource.com
主题: Re: [Xen-devel] Kernel 2.4?
On Fri, May 19, 2006 at 09:46:19PM +0800, Yuzhong Sun wrote:
> I am porting OpenMosix on top of Xen. However, the stable release of
> openMosix is based on Linux Kernel 2.4(They are trying to port it to
kernel
> 2.6).
There's lots more work to port 2.4 kernels to Xen-3, than to finish 2.6
openmosix. Now you could just use Xen-2, which support 2.4 kernels.
Patching 2.4 kernel on Xen2 with openmosix should be trivial.
> I wonder why Xen didn't support the lower kernel version such as 2.4
kernel.
> There is some open sources based on kernel 2.4.
I wouldn't count openmosix-2.4 as a good source here ...
--
Vincent Hanquez
[-- Attachment #1.2: Type: text/html, Size: 7056 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2006-05-19 15:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-19 13:46 Kernel 2.4? Yuzhong Sun
2006-05-19 13:58 ` Vincent Hanquez
2006-05-19 15:11 ` Yuzhong Sun [this message]
2006-05-19 15:35 ` 答复: [Xen-devel] " Ronald G Minnich
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='009001c67b56$842f8af0$9929e29f@IBMSYZH' \
--to=yuzhongsun@ict.ac.cn \
--cc=tab@snarc.org \
--cc=xen-devel@lists.xensource.com \
/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.