From: Jacob Gorm Hansen <jacobg@diku.dk>
To: "Ronald G. Minnich" <rminnich@lanl.gov>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: Xen as a kernel module
Date: Fri, 28 Jan 2005 15:29:11 -0800 [thread overview]
Message-ID: <41FACAC7.9060502@diku.dk> (raw)
In-Reply-To: <Pine.LNX.4.58.0501281626050.26402@enigma.lanl.gov>
Ronald G. Minnich wrote:
>
> Adam sulmicki is doing testing of that type of thing now, and we should
> have some results in a few weeks on a dual-xeon cluster of about 128
> nodes.Part of that will involve a virtual Plan 9 cluster as well on the
> same hardware. You just gotta love Xen.
I do love Xen. Not to worry ;-)
Jacob
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
next prev parent reply other threads:[~2005-01-28 23:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 2:34 Xen as a kernel module Neugebauer, Rolf
2005-01-26 3:12 ` Jacob Gorm Hansen
2005-01-26 7:55 ` Keir Fraser
2005-01-27 13:24 ` Mark Williamson
2005-01-28 20:59 ` Ronald G. Minnich
2005-01-28 23:16 ` Jacob Gorm Hansen
2005-01-28 23:26 ` Ronald G. Minnich
2005-01-28 23:29 ` Jacob Gorm Hansen [this message]
2005-01-29 2:15 ` Adam Sulmicki
2005-01-26 3:57 ` Ronald G. Minnich
-- strict thread matches above, loose matches on Subject: below --
2005-01-26 11:41 Ian Pratt
2005-01-26 1:24 Jacob Gorm Hansen
2005-01-26 1:32 ` Kip Macy
2005-01-26 1:59 ` Jacob Gorm Hansen
2005-01-26 4:30 ` Ronald G. Minnich
2005-01-26 8:41 ` Steven Hand
2005-01-26 23:19 ` Jacob Gorm Hansen
2005-01-27 15:05 ` Tobias Hunger
2005-01-28 18:32 ` Mark Williamson
2005-01-28 20:09 ` Jacob Gorm Hansen
2005-01-27 13:30 ` Mark Williamson
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=41FACAC7.9060502@diku.dk \
--to=jacobg@diku.dk \
--cc=rminnich@lanl.gov \
--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.