qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Deema B <stou4r@gmail.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Command line option "-option-rom" doesn't take the ROM file
Date: Tue, 24 Oct 2017 12:22:45 -0700	[thread overview]
Message-ID: <CACw_XP-pUdB-JCThpoibqAF0D4Fi+AS-j3tthtLdWMmLm2X9Wg@mail.gmail.com> (raw)
In-Reply-To: <20171024115032.GA18756@stefanha-x1.localdomain>

Thank you, Stefan!  That worked.
Sorry for the double email, I'm learning quickly :)

On Tue, Oct 24, 2017 at 4:50 AM, Stefan Hajnoczi <stefanha@gmail.com> wrote:

> On Mon, Oct 23, 2017 at 02:22:05PM -0700, Deema B wrote:
> > I'm trying to use the -option-rom option to supply my own virtio OpROM.
> >
> > I am not able to see the ROM being launch (the built-in version comes up
> > instead).
> > The only way I am able to make it work is to rebuild the Qemu and iPXE
> > together.
> >
> > I'm assuming this is working feature, and I'm simply doing something
> wrong.
> > Appreciate any suggestions, pointers, and to hear your experience with
> this
> > particular option.
>
> Hi Deema,
> You can specify the option ROM on a per-device basis:
>
>   -device virtio-net-pci,romfile=my-ipxe.rom,...
>
> The advantage of this approach is that there is no conflict between the
> global -option-rom file and the default file loaded by the NIC device.
>
> Stefan
>

  reply	other threads:[~2017-10-24 19:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-23 21:22 [Qemu-devel] Command line option "-option-rom" doesn't take the ROM file Deema B
2017-10-24 11:50 ` Stefan Hajnoczi
2017-10-24 19:22   ` Deema B [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-10-23 17:54 Deema B
2017-10-24 11:53 ` Stefan Hajnoczi

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=CACw_XP-pUdB-JCThpoibqAF0D4Fi+AS-j3tthtLdWMmLm2X9Wg@mail.gmail.com \
    --to=stou4r@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    /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).