From: Rob Landley <rob@landley.net>
To: qemu-devel@nongnu.org
Cc: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [PATCH] don't require a disk image for network boot
Date: Fri, 16 Feb 2007 19:57:56 -0500 [thread overview]
Message-ID: <200702161957.57784.rob@landley.net> (raw)
In-Reply-To: <200702151627.54818.paul@codesourcery.com>
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" <balrog@zabor.org> a écrit :
> > > 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=blabla", we
> > could boot over the network, without the need for any disk image, but
> > Qemu wants to have a disk image. Is it mandatory ?
>
> The BIOS doesn't know about the -kernel option, so qemu replaces the first
> sector of the disk image with a dummy bootloader that jumps to the preloaded
> 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, and if
qemu notices that it has -kernel but no hda, from a UI perspective qemu could
easily supply the standard workaround for itself...
Rob
--
"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-Exupery
prev parent reply other threads:[~2007-02-17 0:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87bqjyxg10.fsf@tac.ki.iif.hu>
2007-02-13 14:58 ` [Qemu-devel] [PATCH] don't require a disk image for network boot andrzej zaborowski
2007-02-13 15:08 ` Stuart Brady
2007-02-15 9:17 ` Thomas Petazzoni
2007-02-15 15:45 ` Ed Swierk
2007-02-15 16:27 ` Paul Brook
2007-02-17 0:57 ` Rob Landley [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200702161957.57784.rob@landley.net \
--to=rob@landley.net \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.