From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
xen-devel@lists.xenproject.org, stefano.stabellini@citrix.com
Subject: Re: qemu-xen-dir + PCI passthrough = BOOM
Date: Wed, 18 Dec 2013 11:18:36 -0500 [thread overview]
Message-ID: <20131218161836.GB7405@pegasus.dumpdata.com> (raw)
In-Reply-To: <1387383185.28680.60.camel@kazak.uk.xensource.com>
On Wed, Dec 18, 2013 at 04:13:05PM +0000, Ian Campbell wrote:
> On Wed, 2013-12-18 at 10:22 -0500, Konrad Rzeszutek Wilk wrote:
> > load_roms and bios_load are not set - so it wouldn't even do it.
> > It only does it for Bochs BIOS.
>
> Right, this is deliberate.
>
> For ROMBIOS (AKA BOchs BIOS) hvmloader loads the options roms. and I
> think ROMBIOS subsequently loads them.
>
> For SeaBIOS it is the BIOS itself which both loads and executes the
> ROMS, which is why it is NULL in hvmloader.
Aha!
>
> The SeaBIOS way is far more like how systems normally work and because
> the BIOS is in charge it can do a better job than splitting it between
> two entities.
>
> Seems like perhaps I was mistaken about hvmloader+rombios not supporting
> loading from the ROM BAR of the device, it does seem to have some
> limited support for that (serial controllers and disk controllers only)
>
> hvmloader+rombios does hardcode the VGA bios (rather than getting it
> from the emulated devices ROM bar), which is probably what I was
> thinking of, that's why people doing VGA passthrough with rombios need
> to grab the bios image and build it into hvmloader.
Right, which I hope to fix to make this work without this madness.
>
> hvmloader+rombios also hardcodes the etherboot rom.
>
> Ian.
>
next prev parent reply other threads:[~2013-12-18 16:18 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 19:51 qemu-xen-dir + PCI passthrough = BOOM Konrad Rzeszutek Wilk
2013-12-05 12:16 ` Anthony PERARD
2013-12-06 14:49 ` Konrad Rzeszutek Wilk
2013-12-06 15:35 ` Anthony PERARD
2013-12-06 16:00 ` Wei Liu
2013-12-06 16:03 ` Wei Liu
2013-12-16 15:08 ` Konrad Rzeszutek Wilk
2013-12-18 14:48 ` Anthony PERARD
2013-12-18 14:57 ` Ian Campbell
2013-12-18 15:22 ` Konrad Rzeszutek Wilk
2013-12-18 16:13 ` Ian Campbell
2013-12-18 16:18 ` Konrad Rzeszutek Wilk [this message]
2013-12-22 11:25 ` Wu, Feng
2013-12-31 15:30 ` Konrad Rzeszutek Wilk
2014-01-06 9:54 ` Ian Campbell
2014-01-07 0:27 ` Wu, Feng
2014-01-08 19:44 ` Konrad Rzeszutek Wilk
2014-01-09 14:56 ` Anthony PERARD
2014-01-09 15:36 ` Pasi Kärkkäinen
2014-01-09 15:43 ` Pasi Kärkkäinen
2014-01-09 23:54 ` Sander Eikelenboom
2014-01-10 0:17 ` Sander Eikelenboom
2014-01-10 0:22 ` Sander Eikelenboom
2014-01-10 3:28 ` Konrad Rzeszutek Wilk
2014-01-10 15:19 ` Anthony PERARD
2014-01-10 16:05 ` Sander Eikelenboom
2014-01-10 16:25 ` Anthony PERARD
2014-01-10 16:38 ` Sander Eikelenboom
2014-01-10 16:35 ` Konrad Rzeszutek Wilk
2014-01-10 17:38 ` Sander Eikelenboom
2014-01-10 18:01 ` Konrad Rzeszutek Wilk
2014-01-26 0:05 ` Zhang, Yang Z
2014-01-27 12:12 ` Stefano Stabellini
2014-01-27 15:34 ` Zhang, Yang Z
2014-01-27 15:37 ` Stefano Stabellini
2014-01-31 15:23 ` Stefano Stabellini
2014-01-26 2:15 ` Zhang, Yang Z
2014-01-16 6:40 ` Zhang, Yang Z
2014-01-16 11:36 ` Konrad Rzeszutek Wilk
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=20131218161836.GB7405@pegasus.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=stefano.stabellini@citrix.com \
--cc=xen-devel@lists.xenproject.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.