From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:44756) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QgGTw-0001xI-At for qemu-devel@nongnu.org; Mon, 11 Jul 2011 09:25:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QgGTu-0001ap-Ce for qemu-devel@nongnu.org; Mon, 11 Jul 2011 09:25:04 -0400 Received: from mail-gw0-f45.google.com ([74.125.83.45]:37586) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QgGTt-0001aZ-UK for qemu-devel@nongnu.org; Mon, 11 Jul 2011 09:25:02 -0400 Received: by gwb19 with SMTP id 19so1798744gwb.4 for ; Mon, 11 Jul 2011 06:25:01 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20110711114151.19872.43356.malonedeb@wampee.canonical.com> References: <20110711114151.19872.43356.malonedeb@wampee.canonical.com> <20110711114151.19872.43356.malonedeb@wampee.canonical.com> Date: Mon, 11 Jul 2011 14:25:00 +0100 Message-ID: From: Stefan Hajnoczi Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [Qemu-devel] [Bug 808737] [NEW] No option to load additional binary files from command line in QEMU List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Bug 808737 <808737@bugs.launchpad.net> Cc: qemu-devel@nongnu.org On Mon, Jul 11, 2011 at 12:41 PM, Anup Patel <808737@bugs.launchpad.net> wrote: > Public bug reported: > > There is no command line option like -kerner, or -initrd to load an > arbitrary binary file to a RAM location when launching QEMU. It depends on your target (e.g. qemu-system-x86_64) but you can load your own code as a bzImage or multiboot binary. Both formats are documented: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob_plain;f=Documentation/x86/boot.txt http://www.gnu.org/software/grub/manual/multiboot/multiboot.html The problem with loading binary code is that you quickly want some options (is this real mode or protected mode code?, what address to load at?, are there any modules/initrd extras elsewhere in memory?). That's basically what multiboot is for. Does multiboot do what you need? If not, please be more specific and describe your target machine and use case. Stefan