US 12,003,377 B1
Distributed computing system with hypervisor mobility service
Shivjit Satish Patil, Chapel Hill, NC (US); Rupesh Bhagaban Patro, Redmond, WA (US); Kenyon James Hensler, Acworth, GA (US); Aishwarya Srinivasa Raghavan, Sammamish, WA (US); Rangaprasad Narasimhan, Sammamish, WA (US); and Anand Ramakrishna, Redmond, WA (US)
Assigned to Microsoft Technology Licensing, LLC, Redmond, WA (US)
Filed by Microsoft Technology Licensing, LLC, Redmond, WA (US)
Filed on Dec. 16, 2022, as Appl. No. 18/067,435.
Int. Cl. H04L 41/0895 (2022.01); G06F 9/455 (2018.01); H04L 61/5084 (2022.01); H04L 101/668 (2022.01)
CPC H04L 41/0895 (2022.05) [G06F 9/45558 (2013.01); H04L 61/5084 (2022.05); H04L 2101/668 (2022.05)] 18 Claims
OG exemplary drawing
 
1. A distributed computing system, comprising:
a server executing a mobility service;
a first computing device executing a first hypervisor implementing a first mobility client configured to:
detect an attachment of a virtual machine to the first hypervisor;
responsive to detecting the attachment of the virtual machine to the first hypervisor, increment a first mobility sequence number; and
send to the mobility service a notification of the attachment of the virtual machine to the first hypervisor;
a second computing device executing a second hypervisor implementing a second mobility client configured to:
detect an attachment of the virtual machine to the second hypervisor;
send a message to the first computing device indicating the attachment of the virtual machine to the second hypervisor;
responsive to detecting the attachment of the virtual machine to the second hypervisor, increment a second mobility sequence number; and
send to the mobility service a notification of the attachment of the virtual machine to the second hypervisor,
wherein the first mobility client is further configured to:
based at least on the message, store network routing information indicating a network location of the virtual machine as attached to the second hypervisor;
receive network traffic for the virtual machine that was routed to the first hypervisor at the first computing device; and
forward the network traffic for the virtual machine from the first computing device to the second hypervisor implemented on the second computing device based on the stored network routing information, and
wherein a tracking service determines whether the virtual machine is attached to the first hypervisor or the second hypervisor based on determining which of the first mobility sequence number and the second mobility sequence number is larger.