Application publishing using memory state sharing

Patent metadata

Field	Value
Publication number	US-9998467-B2
Application number	US-201715436506-A
Country	US
Kind code	B2
Filing date	Feb 17, 2017
Priority date	Aug 23, 2014
Publication date	Jun 12, 2018
Grant date	Jun 12, 2018

Abstract

Examples described herein enable memory state sharing among a plurality of virtual machines (VM) including a parent VM and a child VM. A request for memory state sharing between the parent VM and the child VM is received, and the parent VM is suspended. The child VM resumes execution of one or more suspended applications. In one example, the child FM is forked with pre-loaded, suspended applications from the parent VM. Aspects of the disclosure offer a high performance, resource efficient solution that outperforms traditional approaches in areas of software compatibility, stability, quality of service control, re-source utilization, and more.

First claim

We claim:

1. A method comprising:
receiving a request by a user of a child virtual machine (“VM”) to execute an application;
determining that the application is a pre-launched application that is suspended on a parent VM;
in response to a determination that the application is suspended, creating a network security token for the suspended application, wherein the network security token is based on an identify of a user;
binding the network security token to the suspended application; and
resuming execution of the suspended application using the network security token.

2. The method of claim 1 , wherein binding the network security token to the application comprises calling a new application program interface to perform a local login and specifying new credentials that define a valid network token using the identity of the user.

3. The method of claim 2 , further comprising replacing an existing network security token on the child VM with the created network security token.

4. The method of claim 3 , wherein the created network security token defines the identity of the application in the child VM on a network and wherein the identity of the application in the child VM on a local machine is the local account of the user.

5. The method of claim 1 , wherein one or more code pages of the application is locked into memory of the parent VM such that the application code pages are resident in memory of the parent VM.

6. The method of claim 5 , where resuming execution of the suspended application includes resuming execution of the application on the child VM using the locked code pages of the application.

7. A system comprising:
one or more computers including one or more processors and a memory area associated with a computing device and including data shared among a plurality of virtual machines (“VMs”) including a parent VM and a child VM, wherein the one or more computers include instructions that when executed by the processor cause the one or more processors to perform operations comprising:
receiving a request by a user of a child VM to execute an application;
determining that the application is a pre-launched application that is suspended on a parent VM;
in response to a determination that the application is suspended, creating a network security token for the suspended application, wherein the network security token is based on an identify of a user;
binding the network security token to the suspended application; and
resuming execution of the suspended application using the network security token.

8. The system of claim 7 , wherein binding the network security token to the application comprises calling a new application program interface to perform a local login and specifying new credentials that define a valid network token using the identity of the user.

9. The system of claim 8 , wherein the instructions are further configured to perform operations comprising replacing an existing network security token on the child VM with the created network security token.

10. The system of claim 9 , wherein the created network security token defines the identity of the application in the child VM on a network and wherein the identity of the application in the child VM on a local machine is the local account of the user.

11. The system of claim 7 , wherein one or more code pages of the application is locked into memory of the parent VM such that the application code pages are resident in memory of the parent VM.

12. The system of claim 11 , where resuming execution of the suspended application includes resuming execution of the application on the child VM using the locked code pages of the application.

13. One or more non-transitory computer-readable storage media including computer-executable instructions that, when executed, cause one or more processors to perform operations comprising:
receiving a request by a user of a child virtual machine (“VM”) to execute an application;
determining that the application is a pre-launched application that is suspended on a parent VM;
in response to a determination that the application is suspended, creating a network security token for the suspended application, wherein the network security token is based on an identify of a user;
binding the network security token to the suspended application; and
resuming execution of the suspended application using the network security token.

14. The one or more non-transitory computer-readable storage media of claim 13 , wherein binding the network security token to the application comprises calling a new application program interface to perform a local login and specifying new credentials that define a valid network token using the identity of the user.

15. The one or more non-transitory computer-readable storage media of claim 14 , further comprising instructions that cause the one or more processors to perform operations comprising: replacing an existing network security token on the child VM with the created network security token.

16. The one or more non-transitory computer-readable storage media of claim 15 , wherein the created network security token defines the identity of the application in the child VM on a network and wherein the identity of the application in the child VM on a local machine is the local account of the user.

17. The one or more non-transitory computer-readable storage media of claim 13 , wherein one or more code pages of the application is locked into memory of the parent VM such that the application code pages are resident in memory of the parent VM.

Assignees

• Vmware Inc

Inventors

• Beveridge Daniel James
• Watts Blake
• Larsson Per Olov
• Agrawal Banit
• Li Hui

Classifications

• G06F9/45558 Primary

  Hypervisor-specific management and integration aspects · CPC title

• G06F2009/45562

  Creating, deleting, cloning virtual machine instances · CPC title

• G06F9/455

  Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines · CPC title

• G06F2009/45575

  Starting, stopping, suspending or resuming virtual machine instances · CPC title

• G06F9/52

  Program synchronisation; Mutual exclusion, e.g. by means of semaphores · CPC title