that are current HPE server running Hyper-V and Hyper-V HPE servers container compatible with Windows Server 2016. Windows Server, and Hyper-V containers onto Windows Server 2016 and are thus equally compatible and usable. HPE extends the compatibility of the various ProLiant server service packs. Therefore, it is quite possible, that can be installed on older ProLiant servers Windows Server 2016.

but must be set to compatible drivers here. The establishment of container technology docker from Windows Server 2016 on HPE servers is done either directly on the Hyper-V host itself or it still a virtual server is installed on the HPE-Hyper-V host on the Hyper-V is also used. . Also here is make sure that the drivers for the server are compatible with Windows Server 2016. Windows 2016 is mandatory for the use of Windows Server, and Hyper-V containers. This container technology do not support earlier versions of Windows.

2016 on HPE ProLiant server to install Windows Server 2016 and Hyper-V, should be checked in the first step, if the server is compatible with Windows Server 2016. Microsoft is the Windows Server catalog available.

in Windows Server 2016, embedded virtualization (nested) can be used, if the guest system also uses Windows Server 2016 in Hyper-V. Therefore, for example quickly smaller production environments can be build, and test and development environments. Microsoft Windows Server 2016 and HPE with current drivers for Windows Server 2016 to provide everything that is necessary. Once a Server Windows Server 2016 and Hyper-V support, also the embedded virtualization can be used.

to

Windows Server 2016 as the basis for Hyper-V and Hyper-V container

to Hyper-V and thus Hyper-V container in Windows Server 2016, a stable installation from Windows Server 2016 on the server is necessary. Also installing the latest drivers that are provided on the respective driver page of the HPE server is important. Here, it is also important to install the latest Service Pack by HPE for the ProLiant server. ZDNet.de own contribution of has explains how to install in a .

as soon as the server is set up, can be on different ways to install Hyper-V and set up. The installation of Hyper-V is a prerequisite for the use of Hyper-V containers. In General, parallel virtual server based on hyper-v can be operated on a server and Hyper-V containers on the basis of Windows Server 2016 including the container technology. Here, companies can apply to the conventional installation of Windows Server 2016, with a graphical interface, or on the core server and the new Nano installation. Once a server is compatible with Windows Server 2016, all variants of Windows Server 2016 on the server can be installed.

Server for the installation of Hyper-V prepare

once the server is installed and is set up, all updates of the server should be installed through Windows Update in the settings. “

 on HPE servers can install Hyper-V on the basis of Windows Server 2016 (screenshot: Thomas Joos). on HPE servers can install Hyper-V on the basis of Windows Server 2016 (screenshot: Thomas Joos).

prior to the installation of Hyper-V should be taken also, that all support for virtualization, and thus are enabled in the BIOS/UEFI settings Hyper-V. In most BIOS/UEFI settings of HPE servers are these settings through “ system OptionsVirtualization options” . All functions should be used to “Enabled”. “

 in the BIOS/UEFI settings support for virtualization must be enabled to use Hyper-V or vSphere 6.5 efficiently (screenshot: Thomas Joos). in the BIOS/UEFI settings support for virtualization must be enabled to use Hyper-V or vSphere 6.5 efficiently (screenshot: Thomas Joos).

Intel virtualization extensions: VT-x, VT-d, EPT

since 2006 offers Intel processors, the special virtualization features include. These were expanded in the meantime and are generally called Intel virtualization technology (VT-x). The appropriate options can be found in the BIOS/UEFI HPE servers, and should be activated. In addition to VT-x, the Xeon platform offers also VT-d (virtualization technology for directed I/o), which virtualization solutions receive direct access to peripheral devices such as network cards. Also the newer Xeon processors available CPU extension allows extended page tables (EPT), accelerated memory access also known as second-level address translation (SLAT), a virtualization solution. An overview of Xeon processors optimized for virtualization can be found on the Intel Web page .

Intel IT managers with the support “ Intel IT server sizing tool “. This will help the configuration of servers on the basis of appropriate, necessary performance of the VMs and containers. In addition, Microsoft offers the tool core info to test which features a processor supports. Hyper-V in Windows Server 2016 offers new maximum values. These should take account administrators when buying new servers. The new maximum values can be seen in the table.

maximum CPUs per host 512
max memory per host 24 TB
max memory per VM 16 TB
maximum number of virtual CPUs per VM 240

table 1: maximum level of Hyper-V hosts with Windows Server 2016

Hyper-V install

as soon as the server is prepared , Hyper-V can be installed. Either the Server Manager is used to install, or the PowerShell. Certainly, the use of Server Manager is the easiest way to install Hyper-V on a server with Windows Server 2016. manage/roles and features add selects the server on which to install Hyper-V. Then, the server role is selected Hyper-V . Here, ProLiant servers do not differ from other servers.

because current HPE Server Windows Server 2016 support, also the new Nano installation is supported. They can be operated on physical servers, but also as a virtual server on the basis of HPE-Hyper-V hosts with Windows Server 2016. Set up to do this by using either the Microsoft Nano Server Image Builder or with PowerShell. The Nano Server Image Builder also displays the necessary commands for the PowerShell at the end of the wizard. If the nano image on a physical HPE ProLiant server is to be used, all current Windows Server 2016-Server driver should be involved in the image. This is done through a wizard in the Microsoft Nano Server Image Builder. “

 Hyper-V can be operated on HPE servers on basis Nano installing Windows Server 2016 (screenshot: Thomas Joos). Hyper-V can be operated on HPE servers on basis Nano installing Windows Server 2016 (screenshot: Thomas Joos).

in addition to the Server Manager also the PowerShell can be used to install hyper-v. The cmdlet call get-WindowsFeature Hyper-V * will be shown whether the role and the management tools are already installed. Windows Server 2016 the command with the option computername can check the installation of Hyper-V also on remote servers in the network.

to install Hyper-V, the cmdlet is used install-WindowsFeature . With install-WindowsFeature Hyper-V the server role is installed with the option -IncludeManagementTools including the administration tools. Should the server just automatically restart, still uses the option restart . “

 HPE servers can use nano-installation from Windows Server 2016 (screenshot: Thomas Joos). HPE servers can use nano-installation from Windows Server 2016 (screenshot: Thomas Joos).

embedded virtualization use

to use Hyper-V based of virtual server container, 2 insists on a Hyper-V host with Windows Server016 embedded virtualization to enable the option. A Nano-server image exists, this can be as a virtual server on the Hyper-V Manager in Hyper-V are included. To do this, the image, or the virtual disk, which in turn was created with the Nano Server Image Builder serves as the basis.

before the embedded virtualization can be used on a virtual server to Hyper-V-based, some preparations must be made. First, the dynamic memory for the virtual machine must be disabled if it is turned on. In addition, the virtualization extensions to the vCPU must be enabled as well as MAC address spoofing. The virtualization extensions are enabled in the PowerShell host by typing the following command in PowerShell:

set VMProcessor – VMName “VMName” ExposeVirtualizationExtensions $true

that is spoofing of MAC addresses in the settings of the VM using the menu item “ advanced features ” below the virtual network adapter set. The function can be done also in the PowerShell:

get VMNetworkAdapter – VMName “VMName” | Set-VMNetworkAdapter – MacAddressSpoofing

on generally must be ensured, that no longer work when using this virtualization many functions in the VM or are restricted. Live migration is just as little possible, such as creating and using snapshots. Also saving the State of the VM is not possible, the VM must always be restarted for changes. Such a configuration is therefore most useful for test and development environments. [

embedded virtualization is enabled using a PowerShell script that can be downloaded and launched directly on the HPE-Hyper-V host:

invoke WebRequest https://raw.githubusercontent.com/Microsoft/Virtualization-Documentation/master/hyperv-tools/Nested/Enable-NestedVm.ps1 ~/Enable-NestedVm.ps1[19459006OutFile]

then the script is launched: is ~/Enable-NestedVm.ps1

– VmName

once the embedded virtualization enabled, Hyper-V can be installed in the virtual machine. This process can be started also in the PowerShell on the host. Also the new PowerShell Windows Server 2016 direct function can be used. This allows to run PowerShell commands on the host to the VMs:

invoke-command – VMName “w2k16′ – ScriptBlock {enable-WindowsOptionalFeature feature name Microsoft-Hyper-V – online; Restart-computer}

of course, also the PowerShell within the VM or Server Manager in the VM can be used. Then Hyper-V in the VM available stands. Managing Hyper-V is identical with the management of Hyper-V on a Hyper-V host.

 with the embedded virtualization Hyper-V can be installed within Hyper-V VMs. with the embedded virtualization Hyper-V can be installed within Hyper-V VMs. This is useful for test environments or container hosts (screenshot: Thomas Joos).

use container-host and Hyper-V-container to use Hyper-V containers on an HPE Server parallel to Hyper-V, must the server in addition to the container host be promoted. To the installation of the container features on the server is first needed. The installation can be either Server Manager or the PowerShell. In the PowerShell command used container install-WindowsFeature. When you create a new Nano server, the container function must be included with the image.

Windows Server container technology on the basis of docker is basis for the operation of Hyper-V containers. Some extensions must be installed to manage Windows Server container. To do this, the server must have an Internet connection, because the online feature of PowerShell, these functions can be the easiest install:

install-module-name of DockerMsftProvider-force

install package name docker provider name DockerMsftProvider-force

restart computer to force

make an image on the basis of Windows Server 2016 must be first downloaded the necessary data images in Microsoft/docker and integrated on the server :

docker pull microsoft/windowsservercore

docker pull microsoft / nanoserver

with the docker client the docker hub can be searched by images on the basis of Windows Server 2016:

docker search Microsoft

command install modules posh docker download the auto-completions for the docker client administrators and integrate it in PowerShell. After installation can be switched through the tab key commands and options of the docker clients, much like the command prompt. The module with posh docker import module is integrated in the PowerShell.

Hyper-V containers create and configure

first, there is no difference between Hyper-V containers and conventional Windows Server containers. When you create a Hyper-V container with docker uses the parameter- isolation = hyperv . Developers want to convert a conventional container with docker to a Hyper-V container a mark of insulation must be used. The command looks for example like this:

docker run – rm – it – insulation hyperv nanoserver = cmd

the benefits have to show an example. Is for example with the following command to create a container, and a permanent ping command started in this container, the process on the host is to recognize:

docker run d Microsoft/windowsservercore ping localhost t

the successfully created container is displayed with docker ps . Top with docker display the processes in the container you are.

in this sample is then the ping process and its ID to see. This information to display the command get-process name ping . This information is to recognize that the process has the same ID as in the container.

administrators create a Hyper-V container with the same command, for example with:

docker run d isolation hyperv = microsoft / nanoserver ping t localhost

here can now on the same path the ID of the process for the ping command be obtained. This again docker is top used . Again the process on the host searched for, this is not seen. On the host, the process of a new VM is visible in this case, however. These are the virtual machine that encapsulates the Hyper-V container and before the host operating system protects the executed processes.

conclusion

Hyper-V and Hyper-V-container can operate optimally on HPE servers. It is important that the latest drivers and the latest Service Pack are installed on the server and that BIOS/UEFI is adjusted so that virtualization is optimally supported.

Be the first to comment

Leave a Reply