Abstract: A method for managing an LCS includes: sending a request to a microvisor kernel of a microvisor to provision an LCS on a first information handling system (IHS), wherein the request comprises at least a configuration template (CT); sending a second request to the microvisor kernel to verify that an enclave with a virtual trusted platform module (vTPM) is ready to communicate with the LCS; initiating, based successfully verifying, provisioning of the LCS based on the CT, wherein the provisioning of the LCS comprises at least an initiation of a guest basic input/output system (BIOS) of the LCS; receiving a notification, from the microvisor kernel, specifying that the LCS has been provisioned; after the notification has been received: sending a second notification to a user of the first IHS, wherein the second notification specifies a predetermined expiry date of the enclave with the vTPM on the first IHS.

Abstract: A method for managing a microvisor includes: issuing an API call to a microvisor agent to obtain a configuration template (CT) required to provision an LCS on an IHS; upon obtaining the CT, sending the CT to a microvisor kernel via the microvisor API; provisioning the LCS based on the CT; upon provisioning of the LCS and based on the microvisor kernel's request, initiating a guest BIOS of the LCS; notifying, via a GUI, an administrator about the provisioned LCS; after notifying the administrator: monitoring communication traffic of the LCS; analyzing the communication traffic to generate an analysis output; making, based on the analysis output, a determination that the activity is a malicious activity; and implementing, based on the determination, a security policy to disrupt a malicious user of the LCS.

Abstract: A method for managing an LCS includes: sending a request to a microvisor kernel (MK) of a microvisor to provision an LCS on a first IHS; initiating provisioning of the LCS based on a configuration template; receiving a notification, from the MK, specifying that the LCS has been provisioned; after the notification has been received: obtaining first metadata associated with the first IHS and second metadata associated with a second IHS; analyzing the first metadata and second metadata to extract relevant data; inferring, based on the relevant data, that the first IHS has at least the required amount of hardware resources to execute a vBMC associated with the first IHS; sending, based on the inferring, a second request to an SCP of the first IHS to generate the vBMC on the first IHS; and receiving a second notification, from the SCP, specifying that the vBMC is generated on the SCP.

Abstract: An LCS ePF-enabled resource system includes a resource system coupled to a resource management system and resource device(s) configured to provide resource functionality. The resource system includes a microvisor subsystem that the resource management system configures to provide an LCS and an ePF that is presented to the LCS as providing the resource functionality. When the microvisor subsystem receives an LCS request for the resource functionality from an LCS API subsystem in the LCS via the ePF, it transmits a microvisor request to the resource management system for the resource functionality that causes the resource management system to identify the resource device(s) for providing the resource functionality. Based on the identification of the resource device(s), the microvisor subsystem establishes a communication channel with each resource device, and provides the resource functionality to the LCS using the resource device(s) and via each communication channel, the ePF, and the LCS API subsystem.