From: "Joel C. Salomon" <joelcsalomon@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Lguest (Was re: [9fans] Xen 3.1 w/ Plan 9 domU)
Date: Sun, 8 Jul 2007 15:43:03 -0400 [thread overview]
Message-ID: <7871fcf50707081243g532c9de7yc94a04e17c15c416@mail.gmail.com> (raw)
On 7/4/07, ron minnich <rminnich@gmail.com> wrote:
> folks, just FYI, for the THX project, I have looked hard and am fixing
> on the new lguest hypervisor as the final plan. Please google lguest
> and see what you think. It's 5K lines of code, the guest support code
> is trivial, and I think overall this is going to be the easiest thing
> to do. The work should actually not take too long this time. Xen can
> be hard to get your brain around.
Looks like a patch on the Linux kernel to run as a hypervisor. Is
that how you intend to run it, or are you planning on porting the code
to Plan 9, making p9 the hypervisor? Or am I totally misunderstanding
the blurbs on <http://lguest.ozlabs.org/>?
--Joel
next reply other threads:[~2007-07-08 19:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-08 19:43 Joel C. Salomon [this message]
2007-07-09 5:30 ` ron minnich
2007-07-10 7:05 ` lucio
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=7871fcf50707081243g532c9de7yc94a04e17c15c416@mail.gmail.com \
--to=joelcsalomon@gmail.com \
--cc=9fans@cse.psu.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).