From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Sander Eikelenboom" <linux@eikelenboom.it>,
"Pasi Kärkkäinen" <pasik@iki.fi>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: problem using compiled kernel -- Sisu
Date: Tue, 10 Aug 2010 08:36:02 +0100 [thread overview]
Message-ID: <C886BFF2.1D402%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <764975280.20100802152155@eikelenboom.it>
On 02/08/2010 14:21, "Sander Eikelenboom" <linux@eikelenboom.it> wrote:
> Hi Keir,
>
> I haven't got a machine with xen-unstable nor grub2 at the moment.
> Perhaps Pasi has and could test it ?
If someone can test it this week then it can go in the next release
candidate for 4.0.1.
K.
> --
> 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@eikelenboom.it> 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-inform
>>> at
>>> 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@iki.fi> 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@lists.xensource.com
>>>>> http://lists.xensource.com/xen-devel
>>>
>>>
>>>
>>>
>>>
>>>
>
>
>
>
next prev parent reply other threads:[~2010-08-10 7:36 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 21:57 problem using compiled kernel -- Sisu Sisu Xi
2010-07-27 2:02 ` Jeremy Fitzhardinge
2010-07-27 2:13 ` Sisu Xi
[not found] ` <AANLkTimOUJLndxscJW5CehXYYe0gWUFqsc8PSxewFpAM@mail.gmail.com>
2010-07-27 3:05 ` Jeremy Fitzhardinge
2010-07-27 3:08 ` Sisu Xi
[not found] ` <AANLkTimoL+A=nX7+zqY6+LVuzgNKGrW8eyaJTtS_NqFK@mail.gmail.com>
2010-07-27 17:05 ` Jeremy Fitzhardinge
2010-07-27 17:52 ` Sisu Xi
2010-07-27 19:01 ` Jeremy Fitzhardinge
2010-07-27 19:19 ` Sisu Xi
2010-07-27 20:23 ` Konrad Rzeszutek Wilk
2010-07-27 20:37 ` Pasi Kärkkäinen
2010-07-27 21:09 ` Keir Fraser
2010-07-27 21:59 ` Sander Eikelenboom
2010-07-28 7:49 ` Keir Fraser
2010-07-28 16:53 ` Sisu Xi
2010-07-28 17:49 ` Konrad Rzeszutek Wilk
2010-07-28 22:14 ` Sisu Xi
2010-07-30 0:29 ` Sisu Xi
2010-07-30 0:35 ` Jeremy Fitzhardinge
2010-07-30 0:40 ` Sisu Xi
2010-07-30 17:47 ` Sisu Xi
2010-07-30 21:20 ` Sisu Xi
2010-07-30 21:21 ` Sisu Xi
2010-07-30 21:25 ` Sisu Xi
2010-08-02 16:54 ` Jeremy Fitzhardinge
2010-08-02 18:02 ` Sisu Xi
2010-08-03 3:25 ` Sisu Xi
2010-08-03 6:23 ` Keir Fraser
2010-08-03 17:01 ` Jeremy Fitzhardinge
2010-08-04 14:24 ` Konrad Rzeszutek Wilk
2010-08-04 17:55 ` Sisu Xi
2010-08-04 19:06 ` Konrad Rzeszutek Wilk
2010-08-04 19:12 ` Sisu Xi
2010-08-02 14:49 ` Konrad Rzeszutek Wilk
2010-08-02 15:24 ` Jeremy Fitzhardinge
2010-08-02 15:29 ` Konrad Rzeszutek Wilk
2010-08-02 15:37 ` Jeremy Fitzhardinge
2010-08-02 15:48 ` Sisu Xi
2010-08-02 16:02 ` Konrad Rzeszutek Wilk
2010-08-02 14:44 ` Konrad Rzeszutek Wilk
2010-08-02 15:58 ` Jean-Yves Landry
2010-08-02 13:21 ` Sander Eikelenboom
2010-08-10 7:36 ` Keir Fraser [this message]
2010-08-10 9:57 ` Xen Grub2 testing needed Pasi Kärkkäinen
2010-08-10 14:27 ` problem using compiled kernel -- Sisu Sander Eikelenboom
2010-08-10 14:41 ` Keir Fraser
2010-07-28 4:51 ` Mike Viau
2010-07-27 6:09 ` Pasi Kärkkäinen
2010-07-27 16:26 ` Sisu Xi
2010-07-27 20:27 ` Pasi Kärkkäinen
2010-08-03 11:04 ` Stefan Kuhne
2010-08-03 20:37 ` (XEN) d0:v0: unhandled page fault (ec=0009) Stefan Kuhne
2010-08-03 22:15 ` Jeremy Fitzhardinge
2010-08-03 22:22 ` Stefan Kuhne
2010-08-03 22:37 ` Jeremy Fitzhardinge
2010-08-04 5:58 ` Stefan Kuhne
2010-08-04 8:45 ` Stefan Kuhne
2010-08-04 14:09 ` Konrad Rzeszutek Wilk
2010-08-04 15:46 ` Stefan Kuhne
2010-08-04 20:12 ` Stefan Kuhne
2010-08-06 14:49 ` Konrad Rzeszutek Wilk
2010-08-06 14:50 ` Konrad Rzeszutek Wilk
2010-08-06 20:12 ` Stefan Kuhne
2010-08-09 4:41 ` Konrad Rzeszutek Wilk
2010-08-09 7:06 ` Stefan Kuhne
2010-08-10 8:15 ` Stefan Kuhne
2010-08-13 15:24 ` Stefan Kuhne
2010-08-06 9:10 ` Stefan Kuhne
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C886BFF2.1D402%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=linux@eikelenboom.it \
--cc=pasik@iki.fi \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).