Provisioning customized virtual machines without rebooting

• US 10,203,978 B2
• Filed: 04/05/2016
• Issued: 02/12/2019
• Est. Priority Date: 12/20/2013
• Status: Active Grant

• Current Assignee: Vmware LLC (Broadcom, Inc.)
• Original Assignee: VMware, Inc. (Broadcom, Inc.)
• Inventors: Li, Hui, Beveridge, Daniel James, Chen, Oswald
• Primary Examiner(s): Truong, Camquy
• Application Number:
  US15/091,003
• Publication Number:
  US 20160217001A1
• Time in Patent Office: 1,043 Days
• CPC Class Codes: G06F 1/3287 by switching off individual functional units in the computer system
• CPC Class Codes: G06F 2009/45562 Creating, deleting, cloning virtual machine instances
• CPC Class Codes: G06F 2009/4557 Distribution of virtual machine instances; Migration and load balancing
• CPC Class Codes: G06F 2009/45575 Starting, stopping, suspending or resuming virtual machine instances
• CPC Class Codes: G06F 2009/45591 Monitoring or debugging support
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects

Abstract

Embodiments provision and customize virtual machines (VMs), such as desktop VMs, without rebooting the desktop VMs. In response to a request to provision the VMs, a computing device creates a clone VM from a parent VM template identified in the request. One or more customization that prompt rebooting of the clone VM are applied to the clone VM. The computing device instantiates a plurality of child VMs from the customized clone VM. A child VM configuration is applied to at least one of the instantiated child VMs without provoking a reboot of those child VMs.

Claims

1. A system comprising:

memory associated with a computing device, said memory storing a plurality of parent VM templates; and

a processor programmed to;

receive, by the computing device, a request to provision a plurality of desktop virtual machines (VMs), the request identifying one of the plurality of parent VM templates;

in response to the received request, create a clone VM from the identified parent VM template;

apply a first set of customizations to the done VM that include customizations common to each of the plurality of desktop VMs to be instantiated from the clone VM, the first set of customizations prompting the done VM to;

instantiate the plurality of desktop VMs from the clone VM having the first set of customizations; and

apply a respective second set of customizations specific to each of the one or snore desktop VMs without rebooting the one or more desktop VMs.

2. The system of claim 1, wherein the processor is further programmed to:

upon applying the first set of customizations, suspending the execution of the clone VM to prepare for instantiation of the one or more desktop VMs.

3. The system of claim 2, wherein the second set of customizations are applied after the first set of customizations are applied and upon instantiation of each requested desktop VM.

4. The system of claim 2, wherein instantiation of each requested desktop VM comprises forking the clone VM to create a linked clone requested desktop VM.

5. The system of claim 1, wherein the processor is further programmed to modify one or more of the requested desktop VMs to be a persistent desktop VM such that any subsequent power-on operations do not conflict with a forked state of the one or more modified desktop VMs.

6. The system of claim 5, wherein the modification occurs during migration of the corresponding desktop VM.

7. A method comprising:

receiving a request to provision a plurality of desktop virtual machines (VMs), the request identifying a parent VM template;

in response to the received request, creating a clone VM from the identified parent VM template;

applying a first set of customizations to the clone VM that include customizations common to each of the plurality of desktop VMs to be instantiated from the clone VM, the first set of customizations prompting the clone VM to reboot;

instantiating the plurality of desktop VMs from the clone VM having the first set of customizations; and

applying a respective second set of customizations specific to each of the one or more desktop VMs without rebooting the one or more desktop VMs.

8. The method of claim 7, further comprising:

upon applying the first set of customizations, suspending the execution of the clone VM to prepare for instantiation of the one or more desktop VMs.

9. The method of claim 7, wherein the second set of customizations are applied upon instantiation of each requested desktop VM.

10. The method of claim 9, wherein instantiation of the requested desktop VMs comprises forking each requested desktop VM.

11. The method of claim 7, further comprising modifying one or more of the requested desktop VMs to be a persistent desktop VM such that any subsequent power-on operations do not conflict with a forked state of the one or more modified desktop VMs.

12. The method of claim 11, wherein the modification occurs during migration of the corresponding desktop VMs.

13. The method of claim 7, wherein applying the first set of customizations comprises:

attaching one or more disks to the clone VM before rebooting of the clone VM;

rebooting the clone VM with the one or disks attached; and

customizing the clone VM to redirect data to the attached disks.

14. One or more non-transitory computer-readable media including computer-executable instructions that, when executed, cause at least one processor to perform operations comprising:

receiving a request to provision a plurality of desktop virtual machines (VMs), the request identifying a parent VM template;

in response to the received request, creating a clone VM from the identified parent VM template;

applying a first set of customizations to the clone VM that include customizations common to each of the plurality of desktop VMs to be instantiated from the clone VM, the first set of customizations prompting the clone VM to reboot;

instantiating the plurality of desktop VMS from the clone VM having the first set of customizations; and

applying a respective second set of customizations specific to each of the one or more desktop VMs without rebooting the one or more desktop VMs.

15. The non-transitory computer-readable media of claim 14, wherein the computer-executable instructions further cause the processor to perform operations comprising:

upon applying the first set of customizations, suspending the execution of the clone VM to prepare for instantiation of the one or more desktop VMs.

16. The non-transitory computer-readable media of claim 14, wherein the second set of customizations are applied upon instantiation of each requested desktop VM.

17. The non-transitory computer-readable media of claim 16, wherein instantiation of the requested desktop VM comprises forking each requested desktop VM.

18. The non-transitory computer-readable media of claim 14, wherein the computer-executable instructions further cause the processor to perform operations comprising modifying one or more of the requested desktop VMs to be a persistent desktop VM such that any subsequent power-on operations do not conflict with a forked state of the one or more modified desktop VMs.

19. The non-transitory computer-readable media of claim 18, wherein the modification occurs during migration of the corresponding desktop VM.

20. The non-transitory computer-readable media of claim 14, wherein applying the first set of customizations comprises:

attaching one or more disks to the clone VM before rebooting of the clone VM;

rebooting the clone VM with the one or disks attached; and

customizing the clone VM to redirect data to the attached disks.