9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Xen 3.1 w/ Plan 9 domU: plan9.img file after install not
Date: Fri,  6 Jul 2007 14:21:58 +0100	[thread overview]
Message-ID: <643819421a900215d67f549ceb50512c@hamnavoe.com> (raw)
In-Reply-To: <13426df10707041026u4590977djebab5f1ed29751b7@mail.gmail.com>

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

I've just had a quick browse through (the patch is actually 8977 lines,
but maybe the 5k doesn't include comments).  My first impression is
"that's more like it".  Way simpler.

But:

- Does some of the simplicity come from being linux-specific?  Comments
say "guest and host run the same kernel".  Or is it generic enough to
work with Plan 9 too?

- My interest in Xen is pragmatic: there are plenty of hosting companies
offering "virtual servers" based on Xen, and some at least are happy
to let you run a Plan 9 guest kernel.  (In particular I can recommend
http://www.blackcatnetworks.co.uk from personal experience.)  How long
before lguest reaches that level of maturity?  Sadly, simplicity in
itself is not much of a marketing advantage in the real world.

-- Richard



  reply	other threads:[~2007-07-06 13:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-04 16:40 [9fans] Xen 3.1 w/ Plan 9 domU: plan9.img file after install not recognized Mike
2007-07-04 17:05 ` [9fans] Xen 3.1 w/ Plan 9 domU: plan9.img file after install not Richard Miller
2007-07-04 17:26   ` ron minnich
2007-07-06 13:21     ` Richard Miller [this message]
2007-07-06 14:43       ` ron minnich
2007-07-06 15:03         ` Richard Miller
2007-07-04 23:07   ` Mike
2007-07-05  7:01     ` ron minnich
2007-07-05 14:17       ` Mike
2007-07-05  8:39     ` Richard Miller
2007-07-05 14:11       ` Mike

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=643819421a900215d67f549ceb50512c@hamnavoe.com \
    --to=9fans@hamnavoe.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).