From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:53934) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XK3Et-0000Nx-MH for qemu-devel@nongnu.org; Wed, 20 Aug 2014 06:35:36 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XK3Es-0005Iq-QQ for qemu-devel@nongnu.org; Wed, 20 Aug 2014 06:35:35 -0400 Received: from mail-oi0-x22e.google.com ([2607:f8b0:4003:c06::22e]:59222) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XK37G-0002SH-Jy for qemu-devel@nongnu.org; Wed, 20 Aug 2014 06:27:42 -0400 Received: by mail-oi0-f46.google.com with SMTP id i138so5485492oig.5 for ; Wed, 20 Aug 2014 03:27:42 -0700 (PDT) MIME-Version: 1.0 Date: Wed, 20 Aug 2014 11:27:41 +0100 Message-ID: From: Stefan Hajnoczi Content-Type: text/plain; charset=UTF-8 Subject: [Qemu-devel] Recent SeaBIOS too big for QEMU -initrd List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel Cc: Kevin OConnor , John Snow , Gerd Hoffmann , "Michael S. Tsirkin" 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. The guest Linux kernel rejects the initrd: BIOS-provided physical RAM map: BIOS-e820: 0000000000010000 - 000000000009fc00 (usable) BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved) BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 000000003ffe0000 (usable) BIOS-e820: 000000003ffe0000 - 0000000040000000 (reserved) BIOS-e820: 00000000feffc000 - 00000000ff000000 (reserved) BIOS-e820: 00000000fffc0000 - 0000000100000000 (reserved) ... initrd extends beyond end of memory (0x3ffef79f > 0x3ffe0000) disabling initrd It is easy enough to "fix" the problem by bumping ACPI_DATA_SIZE up to 0x20000 in QEMU. Perhaps this should only be done for bios-256k.bin guests and not bios-128k.bin guests (QEMU 1.7 and older machine types). 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. Any ideas? Stefan