* Handling multiple paths to the same EFI system partition?
@ 2016-12-02 21:26 Matthew Lazarowitz (mlazarow)
0 siblings, 0 replies; only message in thread
From: Matthew Lazarowitz (mlazarow) @ 2016-12-02 21:26 UTC (permalink / raw)
To: edk2-devel@lists.01.org
I am trying to deal with a requirement that our firmware show 2 boot options when there are multiple paths to a GPT disk with an EFI system partition. The specific ask is for both paths to be shown in the boot order. However, the short form device path means these would be duplicate entries which would cause more issues.
Fibre Channel and iSCSI connected drives are the two cases I need to cope with.
The UEFI specification seems to sound as if I could violate the spec if I do something like this.
In section 5.3.3 of the 2.6 spec, there is a statement "If GPT-cognizant software encounters two disks or partitions with identical GUIDs, results will be indeterminate." Other than section 10.12.2 specifying a iScsiMpioCapability field for network boots, I do not see guidance on how to handle a multi path scenario to a single disk.
The best I can think of right now is to modify the OS created option with the full path of of each path if 2 or more paths to a specific disk are detected. However, this would seem to be a potential source of conflict between the OS and the firmware since firmware would be modifying data the OS may require in a specific format.
Is there anything out there to provide some guidance on either rejecting this request and blatantly violating the spec, or being able to successfully fulfill it?
Thanks
Mathew
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2016-12-02 21:26 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-12-02 21:26 Handling multiple paths to the same EFI system partition? Matthew Lazarowitz (mlazarow)
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox