Abstract: A computer-implemented system for migration of a host Virtual Execution Environment (VEE), including a first VM running in a public cloud; the first VM having a first thin guest OS and a first file system; a dedicated hosting VEE on the first VM and executing user applications; a first dispatcher module running inside the dedicated hosting VEE, the first dispatcher module accessible to a user of the dedicated hosting VEE; a second dispatcher module running inside the first VM, the second dispatcher module in communication with the first dispatcher. The second dispatcher module is configured to live-migrate the dedicated hosting VEE with the executing user applications from the first VM to a second VM running on another public cloud, such that the migration is transparent to the dedicated hosting VEE.

Abstract: A hybrid storage capable of storing the image files and the service files for VMs and Containers is provided. A large files storage is placed onto a service volume. A VM image file is placed onto the large file storage and a file system is mounted on it. The small files storage is also placed onto the service volume. This way a portion of the large file storage can be seen to the management system for VMs and Containers as a part of an interface of the common file system. Thus, large files and small files reside on the same distributed storage. One file from the large file storage is dedicated as a service file. The file system is placed into this file, which is mounted into the system as a virtual disk. The small (service) files are stored on the virtual disk. This way all files are accessible by the management system for VMs and Containers.

Abstract: A method, system and computer product for managing host reclaimable memory based on Virtual Machine (VM) needs includes a plurality of VMs running on the host and executing user processes; a hypervisor configured to process VM memory requests; a host CPU configured to control host physical memory reclaim process; at least one VM requiring host physical memory; a VM configuration utility Guest tools configured to determine page types based on a memory map; and a host module configured to scan a Least Recently Used (LRU) list for pages. The host CPU performs a legacy reclaim operation, when the page is not a VM page; executes a hard lock protection, when the page is a VM kernel page; executes a direct access (DAX) LRU operation, when the page is a VM DAX page; and executes access/dirty (A/D) bit marking, when the page is a regular VM page.

Abstract: System for launching application containers inside VMs without data duplication, includes first and second VMs on a host; a storage to which the host has access; a container generation module running on the host and configured to interface to VM-side container generation daemons in the VMs; the container generation daemons transmits to the container generation module a request to pull container layers; a host-side container generation daemon processes the request to pull the container layers from the container generation daemons running inside the VMs; and a DAX device residing on each of the VMs. The host container generation daemon sends the request for any missing container layers to a registry, and writes them onto the storage, maps the layers to the VMs as the DAX devices, maps all needed container layers to the first VM and maps any identical container layers to the second VM, without accessing the registry.

Abstract: Method for sharing driver pages, including, on a computer system having a first driver and performing system services, instantiating Containers; code and data of the driver are loaded sequentially into pages arranged in a virtual memory, and instantiating a next driver upon a request from one of the Containers for system services by: loading physical pages of the next driver into physical memory and allocated virtual memory pages for the next driver; associating the next driver with the first driver and comparing pages of the next driver and the first driver, generating a set of identical physical pages; mapping virtual pages of the next driver to identical physical pages of the first driver while atomically protecting identical physical pages; non-identical pages of the next driver from physical memory remain mapped to virtual pages of the next driver; releasing physical memory occupied by identical physical pages of the next driver.

Abstract: Method for partitioning environments includes instantiating a parent VEE under a host OS; opening a file system of the parent VEE for modification; inside the FS of the parent VEE, creating an image file of an Application Container; mounting a virtual disk that corresponds to the image file; mounting the Application Container file system inside the image file; defining boundaries of the Application Container; placing Application Container files inside the Application Container file system; and creating an interface between the parent VEE and the Application Container for exchanging data. The processes of the Application Container connect to processes of the parent VEE as if they were native host OS processes. The Application Container can only request data from the host OS through the interface of the parent VEE. The image file is protected from modification by the parent VEE. The processes of the Application Container are launched inside the boundaries.