Method and system for providing a roaming remote desktop

• US 10,389,852 B2
• Filed: 06/29/2015
• Issued: 08/20/2019
• Est. Priority Date: 03/06/2013
• Status: Active Grant

• Current Assignee: Vmware LLC (Broadcom, Inc.)
• Original Assignee: VMware, Inc. (Broadcom, Inc.)
• Inventors: Antony, Jinto
• Primary Examiner(s): Chang, Tom Y
• Application Number:
  US14/754,165
• Publication Number:
  US 20150304455A1
• Time in Patent Office: 1,513 Days
• CPC Class Codes: G06F 11/1458 Management of the backup or restore process
• 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 9/45558 Hypervisor-specific management and integration aspects
• CPC Class Codes: G06F 9/4856 resumption being on a different machine, e.g. task migration, virtual machine migration G06F9/5088 takes precedence
• CPC Class Codes: G06F 9/5027 the resource being a machine, e.g. CPUs, Servers, Terminals
• CPC Class Codes: G06F 9/5088 involving task migration
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
• CPC Class Codes: H04L 67/133 Protocols for remote procedure calls [RPC]

Abstract

Techniques are disclosed for migrating a linked clone virtual machine (VM) based on a location of a client device. In one embodiment, a client device transmits its location to a VM management center, and a migration application running thereon determines whether the client device and a linked clone VM to which the client device is attempting to connect are at the same location. If the client device and the linked clone VM are not at the same location, the migration application identifies a VM hosting site proximate to the client device, and instructs a hypervisor to “cold” migrate the linked clone VM and its associated redo log to a VM host and a storage device, respectively, at the identified VM hosting site. The link clone VM may then be “actively” linked to a base VM at the VM hosting site, while maintaining “passive” links to base VM(s) at other locations.

Claims

1. A method for providing a roaming remote desktop, comprising:

maintaining, at a first virtual machine (VM) hosting site, a chain of delta disks for a linked clone VM, wherein metadata of the chain of delta disks indicates a base VM at the first VM hosting site to which the linked clone VM is actively linked and a second base VM at a second VM hosting site to which the linked clone VM is passively linked, wherein a first delta disk of the chain of delta disks points to the base VM to which the linked clone VM is actively linked, and wherein each subsequent delta disk in the chain of delta disks points to a previous delta disk in the chain of delta disks; and

responsive to receiving an updated location of a client device;

migrating the linked clone VM and the chain of delta disks including the metadata from the first VM hosting site to the second VM hosting site, wherein the metadata includes an active and passive links information maintained in a file representing a redo log of the linked clone VM, and

at the second VM hosting site, after the migrating, changing the metadata of the migrated chain of delta disks to indicate that the linked clone VM is actively linked to the second base VM at the second VM hosting site and passively linked to the base VM at the first VM hosting site, wherein updates to a first base disk is automatically propagated to a second base disk based on the active and passive links.

2. The method of claim 1, wherein the second VM hosting site is chosen from a plurality of VM hosting sites as a migration destination for the linked clone VM based on proximity to the updated location of the client device.

3. The method of claim 2, wherein proximity to the updated location of the client device includes at least one of being within a given radius, being in a same city, being in a same country, being in a same office, being physically closest to the client device, and having less than a given latency.

4. The method of claim 2, wherein proximity to the updated location of the client device is determined based on location information received from the client device including at least one of latitude and longitude, an internet protocol (IP) address of a Wi-Fi router, an IP address of an internet service provider, and a private IP address.

5. The method of claim 1,

wherein the updated location of the client device is received during an attempt by the client device to connect to the linked clone VM, and

wherein the migration is performed before the client device is connected to the linked clone VM.

6. The method of claim 1, wherein the updated location of the client device is received after the client device connects to a different Wi-Fi router or internet service provider (ISP).

7. The method of claim 1,

wherein the base VM at the first VM hosting site and the second base VM at the second VM hosting site have identical base disks.

8. The method of claim 1, wherein the migration of the linked clone VM is a cold migration in which the linked clone VM is migrated in a powered off state.

21. The method of claim 1, wherein the metadata, before and after the migrating, further indicates a third base VM at a third VM hosting site to which the linked clone VM is passively linked.

9. A non-transitory computer-readable storage medium embodying computer program instructions to performing a method for providing a roaming remote desktop, the method comprising:

maintaining, at a first virtual machine (VM) hosting site, a chain of delta disks for a linked clone VM, wherein metadata of the chain of delta disks indicates a base VM at the first VM hosting site to which the linked clone VM is actively linked and a second base VM at a second VM hosting site to which the linked clone VM is passively linked, wherein a first delta disk of the chain of delta disks points to the base VM to which the linked clone VM is actively linked, and wherein each subsequent delta disk in the chain of delta disks points to a previous delta disk in the chain of delta disks; and

responsive to receiving an updated location of a client device, migrating the linked clone VM and the chain of delta disks including the metadata from the first VM hosting site to the second VM hosting site, wherein the metadata includes an active and passive links information maintained in a file representing a redo log of the linked clone VM, such that, at the second VM hosting site, after the migrating, the metadata of the migrated chain of delta disks is changed to indicate that the linked clone VM is actively linked to the second base VM at the second VM hosting site and passively linked to the base VM at the first VM hosting site, wherein updates to a first base disk is automatically propagated to a second base disk based on the active and passive links.

10. The non-transitory computer-readable storage medium of claim 9, wherein the second VM hosting site is chosen from a plurality of VM hosting sites as a migration destination for the linked clone VM based on proximity to the updated location of the client device.

11. The non-transitory computer-readable storage medium of claim 10, wherein proximity to the updated location of the client device includes at least one of being within a given radius, being in a same city, being in a same country, being in a same office, being physically closest to the client device, and having less than a given latency.

12. The non-transitory computer-readable storage medium of claim 10, wherein proximity to the updated location of the client device is determined based on location information received from the client device including at least one of latitude and longitude, an internet protocol (IP) address of a Wi-Fi router, an IP address of an internet service provider, and a private IP address.

13. The non-transitory computer-readable storage medium of claim 9,

wherein the updated location of the client device is received during an attempt by the client device to connect to the linked clone VM, and

wherein the migration is performed before the client device is connected to the linked clone VM.

14. The non-transitory computer-readable storage medium of claim 9, wherein the updated location of the client device is received after the client device connects to a different Wi-Fi router or internet service provider (ISP).

15. The non-transitory computer-readable storage medium of claim 9,

wherein the base VM at the first VM hosting site and the second base VM at the second VM hosting site have identical base disks.

16. The non-transitory computer-readable storage medium of claim 9, wherein the migration of the linked clone VM is a cold migration in which the linked clone VM is migrated in a powered off state.

22. The non-transitory computer-readable storage medium of claim 9, wherein the metadata, before and after the migrating, further indicates a third base VM at a third VM hosting site to which the linked clone VM is passively linked.

17. A system, comprising:

a processor; and

a memory, wherein the memory includes a program for reducing perceived read latency, the program being configured to perform operations for providing a roaming desktop, comprising;

maintaining, at a first virtual machine (VM) hosting site, a chain of delta disks for a linked clone VM, wherein metadata of the chain of delta disks indicates a base VM at the first VM hosting site to which the linked clone VM is actively linked and a second base VM at a second VM hosting site to which the linked clone VM is passively linked, wherein a first delta disk of the chain of delta disks points to the base VM to which the linked clone VM is actively linked, and wherein each subsequent delta disk in the chain of delta disks points to a previous delta disk in the chain of delta disks; and

responsive to receiving an updated location of a client device, migrating the linked clone VM and the chain of delta disks including the metadata from the first VM hosting site to the second VM hosting site, wherein the metadata includes an active and passive links information maintained in a file representing a redo log of the linked clone VM;

such that, at the second VM hosting site, after the migrating, the metadata of the migrated chain of delta disks is changed to indicate that the linked clone VM is actively linked to the second base VM at the second VM hosting site and passively linked to the base VM at the first VM hosting site, wherein updates to a first base disk is automatically propagated to a second base disk based on the active and passive links.

18. The system of claim 17, wherein the second VM hosting site is chosen from a plurality of VM hosting sites as a migration destination for the linked clone VM based on proximity to the updated location of the client device.

19. The system of claim 17,

wherein the updated location of the client device is received during an attempt by the client device to connect to the linked clone VM, and

wherein the migration is performed before the client device is connected to the linked clone VM.

20. The system of claim 17, wherein the updated location of the client device is received after the client device connects to a different Wi-Fi router or internet service provider (ISP).

23. The system of claim 17, wherein the metadata, before and after the migrating, further indicates a third base VM at a third VM hosting site to which the linked clone VM is passively linked.