Abstract: Responsive to receiving a first request from an application to create a thread for the application, a guest operating system sends a first notification to a hypervisor to create a dedicated virtual processor for the thread. Responsive to receiving an identifier associated with the dedicated virtual processor from the hypervisor, the guest operating system starts the thread using the dedicated virtual processor, and pins the thread to the dedicated virtual processor.

Abstract: A migration system includes a memory, a physical processor in communication with the memory, a first device, a second device, a first hypervisor at a source location, a second hypervisor at a destination location, a first virtual machine, and a second virtual machine. The first virtual machine includes a guest OS executing on the first hypervisor and a guest driver and the second virtual machine includes the guest OS executing on the second hypervisor and the guest driver. The first and second hypervisors send a request to save a device state to the guest driver in the guest OS executing on the first hypervisor and send a migration notification to the guest OS executing on the second hypervisor. The guest driver saves a state signature in the memory. The guest driver determines a status of the state signature as one of matching the second device and mismatching the second device.

Abstract: An error recovery system includes a memory, a processor in communication with the memory, a primary device, a backup device, a hypervisor executing on the processor, and a virtual machine. The virtual machine includes a guest operating system (OS) executing on the hypervisor, a pass-through device, and a guest driver. The hypervisor executes to detect an error associated with the primary device and to send a request to save a device state to the guest driver. The hypervisor also grants the guest OS access to the backup device. The guest driver receives the request from the hypervisor, and responsive to receiving the request, saves a state signature in the memory. The state signature includes a device signature and the device state of the primary device. Additionally, the guest driver determines a status of the device signature as one of matching and mismatching the backup device.

Abstract: An indication that a virtual machine has been migrated may be received. In response to receiving the indication, one or more network addresses associated with the virtual machine may be identified. A notification message corresponding to the one or more network addresses may be generated. The notification message may be transmitted on networks for the one or more network addresses. The virtual machine may determine whether a response message has been received for each of the one or more network addresses. The virtual machine may transmit a subsequent notification message in view of determining that at least one response message has not been received for at least one of the one or more network addresses.

Abstract: A method includes receiving, by a processing device of a monitoring node, an indication over a network that a virtual machine successfully migrated from a first host to a second host. The indication includes a virtual machine address of the virtual machine executing on the second host. The method also includes, responsive to the indication that the virtual machine successfully migrated from the first host to the second host, starting to monitor incoming packets of the monitoring node for an incoming packet that includes a source address field having the virtual machine address, and, upon determining, after a threshold period of time, that none of the incoming packets include the source address field having the virtual machine address, notifying a reporting node that the incoming packet was not received to facilitate performance of an action to reduce downtime of communication with the virtual machine over the network.

Abstract: Systems and methods for implementing guest-initiated announcement of virtual machine migration. An example method may comprise: receiving, by an origin hypervisor running on an origin computer system, a migration announcement of a virtual machine; copying at least a part of a state of the virtual machine to a destination computer system; and responsive to stopping the virtual machine on the origin computer system, causing a destination hypervisor running on the destination computer system to broadcast the migration announcement over a network associated with the destination computer system.

Abstract: A hypervisor may identify that a virtual machine has been migrated to the hypervisor from another hypervisor. In response to identifying that the virtual machine has been migrated, the hypervisor may provide a notification message including one or more network addresses associated with the migrated virtual machine. The hypervisor may receive network traffic data and determine that the received network traffic data corresponds to a response message for at least one of the one or more network addresses associated with the migrated virtual machine. The hypervisor may determine that each of the one or more network addresses has not received the response message and provide a subsequent notification message.

Abstract: A system and method of translation bypass includes a hypervisor configuring a host input-output memory management unit to translate a guest memory of a guest virtual machine. The hypervisor reserves a first portion of the guest memory. The hypervisor receives, from the guest virtual machine, a guest physical address. The hypervisor stores the guest physical address in the first portion of the guest memory. The hypervisor configures a device to access the first portion of the guest memory to locate a command.

Abstract: Responsive to receiving a first request from an application to create a thread for the application, a guest operating system sends a first notification to a hypervisor to create a dedicated virtual processor for the thread. Responsive to receiving an identifier associated with the dedicated virtual processor from the hypervisor, the guest operating system starts the thread using the dedicated virtual processor, and pins the thread to the dedicated virtual processor.

Abstract: An error recovery system includes a memory, a processor in communication with the memory, a primary device, a backup device, a hypervisor executing on the processor, and a virtual machine. The virtual machine includes a guest operating system (OS) executing on the hypervisor, a pass-through device, and a guest driver. The hypervisor executes to detect an error associated with the primary device and to send a request to save a device state to the guest driver. The hypervisor also grants the guest OS access to the backup device. The guest driver receives the request from the hypervisor, and responsive to receiving the request, saves a state signature in the memory. The state signature includes a device signature and the device state of the primary device. Additionally, the guest driver determines a status of the device signature as one of matching and mismatching the backup device.

Abstract: A system and method of translation bypass includes a hypervisor retrieving a physical bus address range from a host input-output memory management unit. The hypervisor reserves an allowed address range of the physical bus address range, and sends the allowed address range to a guest virtual machine. Sending the allowed address range sets a guest bus address range mapped by a virtual input-output memory management unit. The guest virtual machine is prevented from accessing any bus address outside of the allowed address range. The hypervisor receives, from the guest virtual machine, an access request to a guest bus address, which is an address within the allowed address range. The hypervisor stores the access request to the guest bus address in physical memory mapped in the host input-output memory management unit to an address outside of the allowed address range.

Abstract: Responsive to receiving a first request from an application to create a thread for the application, a guest operating system sends a first notification to a hypervisor to create a dedicated virtual processor for the thread. Responsive to receiving an identifier associated with the dedicated virtual processor from the hypervisor, the guest operating system starts the thread using the dedicated virtual processor, and pins the thread to the dedicated virtual processor.

Abstract: A system and method of translation bypass includes a hypervisor retrieving a physical bus address range from a host input-output memory management unit. The hypervisor reserves an allowed address range of the physical bus address range, and sends the allowed address range to a guest virtual machine. Sending the allowed address range sets a guest bus address range mapped by a virtual input-output memory management unit. The guest virtual machine is prevented from accessing any bus address outside of the allowed address range. The hypervisor receives, from the guest virtual machine, an access request to a guest bus address, which is an address within the allowed address range. The hypervisor stores the access request to the guest bus address in physical memory mapped in the host input-output memory management unit to an address outside of the allowed address range.

Abstract: A system and method of translation bypass includes a hypervisor configuring a host input-output memory management unit to translate a guest memory of a guest virtual machine. The hypervisor reserves a first portion of the guest memory. The hypervisor receives, from the guest virtual machine, a guest physical address. The hypervisor stores the guest physical address in the first portion of the guest memory. The hypervisor configures a device to access the first portion of the guest memory to locate a command.

Abstract: A migration system includes a memory, a physical processor in communication with the memory, a first device, a second device, a first hypervisor at a source location, a second hypervisor at a destination location, a first virtual machine, and a second virtual machine. The first virtual machine includes a guest OS executing on the first hypervisor and a guest driver and the second virtual machine includes the guest OS executing on the second hypervisor and the guest driver. The first and second hypervisors send a request to save a device state to the guest driver in the guest OS executing on the first hypervisor and send a migration notification to the guest OS executing on the second hypervisor. The guest driver saves a state signature in the memory. The guest driver determines a status of the state signature as one of matching the second device and mismatching the second device.

Abstract: Responsive to receiving a first request from an application to create a thread for the application, a guest operating system sends a first notification to a hypervisor to create a dedicated virtual processor for the thread. Responsive to receiving an identifier associated with the dedicated virtual processor from the hypervisor, the guest operating system starts the thread using the dedicated virtual processor, and pins the thread to the dedicated virtual processor.

Abstract: An error recovery system includes a memory, a processor in communication with the memory, a primary device, a backup device, a hypervisor executing on the processor, and a virtual machine. The virtual machine includes a guest operating system (OS) executing on the hypervisor, a pass-through device, and a guest driver. The hypervisor executes to detect an error associated with the primary device and to send a request to save a device state to the guest driver. The hypervisor also grants the guest OS access to the backup device. The guest driver receives the request from the hypervisor, and responsive to receiving the request, saves a state signature in the memory. The state signature includes a device signature and the device state of the primary device. Additionally, the guest driver determines a status of the device signature as one of matching and mismatching the backup device.