From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: problem using compiled kernel -- Sisu Date: Tue, 10 Aug 2010 08:36:02 +0100 Message-ID: References: <764975280.20100802152155@eikelenboom.it> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <764975280.20100802152155@eikelenboom.it> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Sander Eikelenboom , Pasi =?ISO-8859-1?B?S+Rya2vkaW5lbg==?= Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 02/08/2010 14:21, "Sander Eikelenboom" wrote: > Hi Keir, >=20 > 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 >=20 >=20 >=20 > Wednesday, July 28, 2010, 9:49:42 AM, you wrote: >=20 >> 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 t= hat >> the loader name does look like that, and that we now correctly handle GR= UB2 >> command lines. Since I do not have GRUB2 installed. >=20 >> If it works okay, I'll backport it for 4.0.1. >=20 >> Thanks, >> Keir >=20 >> On 27/07/2010 22:59, "Sander Eikelenboom" wrote: >=20 >>> Don't know if the bootloader name in the multiboot specs contains the g= rub >>> version number .. so it perhaps could be derived from there ? >>>=20 >>> http://www.gnu.org/software/grub/manual/multiboot/multiboot.html#Boot-i= nform >>> at >>> ion-format >>>=20 >>> See flag 9 >>>=20 >>> -- >>> Sander >>>=20 >>>=20 >>> Tuesday, July 27, 2010, 11:09:29 PM, you wrote: >>>=20 >>>> On 27/07/2010 21:37, "Pasi K=E4rkk=E4inen" wrote: >>>=20 >>>>>> 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 >>>=20 >>>> 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=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 fir= st >>>> item in the string actually lops a parameter. The workaround is to sti= ck >>>> something dummy as the first parameter, such as a period. This behavio= ur >>>> change between GRUB1 and GRUB2 is a pain in the arse. >>>=20 >>>> -- Keir >>>=20 >>>>>>>> (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 >>>=20 >>>=20 >>>=20 >>>=20 >>>=20 >>>=20 >=20 >=20 >=20 >=20