Re: Strange interaction from grub2 and XEN

Re: Strange interaction from grub2 and XEN

[Marco Nenciarini]

Marco Nenciarini ha scritto:
> Boris Derzhavets ha scritto:
>> I switched etc/default/grub :
>> |   GRUB_DISABLE_LINUX_UUID=true
>> and ran:-
>> # update-grub
>> Compiled pvops kernel with built in command line:-
>>    root=/dev/sda(x) ro console=tty0
> 
> This is a workaround, like my dummy argument.
> 
> I'm looking for a real solution, as find where is the problem and a 
> proper correction, or a rationale that explain what I'm doing wrong.
> 
> Kind regards,
> Marco
> 

I finally found the the root cause of this issue on grub-devel mailing list.

http://lists.gnu.org/archive/html/grub-devel/2009-08/msg00001.html

Now I wonder if there is any chance to make the xen hypervisor aware of 
this behavior change in grub2.

Kind regards,
Marco

-- 
---------------------------------------------------------------------
|    Marco Nenciarini    | Debian/GNU Linux Developer - Plug Member |
| mnencia@prato.linux.it | http://www.prato.linux.it/~mnencia       |
---------------------------------------------------------------------
Key fingerprint = FED9 69C7 9E67 21F5 7D95  5270 6864 730D F095 E5E4

Re: Re: [Xen-users] Strange interaction from grub2 and XEN

[Keir Fraser]

On 23/11/2009 16:20, "Marco Nenciarini" <mnencia@prato.linux.it> wrote:

>> I'm looking for a real solution, as find where is the problem and a
>> proper correction, or a rationale that explain what I'm doing wrong.
> 
> I finally found the the root cause of this issue on grub-devel mailing list.
> 
> http://lists.gnu.org/archive/html/grub-devel/2009-08/msg00001.html
> 
> Now I wonder if there is any chance to make the xen hypervisor aware of
> this behavior change in grub2.

So they've stopped passing the kernel name as a first element of the command
line, but haven't allocated a new flag or anything to indicate that new
behaviour? What are we supposed to do to detect it and act on it?

 -- Keir

Re: Re: [Xen-users] Strange interaction from grub2 and XEN

[Keir Fraser]

On 24/11/2009 17:11, "Keir Fraser" <keir.fraser@eu.citrix.com> wrote:

>> Now I wonder if there is any chance to make the xen hypervisor aware of
>> this behavior change in grub2.
> 
> So they've stopped passing the kernel name as a first element of the command
> line, but haven't allocated a new flag or anything to indicate that new
> behaviour? What are we supposed to do to detect it and act on it?

Looks like you're supposed to provide your own dummy first arg, like a '.'
or something, if booting something that assumes first arg is the kernel
name. Seems pretty stupid and unnecessary to change the behaviour I must
say. GRUB sucks.

 -- Keir