From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Dan Magenheimer" <dan.magenheimer@oracle.com>
Subject: RE: PVM guests and p[yv]grub and the extra= parameter
Date: Tue, 15 Jul 2008 22:18:33 -0600
Message-ID: <20080715221833578.00000080236@djm-pc>
References: <20080716012804.GH5288@implementation>
Reply-To: "dan.magenheimer@oracle.com" <dan.magenheimer@oracle.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <20080716012804.GH5288@implementation>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Samuel Thibault <samuel.thibault@eu.citrix.com>
Cc: "Xen-Devel (E-mail)" <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

> > > Instead, would for instance being able to set the menu
> > > entry to be activated by default be ok?
> >
> > That would be nice too, but doesn't replace the niceness
> > of being able to alter the booting behavior of a pv guest
> > without ever mucking with grub interactive edits or grub
> > configuration files.
> =

> 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=3D
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.

Dan