All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: "Jan Kundrát" <jan.kundrat@fzu.cz>,
	"Jeremy Katz" <katzj@redhat.com>,
	"Andy Whitcroft" <apw@shadowen.org>,
	xen-devel@lists.sourceforge.net
Subject: Re: [PATCH] Xen Grub-style boot loader
Date: Thu, 03 Feb 2005 17:37:10 -0600	[thread overview]
Message-ID: <4202B5A6.4010501@us.ibm.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D1236F2@liverpoolst.ad.cl.cam.ac.uk>

Ian Pratt wrote:

>I think to be useful this would need to run within the guest domain such that the grub menu appeared over the guest console connection. We'd have to use something akin to a real bootloader (but 32bit) to pull in the image and jump at it. Using linux with a suitable initrd and kexec might be a good soloution.
>  
>
Making the console appear over the guest connection isn't hard while 
still having the boot loader be a dom0 process.  It's particularly easy 
if you make the console visible as a tty.  In the current Xend 
architecture, you would just dup the socket as the std(in|out) of the 
process and exec the boot loader before starting the domain.

I think the only real advantage to having it be a part of domain-U is 
that you avoid the problem with mounting a file system.  The more I 
think about it though the more of a security concerns worry me.  Long 
term, I think a domU loader is a better solution.  However, I think 
there's a large class of users where a dom0 boot loader would be just fine.

>I'm not sure that the interactive selection of kernels is the #1 requirement here -- I think its more about being able to read the kernel from the domain's file system, and to be able to control the command line options. 
>  
>
It's definitely not the #1 requirement but it's certainly useful.  You 
don't really need a boot loader to read the kernel from the domain's 
file system or to give the user the ability to control the command line.

Would you being willing to accept a boot loader that ran as a dom0 
process and exported it's screen through the console?  Even if it was 
only a temporary solution until a better boot loader was written?  I ask 
because I can probably code up the rest (I already can read the 
grub.conf off of a specified device) by tonight or tomorrow.

I think it would take more time than I could invest to do the dom0 
approach any time soon.  Unless of course someone else is willing to do 
it in which case I agree that the dom0 approach is superior :-)

Regards,
Anthony Liguori

>Ian
>
>  
>



-------------------------------------------------------
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-03 23:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-03 23:12 [PATCH] Xen Grub-style boot loader Ian Pratt
2005-02-03 23:30 ` Jacob Gorm Hansen
2005-02-03 23:37 ` Anthony Liguori [this message]
2005-02-04  3:13   ` Jeremy Katz
  -- strict thread matches above, loose matches on Subject: below --
2005-02-03 17:28 boot loaders for domain != 0 Ian Pratt
2005-02-03 19:32 ` Jan Kundrát
2005-02-03 20:57   ` [PATCH] Xen Grub-style boot loader Anthony Liguori
2005-02-03 23:58     ` Anthony Liguori

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=4202B5A6.4010501@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=apw@shadowen.org \
    --cc=jan.kundrat@fzu.cz \
    --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.