Perhaps we've got the grub.cfg syntax for specifying multiboot kernel/module
command-line options wrong. Unfortunately I can't find any documentation
describing what the syntax is for multiboot config entries.
On 30/08/2009 17:41, "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx> wrote:
> Mine should, if GRUB2 passes through Xen's command line.
> -- Keir
> On 30/08/2009 17:22, "Boris Derzhavets" <bderzhavets@xxxxxxxxx> wrote:
>> I've tested both options.
>> Chris's one works with Grub2, Keir's doesn't.
>> Distro Ubuntu 9.10 Server (alpha 4.)
>> --- On Sun, 8/30/09, Keir Fraser <keir.fraser@xxxxxxxxxxxxx> wrote:
>>> From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
>>> Subject: Re: [Xen-devel] Re: Failure to setup Xen 3.4.1 Dom0 on top of
>>> 9.10 Server HVM DomU ( 184.108.40.206 xenified kernel)
>>> To: "Christian Tramnitz" <chris.ace@xxxxxxx>,
>>> Date: Sunday, August 30, 2009, 11:50 AM
>>> On 30/08/2009 14:26, "Christian Tramnitz" <chris.ace@xxxxxxx
>>> </mc/compose?to=chris.ace@xxxxxxx> > wrote:
>>>> Afaik grub2 does not pass the boot parameters "root=/dev/sda2 ro
>>>> console=tty0" to the kernel in multiboot/module combination. I have seen
>>>> the same problem on gentoo/grub2 and also read about this before. (This
>>>> is not really Xen specific, but multiboot related).
>>> Okay, that would clearly be a GRUB regression I think. But there is a simple
>>> enough less ugly workaround than you suggest...
>>>> My workaround was to compile the kernel options as static cmdline into
>>>> the kernel itself...
>>> Better solution would be to append dom0's options to Xen's own command line,
>>> separated by --. E.g.,
>>> multiboot (hd0,1)/xen-3.4.gz console=tty -- root=/dev/sda2 ro console=tty0
>>> -- Keir
>>> Xen-devel mailing list
>>> Xen-devel@xxxxxxxxxxxxxxxxxxx </mc/compose?to=Xen-devel@xxxxxxxxxxxxxxxxxxx>
> Xen-devel mailing list
Xen-devel mailing list