From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Dan Magenheimer" Subject: RE: PVM guests and p[yv]grub and the extra= parameter Date: Wed, 16 Jul 2008 06:35:47 -0600 Message-ID: <20080716063547328.00000080236@djm-pc> References: <20080715221833578.00000080236@djm-pc> Reply-To: "dan.magenheimer@oracle.com" Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20080715221833578.00000080236@djm-pc> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "dan.magenheimer@oracle.com" , Samuel Thibault Cc: "Xen-Devel (E-mail)" List-Id: xen-devel@lists.xenproject.org > > 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. 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? It would be neat if you could put in the vm config file something like (as a contrived example): bootconfig=3D" default=3D0 timeout=3D10 title Linux 2.6.25 kernel /vmlinuz-2.6.25 ro root=3Dxxx initrd /initrd-2.6.25.img title Linux 2.6.25 kernel /vmlinuz-2.6.25 ro root=3Dxxx debug initrd /initrd-2.6.25.img " Then you could just tell a customer to change default=3D0 to default=3D1, or change debug to, for example, clock=3Dpit, or whatever. Thanks, Dan