All of lore.kernel.org
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@eu.citrix.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: "Xen-Devel (E-mail)" <xen-devel@lists.xensource.com>
Subject: Re: PVM guests and p[yv]grub and the extra= parameter
Date: Wed, 16 Jul 2008 13:52:58 +0100	[thread overview]
Message-ID: <20080716125258.GP4715@implementation.uk.xensource.com> (raw)
In-Reply-To: <20080716063547328.00000080236@djm-pc>

Dan Magenheimer, le Wed 16 Jul 2008 06:35:47 -0600, a écrit :
> > > Another possibility would be to provide the menu.lst as a 
> > ramdisk.  We
> > > keep the confinment of grub inside the domain, but still 
> > provide full
> > > configurability.
> > 
> > That's a neat solution.  Still not as clean as an extra=
> > vm.cfg parameter though.  (Think about instructing a novice
> > user over the phone how to construct a grub.conf file from
> > scratch!)  But it's much better than the other alternatives.
> 
> Thinking about this a bit more, were you thinking about
> thh vm config file providing a file name on the dom0
> filesystem?  Or providing the entire menu.lst file in
> the vm config file.  Or either?

The latter.

> It would be neat if you could put in the vm config file
> something like (as a contrived example):
> 
> bootconfig="
> default=0
> timeout=10
> title Linux 2.6.25
> 	kernel /vmlinuz-2.6.25 ro root=xxx
>       initrd /initrd-2.6.25.img
> title Linux 2.6.25
> 	kernel /vmlinuz-2.6.25 ro root=xxx debug
>       initrd /initrd-2.6.25.img
> "
> 
> Then you could just tell a customer to change
> default=0 to default=1, or change debug to,
> for example, clock=pit, or whatever.

You can obtain that by putting that into a dom0 file and referencing it
from the ramdisk option (the name becomes a bit unfortunate...)

Samuel

      reply	other threads:[~2008-07-16 12:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-02 17:17 PVM guests and p[yv]grub and the extra= parameter Dan Magenheimer
2008-07-02 17:22 ` Keir Fraser
2008-07-02 17:29 ` Samuel Thibault
2008-07-02 17:42   ` Dan Magenheimer
2008-07-16  1:28     ` Samuel Thibault
2008-07-16  4:18       ` Dan Magenheimer
2008-07-16 11:24         ` [PATCH] " Samuel Thibault
2008-07-16 12:35         ` Dan Magenheimer
2008-07-16 12:52           ` Samuel Thibault [this message]

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=20080716125258.GP4715@implementation.uk.xensource.com \
    --to=samuel.thibault@eu.citrix.com \
    --cc=dan.magenheimer@oracle.com \
    --cc=xen-devel@lists.xensource.com \
    /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.