From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1LUKlB-0006uA-Ex
	for qemu-devel@nongnu.org; Tue, 03 Feb 2009 07:52:13 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1LUKl8-0006tA-I9
	for qemu-devel@nongnu.org; Tue, 03 Feb 2009 07:52:11 -0500
Received: from [199.232.76.173] (port=57131 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1LUKl7-0006su-Pr
	for qemu-devel@nongnu.org; Tue, 03 Feb 2009 07:52:10 -0500
Received: from ns.suse.de ([195.135.220.2]:43682 helo=mx1.suse.de)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <kwolf@suse.de>) id 1LUKl7-0002Pv-Cb
	for qemu-devel@nongnu.org; Tue, 03 Feb 2009 07:52:09 -0500
Message-ID: <49883F87.9000903@suse.de>
Date: Tue, 03 Feb 2009 13:58:47 +0100
From: Kevin Wolf <kwolf@suse.de>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH] Add multi-boot kernel loading support
References: <49873680.2040603@exactcode.de>
In-Reply-To: <49873680.2040603@exactcode.de>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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: rene@exactcode.de
Cc: qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>

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).

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.

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.

Kevin