WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-api

Re: [Xen-API] grub/cmdline

To: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Subject: Re: [Xen-API] grub/cmdline
From: Jim Fehlig <jfehlig@xxxxxxxxxx>
Date: Wed, 15 Nov 2006 18:08:27 -0700
Cc: Tim Deegan <Tim.Deegan@xxxxxxxxxxxxx>, xen-api@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 15 Nov 2006 17:10:48 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20061115214405.GA5524@xxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
References: <20061115201059.GB7078@xxxxxxxxxxxxxxxxx> <20061115214405.GA5524@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.8 (X11/20061025)
Ewan Mellor wrote:
[Bringing Tim into the conversation]

On Wed, Nov 15, 2006 at 08:10:59PM +0000, John Levon wrote:

What are grub/cmdline's semantics? It appears to be undocumented.

I'm trying to work out what changes are needed for the bootloader changes I'm
making. The current .py changes I'm making after discussion with Tim Deegan
are:
use_bootloader (new: if set, use a bootloader. == 1 is implied if bootloader is
set, or if kernel is not set)
bootloader/bootloader_args (as before, default to pygrub if use_bootloader is
set)

As far as I can work out, if boot_type is 'kernel_internal', then this
corresponds to setting use_bootloader to 1. It's not clear how
bootloader_args is represented in the API - is it?

Currently it seems that 'bootloader' is returned when get_boot_method is
called, but the API docs says it's an enum of boot_type? Well actually it
returns '' now.

I was looking at this again just the other day.  Here's where I got to --
let's see how it fits in with what you've got:


vm has three mutually exclusive groups: "grub", "external", and "hvm", with
the fields

vm.grub.cmdline

vm.external.kernel
vm.external.args
vm.external.initrd

vm.hvm.boot

Grub means "parse the grub config file inside the guest, and boot
appropriately".  grub.cmdline is _supposed_ to be a way of specifying "select
this particular label from the config file" or "append these parameters to the
kernel command line before you boot" or mixtures of the two.  Is that feasible
with one string?

External means "take the specified kernel from dom 0, and give it the given
args and initrd".

HVM means "run hvmloader and boot using a BIOS", with hvm.boot specifying the
order of boot devices.

Kernel_internal is unnecessary.

How does this fit with your thinking?

What about support for other boot loaders? SLES for example uses domUloader. How would this be specified? Although moving forward, particularly with the work John has been doing, I'm thinking we should just be using pygrub. Not sure why we were using domUloader anyway and the person with some context behind this decision is not available ATM.

Jim


_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-api