[SeaBIOS] [Qemu-devel] [RFC] Passing boot order from qemu to seabios
anthony at codemonkey.ws
Mon Oct 11 22:50:08 CEST 2010
On 10/11/2010 03:36 PM, Gleb Natapov wrote:
> On Mon, Oct 11, 2010 at 03:30:21PM -0500, Anthony Liguori wrote:
>> On 10/11/2010 02:59 PM, Gleb Natapov wrote:
>>> No boot rom should do that. extboot wreaks havoc when it is used.
>>> And since virtio is now supported by bios there is no reason to use it.
>> You don't really have a choice. You could be doing hardware
>> passthrough and the ROM on the card may hijack int19.
> Then this particular HW would be broken on real HW too and will not
> respect BIOS settings. But the code we provide should work properly.
>>> Whoever needs scsi boot should add it to seabios too.
>> I don't disagree.
>> I think the best thing to do is to let SeaBIOS create a boot order
>> table that contains descriptive information and then advertise that
>> to QEMU.
> What for? Why this step is needed?
>> QEMU can then try to associate the list of bootable devices with
>> it's own set of devices and select a preferred order that it can
>> then give back to SeaBIOS. SeaBIOS can then present that list to
>> the user for additional refinement.
> Why not skip your first step and let QEMU create boot order list and
> pass it into Seabios. If menu=on option is present user will be able to
> override the default from Seabios.
Because SeaBIOS is definitive and QEMU is not.
We can ask SeaBIOS to boot from SCSI LUN 3 on PCI address X.Y.Z but that
doesn't mean that it can figure out what that means. If it can't, how
do we communicate that to the user? If SeaBIOS communicates its list to
QEMU then we can at least display that list in the monitor in the same
way that it's displayed to the guest. That means that we can reorder in
the monitor and potentially can persistent the boot device list in a
more meaningful way.
More information about the SeaBIOS