JOIN OUR
COMMUNITY

TRY OUR SOFTWARE

Open Virtualization Blog


Windows containers & Hyper-V nested virtualization

Posted by UDS Enterprise Team |

This year, the term Hyper-V nested virtualization is everywhere, and not only because it is a new Hyper-V Server 2016 feature, but because od the implications on another technology whic is becomng more and more popular: containers.

The support for containers is one key benefit of Hyper-V nested virtualization, since it brings a new take on VMs, with less overhead and more flexibility to develop and deploy applications.

None

Containers are a new type of VMs less isolated than the traditional ones. Resources common to all containers running on a host are shared, which means greater efficiency. For example, if you're running three different containers on a host with the same Windows Server version, only one copy of the Windows directory is needed. Sharing resources reduces overhead and makes containers more lightweight.

Windows containers benefit administrators in some ways. Developers can come closer to the actual operation of the code, so they can build a custom version of the environments the code requires to run. Developers build container images which are then shipped over to administrators, who can handle updates quickly and easily. Each container image might work on a very small part of the overall application, which componentizes the application and makes it easier to work in a microservices-oriented environment.

In addition, developers can write code that works exactly within their environment and dministrators spend less time figuring out if code is not working and more time managing the overall infrastructure.

For further information on this technology and how to manage it, have a look at SearchWindowsServer


SHARE


0 COMMENTS

You must authenticate to review this post