All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: Jacob Gorm Hansen <jacobg@diku.dk>,
	xen-devel@lists.sourceforge.net, katzj@redhat.com
Subject: Re: Building domains as a lesser user (was Re: boot loaders for domain != 0)
Date: Thu, 03 Feb 2005 21:29:58 -0600	[thread overview]
Message-ID: <4202EC36.8000103@codemonkey.ws> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D1236FB@liverpoolst.ad.cl.cam.ac.uk>

Ian Pratt wrote:

>One fairly simple option is to use Linux as a domU boot loader. Boot
>with an intrd, 
>mount the specified filesystem, read off grub.conf, display a menu over
>the xencons, kexec the appropriate kernel.
>
>I'd have to think through whether kexec would need modifications, but I
>believe it uses the same 32 bit kernel entry point that xen/linux does
>(no grubby 16bit nastiness). 
>  
>
Yeah, I think kexec would work but unfortunately it's not part of the 
kernel yet.  It could be folded into Xen but I agree with Jeremy that it 
seems like overkill.  Boot through Linux just to get to a grub screen 
seems a little strange too.

Jacob's two-stage approach would work although it requires a lot of 
custom code.  It also makes it pretty difficult to support new types of 
loaders.  And you still have a point of failure with that "trusted" 
loader.  I don't think you ever really see a graphical boot using this 
approach either.  Getting a system going with xlibs working would 
basically put you back at the kexec() solution.

I've got the user-space boot loader working quite nicely.  I want to 
test at the systems in the office though so I'll post it sometime 
tomorrow.  In the very least, it can be used a data point.  It seems 
like a very appealing solution if the security concerns can be addressed.

Regards,

Anthony Liguori
anthony@codemonkey.ws



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

  parent reply	other threads:[~2005-02-04  3:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-04  2:30 Building domains as a lesser user (was Re: boot loaders for domain != 0) Ian Pratt
2005-02-04  3:09 ` Jeremy Katz
2005-02-04  5:13   ` Ronald G. Minnich
2005-02-04  3:29 ` Anthony Liguori [this message]
2005-02-04  3:38   ` Jacob Gorm Hansen
2005-02-04  3:54     ` Anthony Liguori
2005-02-04  4:02       ` Jacob Gorm Hansen
2005-02-04 19:49   ` Adam Sulmicki
  -- strict thread matches above, loose matches on Subject: below --
2005-02-04 12:33 Ian Pratt
2005-02-04 20:48 ` Anthony Liguori
2005-02-04  9:44 Ian Pratt
2005-02-03 22:11 boot loaders for domain != 0 Ian Pratt
2005-02-04  1:09 ` Jacob Gorm Hansen
2005-02-04  2:16   ` Building domains as a lesser user (was Re: boot loaders for domain != 0) Anthony Liguori
2005-02-04  3:12     ` Jacob Gorm Hansen
2005-02-04  3:16     ` Jacob Gorm Hansen
2005-02-04  3:34       ` Anthony Liguori
2005-02-04  3:56         ` Jacob Gorm Hansen

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=4202EC36.8000103@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=jacobg@diku.dk \
    --cc=katzj@redhat.com \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --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.