From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: problem using compiled kernel -- Sisu Date: Tue, 27 Jul 2010 22:09:29 +0100 Message-ID: References: <20100727203755.GQ17817@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20100727203755.GQ17817@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Pasi =?ISO-8859-1?B?S+Rya2vkaW5lbg==?= , Sisu Xi Cc: Jeremy Fitzhardinge , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 27/07/2010 21:37, "Pasi K=E4rkk=E4inen" wrote: >> what info are missing? >>=20 >=20 > 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 protoco= l 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=3Dall 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=3Dall guest_loglvl=3Dall sync_console >>>> console_to_ring com1=3D115200,8n1 console=3Dcom1 >=20 > See, dom0_mem is missing from there.. > The same thing happens with dom0 kernel, you lose the first parameter > (console=3Dhvc0). >=20 > -- Pasi >=20 >=20 >=20 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel