Windows Server Technical Preview (Windows Server) Hyper-V experience

650) this.width=650; "height=" 268 "title=" clip_image001 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image001 "src=" http://img1.51cto.com/ Attachment/201410/8/2661587_1412755003p0n7.png "border=" 0 "/>

The first time you're ready to experience the next Hyper-V, in the official note, client Hyper-V on Windows 10 Technology Preview and Microsoft Hyper-V Server Technology Preview run the new and changed features of the Hyper-V role as follows:

1. Rolling upgrades for Hyper-V clusters

2. Storage quality of service (QoS)

3. Virtual machine configuration version

4. New virtual machine configuration file format

5. Production checkpoints

6. Hyper-V Manager improvements

7. Provide integrated services through Windows Update

8. Hot Add and remove network adapters and memory

9. Linux Secure Boot

10. Compatible Connection Standby status

Let's take a look at the desktop side of the hypertension, in WINDOWS10, open the programs and features interface, click Enable or disable Windows features, in the Windows feature interface, check Hyper-V, you can expand Hyper-V view or choose the option to install , Hyper-V contains 2 parts, one is the management tool for Hyper-V, including Hyper-V Manager and PowerShell, and the other is the Hyper-V platform, including the virtualization layer and virtualization services. There is no difference in installation with Hyper-V in Windows 8.1. However, with the server version, the client version of Hyper-V still provides only the underlying functionality.

650) this.width=650; "height=" 311 "title=" clip_image003 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image003 "src=" http://img1.51cto.com/ Attachment/201410/8/2661587_1412755008b0tc.jpg "border=" 0 "/>

The installation process, like Windows 8.1, requires a system reboot, and when restarted, we can see the management tools for Hyper-V in the Start menu.

650) this.width=650; "height=" 584 "title=" clip_image005 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image005 "src=" http://img1.51cto.com/ Attachment/201410/8/2661587_1412755012qyjl.jpg "border=" 0 "/>

Click into Hyper-V manager and we can create a new virtual machine, the version of Hyper-V Manager in Windows 10 is 6.4, and the Windows Version 8.1 of the manager for Hyper-V is version 6.3, and Microsoft has improved for the 6.4 version, including Hyper-V virtual machine connectivity.

1. You can now use a different set of credentials to connect to the remote host in Hyper-V manager. You can also choose to save these credentials to log in again later.

2. You can now use Hyper-V Manager to manage multiple versions of Hyper-V. Using Hyper-V Manager in Windows Server Technology Preview and Windows 10 Technology Preview, you can manage computers on Windows Server 2012, Windows 8, Windows Server R2, and Windo WS 8.1 Runs Hyper-V.

3. Hyper-V Manager can use the WS-Protocol to allow remote Hyper-V hosts for CredSSP, Kerberos, or NTLM authentication to communicate. Using CredSSP to connect to a remote Hyper-V host allows you to perform live migrations in Active Directory without the first advantageous constrained delegation. Moving to WS-based infrastructure also simplifies the configuration necessary because WS-People connect through port 80, which is turned on by default enabling hosts for remote administration.

650) this.width=650; "height=" 423 "title=" clip_image007 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image007 "src=" http://img1.51cto.com/ Attachment/201410/8/2661587_1412755014moi9.jpg "border=" 0 "/>

Next is to experience Windows Server 10, which is also installed in the same way as Windows Server R2, in Server Manager, click Add Roles and Features.

650) this.width=650; "height=" 420 "title=" clip_image009 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image009 "src=" http://img1.51cto.com/ Attachment/201410/8/2661587_1412755017djy5.jpg "border=" 0 "/>

In the Add Roles page, select the Hyper-V role, if your server's physical hardware does not support virtualization technology vt-d or VT-V technology, there will be an error here, if you are using VMware Workstation to install Windows Server 10 and enable virtualization , you need to edit the vmx file of the virtual machine using Notepad and add hypervisor.cpuid.v0 = "FALSE" and mce.enable = "TRUE". After you choose to look at Hyper-V, the Select Hyper-V Feature dialog box pops up to select the Hyper-V component.

650) this.width=650; "height=" 394 "title=" clip_image011 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image011 "src=" http://img1.51cto.com/ Attachment/201410/8/2661587_1412755023wplc.jpg "border=" 0 "/>

650) this.width=650; "height=" 426 "title=" clip_image012 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image012 "src=" http://img1.51cto.com/ Attachment/201410/8/2661587_1412755025q35c.png "border=" 0 "/>

Setting up a virtual switch is the same as installing Windows Server R2, which is not described here.

650) this.width=650; "height=" 398 "title=" clip_image014 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image014 "src=" http://img1.51cto.com/ Attachment/201410/8/2661587_1412755027qkgl.jpg "border=" 0 "/>

During the installation, some basic settings for Hyper-V are required, which is the same as Windows Server R2, where you set up the authentication method for VM Live migration, the location of virtual machines and virtual disks, and so on. The operating system needs to be restarted several times during the installation process.

650) this.width=650; "height=" 399 "title=" clip_image016 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image016 "src=" http://img1.51cto.com/ Attachment/201410/8/2661587_1412755030bwup.jpg "border=" 0 "/>

After the final Hyper-V is loaded, we can see the Hyper-V option in Server Manager, in Windows Server 10, the Hyper-V virtual machine connector in the start directory in the Hyper-V Management Tools folder, While Hyper-V manager is in the Administrator Tools folder in the Start directory, you can click Hyper-V Manager at this point.

650) this.width=650; "height=" 347 "title=" clip_image018 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image018 "src=" http://img1.51cto.com/ Attachment/201410/8/2661587_14127550332bxz.jpg "border=" 0 "/>

In Hyper-V Manager, we can see the same version of Hyper-V Manager as before in Windows 10, as I've already covered.

650) this.width=650; "height=" 339 "title=" clip_image020 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image020 "src=" http://img1.51cto.com/ Attachment/201410/8/2661587_1412755035ybxe.jpg "border=" 0 "/>

Of course, we installed the Hyper-V manager and the Hyper-V platform, we first create the virtual machine, in the Create Virtual Machine page, select the second generation of virtual machine, Microsoft slowly began to force in the second generation of virtual machines, the first generation of virtual machines I believe in the future will slowly be marginalized, at least to the Windows The curtain call for Server 2008 should not have a 32-bit operating system in the server version after Windows Server 2008. In Windows Server 10, a second-generation virtual machine can add or remove a network adapter while it is running on the VM without causing downtime. You can also adjust the amount of memory that is assigned to a virtual machine when it is running, even if you have not yet enabled dynamic memory.

Linux operating systems running on a 2nd generation virtual machine can now be started using the Secure boot option enabled. Secure boot is enabled on the host running Technology Preview version of Ubuntu, 14.04 and later versions and SUSE Linux Enterprise Server 12. Before you start the virtual machine for the first time, you must specify that the virtual machine should use a Microsoft UEFI certification authority. At the elevated Windows Powershell prompt, type:

Set-vmfirmware vmname-secureboottemplate microsoftueficertificateauthority

650) this.width=650; "height=" 421 "title=" clip_image022 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image022 "src=" http://img1.51cto.com/ Attachment/201410/8/2661587_1412755038ufcq.jpg "border=" 0 "/>

The whole process of the virtual machine is not explained in detail, follow the steps next to know to create a virtual machine to complete, I am here to install the Windows Server Technical preview directly in the virtual machine.

650) this.width=650; "height=" 413 "title=" clip_image024 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image024 "src=" http://img1.51cto.com/ Attachment/201410/8/2661587_1412755041t0ih.jpg "border=" 0 "/>

The effect after the installation is complete.

650) this.width=650; "height=" 315 "title=" clip_image026 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image026 "src=" http://img1.51cto.com/ Attachment/201410/8/2661587_1412755048uzwl.jpg "border=" 0 "/>

However, it is important to note that the current version of the virtual machine provided by Windows Server Technical Preview is 6, and the version of Windows Server R2 is 6, and I feel that at least the performance parameters have been improved, We can use the PowerShell command to view the version of the next virtual machine, enter the command GET-VM * | Format-table Name, Version

650) this.width=650; "height=" 151 "title=" clip_image028 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image028 "src=" http://img1.51cto.com/ Attachment/201410/8/2661587_1412755051rika.jpg "border=" 0 "/>

You can see that the virtual machine version shown is 6.0, and it is important to note that if you import the virtual machine from Windows Server R2 to the Windows 10 version of the Hyper-V server, the virtual machine's profile is not automatically upgraded. This allows the virtual machine to be migrated back to the Windows Server R2 version. If you do not upgrade to the 6 version of the virtual machine, some of the high-level features will not be available.

The virtual machine configuration version represents what version of Hyper-V virtual machine configuration, saved state, snapshot files are compatible with. The configuration version 5 of the virtual machine is compatible with Windows Server R2 and can be run in Windows Server R2 and in Windows Server 10 preview. Configuration version 6 of the virtual machine is compatible with Windows Server 10 and will not run on Hyper-V running on Windows Server R2. Currently, if you are upgrading a version of a virtual machine, you need to upgrade through PowerShell.

Run one of the following commands from an elevated Windows PowerShell command prompt:

Update-vmconfigurationversion Vmname or Update-vmconfigurationversion vmobject

650) this.width=650; "height=" 419 "title=" clip_image030 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" clip_image030 "src=" http://img1.51cto.com/attachment/201410/8/ 2661587_1412755054nr8y.jpg "border=" 0 "/>

Virtual machines now have a new profile format designed to improve the efficiency of reading and writing virtual machine configuration data. It is also designed to reduce the likelihood of data corruption in the event of a storage failure. The new configuration file is used. The VMCX extension is a virtual machine configuration data. The VMRS extension of the run-time state data. The VMCX file is in binary format and does not support direct editing of VMCX or Vmrs files.

This article is from the "Let" cloud "everywhere" blog, please be sure to keep this source http://mabofeng.blog.51cto.com/2661587/1561273

Windows Server Technical Preview (Windows Server) Hyper-V experience