On 01/31/19 11:07, Nikita Leshenko wrote: > This series adds driver support for: > - LSI53C1030 > - SAS1068 > - SAS1068E > > These controllers are widely supported by QEMU, VirtualBox and VMWare. This > work > is part of the more general agenda of enhancing OVMF boot device support to > have > feature parity with SeaBIOS.
If you mark a scsi-cd or scsi-hd device with "bootindex=1" on the QEMU command line, such that the device in question hangs off of the Fusion-MPT SCSI controller, can you tell me what the corresponding entry is in the "bootorder" fw_cfg file? You can find that line in the OVMF debug log, if you build OVMF with the DEBUG_VERBOSE bit (value 0x00400000) set in "gEfiMdePkgTokenSpaceGuid.PcdDebugPrintErrorLevel". Look for: > ConnectDevicesFromQemu: FwCfg: > ... > ConnectDevicesFromQemu: FwCfg: <end> and > SetBootOrderFromQemu: FwCfg: > ... > SetBootOrderFromQemu: FwCfg: <end> I'm asking because you might have to extend OvmfPkg/Library/QemuBootOrderLib too (namely function TranslatePciOfwNodes()), if you want the "bootindex" property to be honored by OVMF, for storage devices hanging off of this controller. Thanks Laszlo _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
