qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: gpxe <gpxe@etherboot.org>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC] gPXE fw_cfg file interface support
Date: Fri, 29 Jan 2010 10:06:23 +0000	[thread overview]
Message-ID: <fbd9d3991001290206j7826c5cfg51f9fc6d6479cf4c@mail.gmail.com> (raw)
In-Reply-To: <4B601224.2030803@redhat.com>

On Wed, Jan 27, 2010 at 10:15 AM, Gerd Hoffmann <kraxel@redhat.com> wrote:
>> Note that this patch only adds the fw_cfg file interface mechanism, it
>> does not
>> automatically probe for a special file when gPXE starts.  You will
>> need to manually
>> "chain fw_cfg:genroms/file".
>
> That should be changed too IMHO.  qemu needs some kind of new switch, so you
> can place the firmware file into some other virtual directory where gpxe
> could look by default, i.e. something like "fw_cfg:gpxe/default". Then you
> can easily have qemu guests netboot from somewhere without any local
> pxe/tftp setup, like this:
>
>  qemu -fw-file gpxe/default=bko.gpxe
>
> with bko.gpxe being:
>
>  #!gpxe
>  dhcp net0
>  set 209:string pxelinux.cfg/default
>  set 210:string http://boot.kernel.org/bko/
>  chain http://boot.kernel.org/bko/pxelinux.0

That sounds good.  I will send out a new patch which fetches
fw_cfg:gpxe/default on startup.

Stefan

  reply	other threads:[~2010-01-29 10:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-27  9:42 [Qemu-devel] [RFC] gPXE fw_cfg file interface support Stefan Hajnoczi
2010-01-27 10:15 ` Gerd Hoffmann
2010-01-29 10:06   ` Stefan Hajnoczi [this message]
2010-02-08  2:23   ` [gPXE] " Shao Miller

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=fbd9d3991001290206j7826c5cfg51f9fc6d6479cf4c@mail.gmail.com \
    --to=stefanha@gmail.com \
    --cc=gpxe@etherboot.org \
    --cc=kraxel@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).