IP Library Granted Patent US 12,014,185
Granted Patent B2
US 12,014,185 · App. 17/962,619 · Granted Jun 18, 2024

Unified boot image for multiple operating systems

Inventors: Aravinda Haryadi (Bangalore, IN); Karthik Ramachandra (Bangalore, IN); Suman Boro (Bangalore, IN)
Assignee: VMware LLC
G06F9/4401G06F9/45558G06F2009/4557
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,014,185
App. No.
17/962,619
Granted
Jun 18, 2024
Kind
B2
Abstract

Disclosed are various embodiments for a unified boot image that can be used to install an operating system onto a host machine and a respective operating system onto a data processing units (DPU) installed on a host machine. The unified boot image contains installation files for installing an operating system on the host machine and an installation depot that can be used to create a boot image for installing the same or different operating system on the DPU. During installation of an operating system on a host machine, the installation workflow can also require installation of an additional operating system or other configuration of a DPU installed in a host machine. In response to determining that an operating system is to be installed on the DPU, the installation depot can be obtained and reformatted into a downloadable format that is compatible with the DPU.

Claims (40)

1. A system, comprising:

a computing device comprising a central processor unit (CPU) and a data processing unit (DPU); and

machine-readable instructions that, when executed by the CPU, cause the computing device to at least:

obtain a unified boot image comprising installation data associated with a first installation workflow for configuring a first hypervisor on the computing device and an installation depot associated with a second installation workflow for configuring a second hypervisor on the DPU;

identify the installation depot associated with the second installation workflow in the unified boot image;

create a DPU boot image based at least in part on the installation depot and a format compatible with the DPU; and

cause the DPU to execute the second installation workflow using the DPU boot image.

2. The system of claim 1 , wherein the machine-readable instructions further cause the computing device to at least execute the first installation workflow based at least in part on the installation data in the unified boot image.

3. The system of claim 1 , wherein the machine-readable instructions further cause the computing device to at least convert the installation depot into the format using a packaging kit.

4. The system of claim 1 , wherein the DPU comprises at least one smart network interface card, the at least one smart network interface card comprising an additional CPU that can execute a storage task or a networking task on behalf of the CPU of the computing device.

5. The system of claim 1 , wherein causing the DPU to execute the second installation workflow using the DPU boot image comprises:

initiating communication with the DPU via a baseboard management controller (BMC); and

providing the DPU boot image to the DPU via the BMC.

6. The system of claim 5 , wherein the machine-readable instructions further cause the computing device to monitor a status of the second installation workflow via one or more status updates received from the BMC.

7. The system of claim 1 , wherein the machine-readable instructions further cause the computing device to receiving configuration data associated with the second installation workflow, the DPU boot image being embedded with the configuration data.

8. A method, comprising:

obtaining a unified boot image comprising installation data associated with a first installation workflow for configuring a first hypervisor on a computing device and an installation depot associated with a second installation workflow for configuring a second hypervisor on a data processing unit (DPU);

identifying the installation depot associated with the second installation workflow in the unified boot image;

creating a DPU boot image based at least in part on the installation depot and a format compatible with the DPU; and

causing the DPU to execute the second installation workflow using the DPU boot image.

9. The method of claim 8 , further comprising executing the first installation workflow based at least in part on the installation data in the unified boot image.

10. The method of claim 8 , further comprising converting the installation depot into the format using a packaging kit.

11. The method of claim 8 , wherein the DPU comprises at least one smart network interface card, the at least one smart network interface card comprising an additional CPU that can execute a storage task or a networking task on behalf of the CPU of the computing device.

12. The method of claim 8 , wherein causing the DPU to execute the second installation workflow using the DPU boot image comprises:

initiating communication with the DPU via a baseboard management controller (BMC); and

providing the DPU boot image to the DPU via the BMC.

13. The method of claim 12 , further comprising monitoring a status of the second installation workflow via one or more status updates received from the BMC.

14. At least one non-transitory, computer-readable medium comprising machine-readable instructions that, when executed by a central processing unit (CPU) of a computing device, cause the computing device to at least:

obtain a unified boot image comprising installation data associated with a first installation workflow for configuring a first hypervisor on the computing device and an installation depot associated with a second installation workflow for configuring a second hypervisor on a data processing unit (DPU);

identify the installation depot associated with the second installation workflow in the unified boot image;

create a DPU boot image based at least in part on the installation depot and a format compatible with the DPU; and

cause the DPU to execute the second installation workflow using the DPU boot image.

15. The at least one non-transitory, computer-readable medium of claim 14 , wherein the machine-readable instructions further cause the computing device to at least execute the first installation workflow based at least in part on the installation data in the unified boot image.

16. The at least one non-transitory, computer-readable medium of claim 14 , wherein the machine-readable instructions further cause the computing device to at least convert the installation depot into the format using a packaging kit.

17. The at least one non-transitory, computer-readable medium of claim 14 , wherein the DPU comprises at least one smart network interface card, the at least one smart network interface card comprising an additional CPU that can execute a storage task or a networking task on behalf of the CPU of the computing device.

18. The at least one non-transitory, computer-readable medium of claim 14 , wherein causing the at least one DPU to execute the second installation workflow using the DPU boot image comprises:

initiating communication with the at least one DPU via a baseboard management controller (BMC); and

providing the DPU boot image to the at least one DPU via the BMC.

19. The at least one non-transitory, computer-readable medium of claim 18 , wherein the machine-readable instructions further cause the computing device to monitor a status of the second installation workflow via one or more status updates received from the BMC.

20. The at least one non-transitory, computer-readable medium of claim 14 , wherein the machine-readable instructions further cause the computing device to receiving configuration data associated with the second installation workflow, the DPU boot image being embedded with the configuration data.

Assignments (3)
CHANGE OF NAME Recorded May 8, 2024
From: VMWARE, INC.
To: VMWARE LLC
Reel/Frame 067355/0001 →
CHANGE OF NAME Recorded May 6, 2024
From: VMWARE, INC.
To: VMWARE LLC
Reel/Frame 067328/0361 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 10, 2022
From: HARYADI, ARAVINDA; RAMACHANDRA, KARTHIK; BORO, SUMAN
To: VMWARE, INC.
Reel/Frame 061359/0548 →
Priority Claims (1)
IN 202241041222 · Jul 19, 2022 · national
Continuity (1)
Related Publication 20240028343A1 · Jan 25, 2024