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/
Home Products Support Community News


Re: [Xen-devel] problem using compiled kernel -- Sisu

To: Sander Eikelenboom <linux@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] problem using compiled kernel -- Sisu
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Wed, 28 Jul 2010 08:49:42 +0100
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Sisu Xi <xisisu@xxxxxxxxx>
Delivery-date: Wed, 28 Jul 2010 00:50:50 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <82563368.20100727235927@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acst1wjI3jBZqxXMTMeOwavlT+DnxgAUmdYL
Thread-topic: [Xen-devel] problem using compiled kernel -- Sisu
User-agent: Microsoft-Entourage/
Ah yes, that could work. I applied a possible fix for GRUB2 handlign as
xen-unstable:21883. It works on the assumption that the loader name for
GRUB2 is of the form "GRUB 1.xx". I print out the loader name as one of the
first things during boot now, so it'd be good if someone could confirm that
the loader name does look like that, and that we now correctly handle GRUB2
command lines. Since I do not have GRUB2 installed.

If it works okay, I'll backport it for 4.0.1.


On 27/07/2010 22:59, "Sander Eikelenboom" <linux@xxxxxxxxxxxxxx> wrote:

> Don't know if the bootloader name in the multiboot specs contains the grub
> version number .. so it perhaps could be derived from there ?
> http://www.gnu.org/software/grub/manual/multiboot/multiboot.html#Boot-informat
> ion-format
> See flag 9
> --
> Sander
> Tuesday, July 27, 2010, 11:09:29 PM, you wrote:
>> On 27/07/2010 21:37, "Pasi Kärkkäinen" <pasik@xxxxxx> wrote:
>>>> what info are missing?
>>> You're missing the fact that grub2 is broken..
>>> Please read grub2 related entries from:
>>> http://wiki.xensource.com/xenwiki/XenCommonProblems
>> This is a tricky issue actually. Strictly it is Xen which throws away the
>> first parameter on each command line. This is because the Multiboot protocol
>> behaviour, as established by GRUB1, is that the command line passed to us
>> includes the name of the kernel binary (e.g. xen.gz loglvl=all sync_console)
>> and so we strip that off. But GRUB2 has arbitrarily changed behaviour to
>> only pass parameters in the command-line string. Hence lopping the first
>> item in the string actually lops a parameter. The workaround is to stick
>> something dummy as the first parameter, such as a period. This behaviour
>> change between GRUB1 and GRUB2 is a pain in the arse.
>>  -- Keir
>>>>>> (XEN) Command line: loglvl=all guest_loglvl=all sync_console
>>>>>> console_to_ring com1=115200,8n1 console=com1
>>> See, dom0_mem is missing from there..
>>> The same thing happens with dom0 kernel, you lose the first parameter
>>> (console=hvc0).
>>> -- Pasi
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>>> http://lists.xensource.com/xen-devel

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>