Kevin O'Connor wrote:
one possible way forward would be to split the current SeaBIOS rom
into two roms: qvmloader and seabios. The qvmloader would do
the qemu specific platform init (pci init, smm init, mtrr init, bios
tables) and then load and run the regular seabios rom.
qvmloader sounds a
Gerd Hoffmann wrote:
and pass down the
tables to the firmware (through a now unspecified interface -- perhaps
the tables could even be installed at this point).
As far I know coreboot can add more stuff such as acpi tables to cbfs at
runtime and seabios able to access cbfs too and pull
Gleb Natapov wrote:
BBS specification is broken since it doesn't provide a way for
discovered boot method (BCV) to be linked back to a device it will
boot from. Nothing we can do to fix this except moving to EFI (an
hope the problem is fixed there).
There is that option, or there could be
Gleb Natapov wrote:
There is no way for qemu to know about BCVs or BEVs
This is very much the key point.
In order to have command line control over the boot process, the
machine and the firmware must agree on things.
I see two options:
1. QEMU works very very hard to provide a machine that
Peter Stuge wrote:
Specifying boot device using PCI BDF is a great example of using
common structured data. That BDF exists both in machine and firmware
data models.
Gleb Natapov wrote:
Bus numbers are assigned by a guest. Qemu knows nothing about them,
so it specify device path by topology
