Hi Keir,
I haven't got a machine with xen-unstable nor grub2 at the moment.
Perhaps Pasi has and could test it ?
--
Sander
Wednesday, July 28, 2010, 9:49:42 AM, you wrote:
> 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.
> Thanks,
> Keir
> 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
>>
>>
>>
>>
>>
>>
--
Best regards,
Sander mailto:linux@xxxxxxxxxxxxxx
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home