Abstract: Temporary firmware is provided as cloud services. Different temporary firmware containers are downloaded via a communications network. A light-weight operating system launches and executes the temporary firmware containers during a boot operation, POST operation, or other scheme. The temporary firmware containers thus detect and perhaps resolve POST errors. The light-weight operating system may also download a full-service/resource operating system. A second or subsequent boot operation may be performed, but control is ceded to the full-service/resource operating system. Multiple firmware tenants may thus be temporarily downloaded to a bare metal machine to support POST error detection activities. Advanced OS serviceability, diagnostics, and other containerized firmware may thus be quickly and simply launched without requiring the excessive time and difficulties of using the full-service/resource operating system.

Abstract: An information handling system is configured, during a pre-extensible firmware interface initialization phase of the information handling system, to learn capabilities of components of the information handling system, create a hand-off block for storage of a virtual graphical browser firmware volume payload, and store learned capabilities of the components of the information handling system in the hand-off block. During a driver execution environment phase, the information handling system may retrieve the learned capabilities of the components of the information handling system stored in the hand-off block, publish learned capabilities retrieved from the hand-off block, retrieve the virtual graphics browser firmware volume payload stored in the hand-off block, and dispatch a virtual graphics browser learning driver and a virtual graphics browser interpreter driver based on retrieved virtual graphics browser firmware volume payload.

Abstract: Temporary firmware is provided as cloud services. Different temporary firmware containers are downloaded via a communications network. A light-weight operating system launches and executes the temporary firmware containers during a boot operation, POST operation, or other scheme. The temporary firmware containers thus detect and perhaps resolve POST errors. The light-weight operating system may also download a full-service/resource operating system. A second or subsequent boot operation may be performed, but control is ceded to the full-service/resource operating system. Multiple firmware tenants may thus be temporarily downloaded to a bare metal machine to support POST error detection activities. Advanced OS serviceability, diagnostics, and other containerized firmware may thus be quickly and simply launched without requiring the excessive time and difficulties of using the full-service/resource operating system.

Abstract: An information handling system is configured, during a pre-extensible firmware interface initialization phase of the information handling system, to learn capabilities of components of the information handling system, create a hand-off block for storage of a virtual graphical browser firmware volume payload, and store learned capabilities of the components of the information handling system in the hand-off block. During a driver execution environment phase, the information handling system may retrieve the learned capabilities of the components of the information handling system stored in the hand-off block, publish learned capabilities retrieved from the hand-off block, retrieve the virtual graphics browser firmware volume payload stored in the hand-off block, and dispatch a virtual graphics browser learning driver and a virtual graphics browser interpreter driver based on retrieved virtual graphics browser firmware volume payload.

Abstract: An information handling system is configured, during a pre-extensible firmware interface initialization phase of the information handling system, to learn capabilities of components of the information handling system, create a hand-off block for storage of a virtual graphical browser firmware volume payload, and store learned capabilities of the components of the information handling system in the hand-off block. During a driver execution environment phase, the information handling system may retrieve the learned capabilities of the components of the information handling system stored in the hand-off block, publish learned capabilities retrieved from the hand-off block, retrieve the virtual graphics browser firmware volume payload stored in the hand-off block, and dispatch a virtual graphics browser learning driver and a virtual graphics browser interpreter driver based on retrieved virtual graphics browser firmware volume payload.

Abstract: An information handling system is configured, during a pre-extensible firmware interface initialization phase of the information handling system, to learn capabilities of components of the information handling system, create a hand-off block for storage of a virtual graphical browser firmware volume payload, and store learned capabilities of the components of the information handling system in the hand-off block. During a driver execution environment phase, the information handling system may retrieve the learned capabilities of the components of the information handling system stored in the hand-off block, publish learned capabilities retrieved from the hand-off block, retrieve the virtual graphics browser firmware volume payload stored in the hand-off block, and dispatch a virtual graphics browser learning driver and a virtual graphics browser interpreter driver based on retrieved virtual graphics browser firmware volume payload.