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.
Abstract:
Particular embodiments change a current storage I/O path used by a host computer to access networked storage to an alternative storage I/O path by considering traffic load at a networked switch in the current storage I/O path. The host computer transmits a request to the networked switch in the current storage I/O path to provide network load information currently experiences by the networked switch. After receiving network load information from the networked switch, the host computer then evaluates whether the networked switch is overloaded based on the received network load information. Based on the evaluation, the host computer selects a new alternative storage I/O path to the networked storage that does not include the networked switch, and then forwards future storage I/O communications to the networked storage using the new alternative storage I/O path.
Abstract:
An example method is provided to perform power management for a distributed storage system accessible by a cluster in a virtualized computing environment. The method may comprise, in response to detecting that a power-off requirement of a host from the cluster is satisfied, retrieving virtual machine data from a first storage resource of the host, storing the virtual machine data on a second storage resource of the host, and powering off one or more components of the host. The second storage resource is configured to be accessible when the one or more components of the host are powered off.
Abstract:
Techniques for managing crash in a host computing system in a cluster are disclosed. In one embodiment, a core dump partition may be configured in memory associated with a remote access controller (RAC) within the host computing system. When the host computing system is crashed, a screen shot associated with the host computing system is obtained through the RAC. Further, a first occurrence of crash in the host computing system is determined based on the obtained screen shot. Furthermore, the core dump file associated with the first occurrence of crash is copied from the core dump partition to a shared datastore. Also, the host computing system is reset through the RAC upon copying the core dump file to the shared datastore.
Abstract:
Techniques for virtual machine (VM) management function availability during management network failure in a first host computing system in a cluster are described. In one example embodiment, management network failure is identified in the first host computing system. The management network being coupled to virtual management software in a management server and used for VM and host management functions. VM and host management functions on the first host computing system are then initiated via a failover agent associated with an active host computing system that is connected to the management network in the cluster and a shared storage network.
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.
Abstract:
Techniques for facilitating parallelized configuration of multiple virtual machines. The techniques include duplicating commands received from an administrator and controlling the multiple virtual machines with those commands in a parallel manner. Different types of commands are treated differently. More specifically, commands for controlling software executing in the virtual machines are replicated and sent to each virtual machine. By contrast, commands for managing virtual machines themselves are provided to virtualization software like a hypervisor to be executed. Duplication of the commands for controlling software executing in the virtual machines is performed by an input/output multiplexer, which also has the function of combining display output from each of the virtual machines. More specifically, the input/output multiplexer displays a common display output to the administrator, where the common display output is the screen that is shown on each of the virtual machines.
Abstract:
Techniques for providing a hyper-converged computing device with an integrated central virtualization switch is disclosed. In one embodiment, the hyper-converged computing device includes a server comprising at least one central processing unit (CPU), memory, and storage, a central virtualization switch integrated with the server, a virtualization application to manage virtual machines hosted by the hyper-converged computing device, and a hyper-converged application to manage the hyper-converged computing device. The hyper-converged application is to appropriately route data associated with an exclusive communication between the virtual machines and peripheral devices through the central virtualization switch that is integrated with the server.
Abstract:
Techniques for placing containers in a cloud (e.g., into virtual machines (“VMs”)) based on container policies. The container policies may specify compute-related qualities, storage-related quality, and/or network-related qualities that are to be met by the underlying software and hardware that supports execution of the virtual machines. A cloud director or other entity receives requests to place containers in a particular virtual machine based on the container policies and directs placement of the virtual machine based on the policies. The cloud director may migrate and/or reconfigure VMs, virtual machine disk files, and/or virtual network interface controllers to satisfy the container placement policy. After placement, the cloud director may disable migration to maintain the VM in a desired state.
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.