Virtual Machines Backed by Host Virtual Memory

• US 20160299712A1
• Filed: 04/27/2015
• Published: 10/13/2016
• Est. Priority Date: 04/07/2015
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Kishan, Arun U., Wang, Landy, Iyigun, Mehmet, Broas, Kevin Michael, Bak, Yevgeniy M.
• Application Number:
  US14/697,398
• Publication Number:
  US 20160299712A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 12/0891 using clearing, invalidating or resetting means
• CPC Class Codes: G06F 12/1027 using associative or pseudo-associative address translation means, e.g. translation look-aside buffer [TLB]
• CPC Class Codes: G06F 12/109 for multiple virtual address spaces, e.g. segmentation G06F12/1036 takes precedence
• CPC Class Codes: G06F 2009/45583 Memory management, e.g. access or allocation
• CPC Class Codes: G06F 2212/1016 Performance improvement
• CPC Class Codes: G06F 2212/151 Emulated environment, e.g. virtual machine
• CPC Class Codes: G06F 2212/50 Control mechanisms for virtual memory, cache or TLB
• CPC Class Codes: G06F 2212/60 Details of cache memory
• CPC Class Codes: G06F 2212/656 Address space sharing
• CPC Class Codes: G06F 3/0604 Improving or facilitating administration, e.g. storage management
• CPC Class Codes: G06F 3/0619 in relation to data integrity, e.g. data losses, bit errors
• CPC Class Codes: G06F 3/0631 by allocating resources to storage systems
• CPC Class Codes: G06F 3/065 Replication mechanisms
• CPC Class Codes: G06F 3/0664 at device level, e.g. emulation of a storage device or system
• CPC Class Codes: G06F 3/0671 In-line storage system
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects
• CPC Class Codes: G06F 9/5016 the resource being the memory

Abstract

A host machine having guest virtual machine physical memory backed by host virtual memory is described. The host machine includes host physical memory. The host machine further includes one or more guest virtual machines. Each of the guest virtual machines includes guest physical memory. The host machine further includes host virtual memory. The host machine further includes a data structure having a correlation of guest physical memory addresses to host virtual memory addresses and a data structure having a correlation of host virtual memory addresses to host physical memory addresses.

Claims

1. In a virtual computing environment, a system for backing guest physical memory with host virtual memory, the system comprising:

a guest virtual machine on a host machine, wherein the guest virtual machine is configured to access guest physical memory;

a second level address translation table (SLAT) that correlates guest physical memory addresses with host physical memory addresses;

a virtualization stack configured to correlate guest physical memory addresses with host virtual memory addresses;

a memory manager configured to correlate host virtual memory addresses with host physical memory addresses;

a hypervisor configured to receive an intercept when a guest virtual machine guest physical memory access refers to a guest physical memory address that does not have a valid entry in the SLAT and to forward the intercept to the virtualization stack; and

wherein the virtualization stack is configured to;

identify a host virtual machine memory address corresponding to a guest physical machine memory address from the guest virtual machine guest physical memory access;

obtain from the memory manager a host physical machine memory address corresponding to the host virtual memory address; and

update the SLAT with a correlation of the guest physical memory address and the host physical memory address.

2. The system of claim 1, further comprising one or more host processes where host virtual memory is implemented.

3. A host machine, wherein the host machine comprises:

host physical memory;

one or more guest virtual machines, wherein each of the guest virtual machines comprises guest physical memory;

host virtual memory;

a data structure having a correlation of guest physical memory addresses to host virtual memory addresses; and

a data structure having a correlation of host virtual memory addresses to host physical memory addresses.

4. The host machine of claim 3, wherein the virtual memory is included as part of a user process being run on the host machine.

5. The host machine of claim 4, wherein the host machine is configured to back guest physical memory of the guest virtual machines by allocating virtual memory in user processes for use by guest physical memory with a different user processes being used for each guest virtual machine.

6. The host machine of claim 4, wherein the host machine is configured to back guest physical memory of the guest virtual machines by allocating virtual memory in one or more user processes for use by guest physical memory with a user process being used for a plurality of guest virtual machines.

7. The host machine of claim 3, wherein the virtual memory is included as part of a kernel virtual address space.

8. The host machine of claim 3, further comprising a virtualization stack that is configured to allocate host virtual memory to guest physical memory.

9. The host machine of claim 8, wherein the virtualization stack comprises the data structure having the correlation of guest physical memory addresses to host virtual memory addresses.

10. The host machine of claim 8, wherein the host machine further comprises one or more second level address tables (SLATs) that correlate guest physical memory addresses with host physical memory addresses and wherein the virtualization stack is configured to intercept translation buffer flushes and based on the intercepted translation buffer flushes, identify entries in the SLATs to be invalidated.

11. The host machine of claim 8, wherein the host machine further comprises one or more second level address tables (SLATs) that correlate guest physical memory addresses with host physical memory addresses and a hypervisor and wherein hypervisor is configured to receive guest access intercepts when a SLAT does not contain a valid entry for a guest physical memory access and to forward the guest access intercepts to the virtualization stack;

and wherein the virtualization stack is configured to identify host virtual memory corresponding to the guest physical memory accesses such that the SLATs can be updated to correlate addresses for the guest physical memory accesses with a host physical memory addresses.

12. The host machine of claim 3, further comprising a memory manager, and wherein the memory manager stores the data structure having a correlation of host virtual memory addresses to host physical memory addresses.

13. The host machine of claim 3, further comprising a memory manager, and wherein the memory manager is configured to manage guest physical memory by managing host virtual memory.

14. The host machine of claim 13, further comprising a hypervisor, and wherein the hypervisor is configured to offload management of guest physical memory to the memory manager.

15. In a virtual computing environment, a method of backing guest physical memory with host virtual memory, the method comprising:

at guest virtual machine on a host, attempting to access guest physical memory using a guest physical memory access;

determining that the guest physical memory access refers to a guest physical memory address that does not have a valid entry in a data structure that correlates guest physical memory addresses with host physical memory addresses;

as a result, identifying a host virtual memory address that corresponds to the guest physical memory address and identifying a host physical memory address that corresponds to the host virtual memory address; and

updating the data structure that correlates guest physical memory addresses with host physical memory addresses with a correlation of the guest physical memory address and the identified host physical memory address.

16. The method of claim 15, wherein determining that the guest physical memory access refers to a guest physical memory address that does not have a valid entry in a data structure that correlates guest physical memory addresses with host physical memory addresses causes an intercept that is forwarded to a virtualization stack on the host which causes the virtualization stack to identify the host virtual memory address that corresponds to the guest physical memory address and to issue a fault to a memory manager to obtain the host physical memory address that corresponds to the host virtual memory address, and to update the data structure that correlates guest physical memory addresses with host physical memory addresses with a correlation of the guest physical memory address and the identified host physical memory address.

17. The method of claim 15, further comprising determining a type for the guest physical memory access and updating the data structure that correlates guest physical memory addresses with host physical memory addresses with the determined type correlated to the guest physical memory address and the identified host physical memory address.

18. The method of claim 15, further comprising performing an action that may change a host physical memory address backing the host virtual memory address, and as a result, invalidating an entry correlating the guest physical memory address with the host physical memory address in the data structure that correlates guest physical memory addresses with host physical memory addresses which causes subsequent access to the guest physical memory address to generate a fault which can be used to update the data structure that correlates guest physical memory addresses with host physical memory addresses with a correct correlation for host virtual memory backing the guest physical memory address.

19. The method of claim 18, wherein the action comprises a page combining operation.

20. The method of claim 15 further comprising, initializing the guest virtual machine, and as part of initializing guest virtual machine, prepopulating at least a portion of the data structure that correlates guest physical memory addresses with host physical memory addresses with some or all guest physical memory address to host physical memory address mappings for the guest virtual machine.