From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HIDtu-0000Od-7z for qemu-devel@nongnu.org; Fri, 16 Feb 2007 19:58:06 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HIDtr-0000KB-RH for qemu-devel@nongnu.org; Fri, 16 Feb 2007 19:58:04 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HIDtr-0000K0-O3 for qemu-devel@nongnu.org; Fri, 16 Feb 2007 19:58:03 -0500 Received: from static-71-162-243-5.phlapa.fios.verizon.net ([71.162.243.5] helo=grelber.thyrsus.com) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1HIDtr-0006ej-9s for qemu-devel@nongnu.org; Fri, 16 Feb 2007 19:58:03 -0500 From: Rob Landley Subject: Re: [Qemu-devel] [PATCH] don't require a disk image for network boot Date: Fri, 16 Feb 2007 19:57:56 -0500 References: <87bqjyxg10.fsf@tac.ki.iif.hu> <20070215101744.6a639186@thomas.toulouse> <200702151627.54818.paul@codesourcery.com> In-Reply-To: <200702151627.54818.paul@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Message-Id: <200702161957.57784.rob@landley.net> Content-Transfer-Encoding: quoted-printable Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Paul Brook On Thursday 15 February 2007 11:27 am, Paul Brook wrote: > On Thursday 15 February 2007 09:17, Thomas Petazzoni wrote: > > Hi, > > > > Le Tue, 13 Feb 2007 15:58:13 +0100, > > > > "andrzej zaborowski" a =E9crit : > > > Subject: don't require a disk image for network boot > > > > BTW, is there a reason why a disk image is required when using the > > -kernel option ? > > > > In the following case: -kernel vmlinuz -append "nfsroot=3Dblabla", we > > could boot over the network, without the need for any disk image, but > > Qemu wants to have a disk image. Is it mandatory ? >=20 > The BIOS doesn't know about the -kernel option, so qemu replaces the fi= rst=20 > sector of the disk image with a dummy bootloader that jumps to the prel= oaded=20 > kernel. It can only do that if there is an image to replace. Yeah, but on Linux the standard workaround is to supply -hda /dev/zero, a= nd if=20 qemu notices that it has -kernel but no hda, from a UI perspective qemu c= ould=20 easily supply the standard workaround for itself... Rob --=20 "Perfection is reached, not when there is no longer anything to add, but when there is no longer anything to take away." - Antoine de Saint-Exuper= y