Re: [Xen-devel] qemu-xen-dir + PCI passthrough = BOOM

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Sun, 2013-12-22 at 11:25 +0000, Wu, Feng wrote:
> 
> > -----Original Message-----
> > From: xen-devel-bounces@xxxxxxxxxxxxx
> > [mailto:xen-devel-bounces@xxxxxxxxxxxxx] On Behalf Of Ian Campbell
> > Sent: Thursday, December 19, 2013 12:13 AM
> > To: Konrad Rzeszutek Wilk
> > Cc: Anthony PERARD; xen-devel@xxxxxxxxxxxxxxxxxxxx;
> > stefano.stabellini@xxxxxxxxxx
> > Subject: Re: [Xen-devel] qemu-xen-dir + PCI passthrough = BOOM
> > 
> > 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.
> > 
> > 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.
> > 
> 
> I am also interested in this thread. Do you know why ROMBIOS doesn't handle
> option ROM the same way as seaBIOS?

ROMBIOS was always this way and nobody has updated it to do things
properly. It's unclear whether it is worth the effort.

IMHO any effort expended would be better spent bringing qemu-upstream
+seabios up to scratch rather than spending time fixing qemu-traditional
+ROMBIOS for new usecases. Although qemu-traditional+ROMBIOS is not
going to be removed (in order to retain compatibility with existing
configurations) it is also not taking new features etc.

Ian.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel