Microsoft Technology Licensing, LLC

Kenyon James Hensler

Anand Ramakrishna

Rangaprasad Narasimhan

Aishwarya Srinivasa Raghavan

Rupesh Bhagaban Patro

Shivjit Satish Patil

A distributed computing system is provided, including a source computing device implementing a source hypervisor executing a virtual machine, a source-side router coupled to the source hypervisor, a destination computing device implementing a destination hypervisor, and a destination-side router coupled to the destination hypervisor. The source hypervisor is connected to the destination hypervisor through a network. During a migration of the virtual machine from the source hypervisor to the destination hypervisor, the source-side router duplicates packets ingressing into the source-side router. The duplicated packets include a first set of packets and a second set of packets, where the first set of packets is routed to the virtual machine through the source hypervisor on the network, and the second set of packets is routed to the virtual machine through the destination hypervisor on the network.

Virtual machine migration on hypervisor network

A method for resolving address resolution protocol (ARP) requests includes, at an ARP listening entity of a computer network, receiving an ARP request for a MAC (media access control) address of a destination entity having a specified IP (internet protocol) address, the ARP request received from a requesting entity, wherein a design of the computer network prevents broadcast of the ARP request to the destination entity. An ARP response is transmitted to the requesting entity, the ARP response specifying a response MAC address to facilitate transmission, by the requesting entity, of a data packet targeting the response MAC address, and wherein prior to receipt of the data packet at the destination entity, the specified IP address is associated with an actual MAC address of the destination entity according to an IP-to-MAC mapping.

Address resolution protocol request resolution

Using a routing protocol for network port failover. A network stack, which does not perform reverse path forwarding, includes a first interface as a loopback interface that is assigned a first internet protocol (IP) address, a second interface to a first network port, and a third interface to a second network port. The routing protocol is configured to communicate over the second interface with a first port at remote network device(s), and to communicate over the third interface with a second port at the remote network device(s). A route comprising the first IP address is announced to the remote network device(s), and default route of the network stack is configured to egress IP packets via the second interface. Later, the routing protocol indicates that there is a forwarding failure associated with the second interface, and the default route is configured to egress IP packets via the third interface.

Using a routing protocol for network port failover

Aspects of the present disclosure relate to storage policy change usage estimation. In examples, a base storage utilization is generated for a storage object according to a current storage policy. The current storage policy may comprise a RAID ('redundant array of independent disks') level and/or a fault tolerance level with which the storage object is stored. An estimated storage utilization may then be generated for the storage object based on the base storage utilization and a new storage policy accordingly. Thus, the base storage utilization may omit or otherwise account for overhead associated with the RAID level and/or fault tolerance level indicated by the current storage policy, while the resulting estimated storage utilization may indicate an estimated physical storage utilization for the storage object if the new storage policy is implemented in place of the current storage policy.

Storage policy change usage estimation

A distributed computing system is provided, including a server executing a mobility service, and 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, and 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, and send a message to the first computing device indicating the attachment of the virtual machine to the second hypervisor. The first mobility client is further configured to store network routing information indicating a network location of the virtual machine, receive network traffic for the virtual machine, and forward the network traffic to the second hypervisor based on the stored network routing information.

Growing community of inventors

Acworth, GA, United States of America

Kenyon James Hensler