From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:60960) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XKECV-0000ob-5N for qemu-devel@nongnu.org; Wed, 20 Aug 2014 18:17:58 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XKECN-00013y-HT for qemu-devel@nongnu.org; Wed, 20 Aug 2014 18:17:51 -0400 Received: from mail-ie0-f170.google.com ([209.85.223.170]:36945) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XKECN-00012w-DQ for qemu-devel@nongnu.org; Wed, 20 Aug 2014 18:17:43 -0400 Received: by mail-ie0-f170.google.com with SMTP id rl12so3695110iec.29 for ; Wed, 20 Aug 2014 15:17:42 -0700 (PDT) Date: Wed, 20 Aug 2014 18:17:40 -0400 From: Kevin O'Connor Message-ID: <20140820221739.GA10152@morn.localdomain> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] Recent SeaBIOS too big for QEMU -initrd List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi Cc: Gerd Hoffmann , John Snow , qemu-devel , "Michael S. Tsirkin" On Wed, Aug 20, 2014 at 11:27:41AM +0100, Stefan Hajnoczi wrote: > The QEMU -initrd option loads the initrd at the top of RAM. There is > a 64 KB safety region for ACPI tables in hw/i386/pc.c:load_linux(): > > initrd_max = max_ram_size-ACPI_DATA_SIZE-1; > > QEMU's bios-256k.bin SeaBIOS build reserves 128 KB at the top of > memory so the 64 KB ACPI data size has become too small. Just to clarify, SeaBIOS uses a variable amount of data at the top of ram. SeaBIOS isn't changing the allocation because of its build parameters, but because QEMU is passing more ACPI tables to it. > Perhaps QEMU -> SeaBIOS -> linuxboot.bin can be simplified so QEMU > doesn't have to guess what e820 region SeaBIOS will reserve. > linuxboot.bin would probably be the place to do it unless SeaBIOS has > Linux loading functionality that could be reused. There is no current functionality in SeaBIOS to deploy a Linux kernel from fw_cfg. However, it looks like it would be pretty simple to add if someone wants to give it a try. -Kevin