Multi-boot system and method for a baseboard management controller (BMC)
An Information Handling System (IHS) includes multiple hardware devices, and a baseboard Management Controller (BMC) in communication with the plurality of hardware devices. The BMC includes executable instructions for beginning execution of a first BMC firmware stack, and during execution of the first BMC firmware stack, halt execution of the first BMC firmware stack, and begin execution of a second BMC firmware stack. At least a portion of the executable instructions used to generate the first BMC firmware stack are different than the executable instructions used to generate the second BMC firmware stack.
1. An information handling system (IHS), comprising:
a plurality of hardware devices; and
a baseboard management controller (BMC) in communication with the plurality of hardware devices, the BMC comprising one or more processors and one or more memory units including instructions that, upon execution by the processors, cause the BMC to:
begin execution of an openBMC firmware stack, wherein the openBMC firmware stack has been implemented by an entity that is separate and distinct from a vendor of the IHS;
when the openBMC firmware stack is being executed, inhibit the openBMC firmware stack from performing at least one function of the BMC; during execution of the openBMC firmware stack, halt execution of the openBMC firmware stack, and begin execution of a vendor-based BMC firmware stack, wherein the vendor-based BMC firmware stack is provided by a vendor of the IHS in which the BMC is configured; and
when the vendor-based BMC firmware stack is being executed, allow the vendor-based BMC firmware stack to perform the at least one function of the BMC.
2. The IHS of claim 1 , wherein the instructions, upon execution, further cause the BMC to:
during the execution of the vendor-based BMC firmware stack, halt the execution of the vendor-based BMC firmware stack, and begin a second execution of the openBMC firmware stack.
3. The IHS of claim 1 , wherein the vendor-based BMC firmware stack is configured to perform one or more maintenance operations for the IHS.
4. The IHS of claim 1 , wherein the instructions, upon execution, further cause the BMC to inhibit the openBMC firmware stack from accessing the vendor-based BMC firmware stack stored in a portion of the memory units.
5. The IHS of claim 1 , wherein the instructions, upon execution, further cause the BMC to store information associated with the license in one or more one time programmable (OTP) bits in the baseboard processor.
6. The IHS of claim 1 , wherein the instructions comprise a bootloader that is executed to:
halt the execution of the openBMC firmware stack, and begin the execution of the vendor-based BMC firmware stack; and
enforce one or more access policies based on whether the openBMC firmware stack or vendor-based BMC firmware stack is currently being executed, the access policies indicating a level of access that the openBMC firmware stack has to a portion of memory units that stores the vendor-based BMC firmware stack.
7. The IHS of claim 1 , wherein the instructions comprise a hypervisor that is executed to:
halt the execution of the openBMC firmware stack, and begin the execution of the vendor-based BMC firmware stack; and
enforce one or more access policies based on whether the openBMC firmware stack or vendor-based BMC firmware stack is currently being executed, the access policies indicating a level of access that the openBMC firmware stack has to a portion of memory units that stores the vendor-based BMC firmware stack.
8. The IHS of claim 1 , wherein the instructions, upon execution, further cause the BMC to perform at least one of suspending the currently executed first or vendor-based BMC firmware stack, and hibernating the currently executed first or vendor-based BMC firmware stack.
9. A method comprising:
beginning, using instructions stored in at least one memory and executed by at least one processor, execution of an openBMC firmware stack on a baseboard management controller (BMC) in communication with a plurality of hardware devices of an information handling system (IHS), wherein the openBMC firmware stack has been implemented by an entity that is separate and distinct from a vendor of the IHS; and
when the openBMC firmware stack is being executed, inhibiting the openBMC firmware stack from performing at least one function of the BMC;
during execution of the openBMC firmware stack, halting, using the instructions, execution of the openBMC firmware stack, and begin execution of a vendor-based BMC firmware stack, wherein at least a portion of the executable instructions used to generate openBMC firmware stack are different than the executable instructions used to generate the vendor-based BMC firmware stack; and
when the vendor-based BMC firmware stack is being executed, allowing the vendor-based BMC firmware stack to perform the at least one function of the BMC.
10. The method of claim 9 , further comprising:
during the execution of the vendor-based BMC firmware stack, halt the execution of the vendor-based BMC firmware stack, and begin a second execution of the openBMC firmware stack.
11. The method of claim 10 further comprising performing one or more maintenance operations for the IHS by the vendor-based BMC firmware stack.
12. The method of claim 11 , further comprising inhibiting the custom BMC firmware stack from accessing the vendor-based BMC firmware stack stored in a portion of the memory units.
13. The method of claim 9 , further comprising storing information associated with the license in one or more one time programmable (OTP) bits in the baseboard processor.
14. The method of claim 9 , further comprising:
halting, by a bootloader, the execution of the openBMC firmware stack, and begin the execution of the vendor-based BMC firmware stack; and
enforcing, by the bootloader, one or more access policies based on whether the openBMC firmware stack or vendor-based BMC firmware stack is currently being executed, the access policies indicating a level of access that the openBMC firmware stack has to a portion of memory units that stores the vendor-based BMC firmware stack.
15. An information handling system (IHS), comprising:
a plurality of hardware devices; and
a baseboard management controller (BMC) in communication with the plurality of hardware devices, the BMC comprising one or more processors and one or more memory units including instructions that, upon execution by the processors, cause the BMC to:
receive selection of an openBMC firmware stack, wherein the openBMC firmware stack has been implemented by an entity that is separate and distinct from a vendor of the IHS;
begin execution of the openBMC firmware stack;
when the openBMC firmware stack is being executed, inhibit the openBMC firmware stack from performing at least one function of the BMC;
during execution of the openBMC firmware stack, halt execution of the openBMC firmware stack, and begin execution of a vendor-based BMC firmware stack, wherein the vendor-based BMC firmware stack is provided by a vendor of the IHS in which the BMC is configured; and
when the vendor-based BMC firmware stack is being executed, allow the vendor-based BMC firmware stack to perform the at least one function of the BMC.