Abstract:
Techniques for virtual machine (VM) availability during management network failure and VM network failure in a first host computing system in a failover cluster are described. In one example embodiment, management network failure is identified in the first host computing system. The management network being coupled to a virtual management software in a management server and used for management functions. Migration of the VMs running on the first host computing system is then initiated to at least one other host computing system in the failover cluster via a migration network by a failover agent associated with the first host computing system. The migration network being isolated from the virtual management software and capable of handling live migrations.
Abstract:
Techniques for placing a first network device into maintenance mode are described. In one embodiment, a first host computing system coupled to the first network device is identified. The first host computing system executes a workload that transmits and receives network traffic via the first network device. If the first host computing system is not coupled to any other network device, the network traffic to the first network device is quiesced by initiating migration of the workload to a second host computing system coupled to any other network device. If the first host computing system is coupled to a second network device, the network traffic to the first network device is quiesced by instructing a virtual switch of the first host computing system to route the network traffic between the workload and the second network device, and cease routing the network traffic between the workload and the first network device.
Abstract:
A method and system include compatibly interfacing a suitably adapted central switch in a computer network virtualization environment to one or more user-end peripheral device(s) to dispense with a need for a user-end thin client. The method and system also include appropriately routing a data associated with a direct and exclusive communication between a virtual machine on a host server including a number of virtual machines and the one or more user-end peripheral device(s) using the central switch.
Abstract:
Techniques for centralized management of network switch operations across multiple virtualization platforms via a “spanned distributed virtual switch.” These techniques generally include creating a distributed virtual switch for each virtual platform that participates in the spanned distributed virtual switch, configuring each such distributed virtual switch with a mutually exclusive set of ports, configuring each distributed virtual switch with network configuration information for associated sets of ports, and synchronizing the network configuration information across distributed virtual switches. When configuration information changes in one distributed virtual switch, those changes are synchronized across other distributed virtual switches that participate in the spanned distributed virtual switch. A computer system, method, and computer-readable medium are provided herein.
Abstract:
Techniques for placing virtual machines based on compliance of device profiles are disclosed. In one embodiment, a list of device profiles may be maintained, with each device profile including details of at least one virtual device and associated capabilities. Further, a device profile from the list of device profiles may be assigned to a virtual machine running on a first host computing system. A virtual device and associated configurations required by the virtual machine may be identified to comply with the device profile. A management operation may be performed to migrate or clone the virtual device and associated configurations from a second host computing system to the first host computing system to support the compliance of the device profile assigned to the virtual machine.
Abstract:
A system and method for responding to a virtual machine (VM) network failure for a host in a network partition in a high availability (HA) cluster. The method includes providing a plurality of network partition response options; and receiving a selection of a first network partition response option from the plurality of network partition response options, the selected first network partition response option causing a processor to transfer execution of a VM on the host to a second host that has VM network connectivity upon detecting a VM network failure for the host.
Abstract:
Examples provide a pooled memory heartbeat for virtual machine hosts. A virtual controller creates a pooled memory heartbeat file system in a shared memory partition of a pooled memory. An agent running on each host in a plurality of virtual machine hosts updates a heartbeat file at an update time interval to lock the heartbeat file. The lock indicates the heartbeat status for a given host is active. A master agent accesses the shared memory partition to check the heartbeat status of each host in the pooled memory file system. The heartbeat status is used to determine whether a host that has lost pooled memory access, is network isolated, or failed. If the pooled memory heartbeat status for a given host indicates the host is a failed host, the set of virtual machines running on the given host are respawned on another healthier host.
Abstract:
Examples provide for virtual machine recovery using pooled memory. A shared partition is created on pooled memory accessible by a plurality of virtual machine hosts. A set of memory pages for virtual machines running on the hosts is moved to the shared partition. A master agent polls memory page tables associated with the plurality of hosts for write access. If the master agent obtains write access to a memory page table of a given host, the given host that previously held the write access is identified as a failed host or an isolated host. The virtual machines of the given host enabled to resume from pooled memory are respawned on a new host while maintaining memory state of the virtual machines using data within the pooled memory, including the virtual machine memory pages, memory page table, host profile data, and/or host-to-VM table data.
Abstract:
Techniques for placing virtual machines based on compliance of device profiles are disclosed. In one embodiment, a list of device profiles may be maintained, with each device profile including details of at least one virtual device and associated capabilities. Further, a device profile from the list of device profiles may be assigned to a virtual machine running on a first host computing system. A virtual device and associated configurations required by the virtual machine may be identified to comply with the device profile. A management operation may be performed to migrate or clone the virtual device and associated configurations from a second host computing system to the first host computing system to support the compliance of the device profile assigned to the virtual machine.
Abstract:
Techniques for security scanning of containers executing within VMs. A virtualization system maintains container disk files that store data for containers. The container disk files are stored separate from, and not included within, virtual machine disk files that store data for the virtual machines. To scan data for any particular container, a scanning module scans the container disk file associated with the container. If a threat is found, a container scan catalog is updated to indicate this fact. A container may be disconnected from the network if identified security threats cannot be removed from the container. An entire VM may be disconnected from the network if all containers within the VM have threats that cannot be cleaned. The use of container disk files for security threat scanning allows for data for individual containers to be scanned.