From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1LULmq-00077Y-TT
	for qemu-devel@nongnu.org; Tue, 03 Feb 2009 08:58:01 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1LULmm-00076h-GR
	for qemu-devel@nongnu.org; Tue, 03 Feb 2009 08:57:59 -0500
Received: from [199.232.76.173] (port=52895 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1LULml-00076Q-Ar
	for qemu-devel@nongnu.org; Tue, 03 Feb 2009 08:57:55 -0500
Received: from mr01.hansenet.de ([213.191.74.10]:35109)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <rene@exactcode.de>) id 1LULmk-0001zx-Sl
	for qemu-devel@nongnu.org; Tue, 03 Feb 2009 08:57:55 -0500
Message-ID: <49884D56.8000603@exactcode.de>
Date: Tue, 03 Feb 2009 14:57:42 +0100
From: Rene Rebe <rene@exactcode.de>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH] Add multi-boot kernel loading support
References: <49873680.2040603@exactcode.de> <49883F87.9000903@suse.de>
In-Reply-To: <49883F87.9000903@suse.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: Quoted-Printable
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org
Cc: Alexander Graf <agraf@suse.de>, Kevin Wolf <kwolf@suse.de>

Hi,

Kevin Wolf wrote:
> Rene Rebe schrieb:
>> Hi all,
>>
>> Alexander Graf implemented multi-boot kernel loading during
>> his work to run Darwin inside Qemu/KVM. As the boot loader
>> expects to load the kernel in an EFI environment a custom
>> booter is used to load the kernel using a legacy BIOS.
>>
>> This is a port of the patch to the new extload / INT 19
>> machinery (including minor cleanups).
>=20
> The memory map doesn't seem to work. It's all zeros for me (haven't
> looked for the reason yet) and that kills my kernel. When I disable the
> memory map part, the kernel seems to boot correctly and it sees all the
> modules with the right command lines.
>=20
> Once these basic things work, another nice feature would be gzip
> support. It took me some minutes until I realized that I tried to feed
> it a gzipped kernel which didn't work, of course.

I think I noticed the same with the GRUB example kernel. I'll
take a look at some later hour.

Is your kernel something you can share for testing?


--=20
   Ren=E9 Rebe - ExactCODE GmbH - Europe, Germany, Berlin
   http://exactcode.de | http://t2-project.org | http://rene.rebe.name