Hyper-V Virtualization Management

I. What is hyper-V?

?    Hyper-V is Microsoft's virtualization product, the first Microsoft to adopt a hypervisor-based technology like VMware and Citrix Open source Xen.    Hyper-V is a system hypervisor virtualization technology proposed by Microsoft to enable desktop virtualization. Support for Hyper-V functionality starts from Windows Server 2008/2012.   two. System Requirements?   1.Intel or AMD64 bit processor [1].? 2.Windows server R2 and above (server operating system), Windows 7 and above (desktop operating system). 3. Hardware-assisted virtualization.   This is in the existing processor, including a virtualized Microsoft Virtualization architecture selector Specifically, Intel VT or Amd-v (AMD-V, formerly codenamed "Pacifica").?   4.CPU must have the hardware Data Execution Prevention (DEP) feature, and the feature must be started.   5. The minimum memory is 2GB. 6. In Microsoft's Hyper-V virtual machine creation process, the maximum virtual hard disk can reach 2040GB three. Hyper-V Architecture1. Basic Hyper-V Virtualization Technology Architecture 2. Detailed architecture Personal understanding: virtual machines running on Hyper-V servers: sub-partitions, virtual machines, guest
Physical server running Hyper-V: Parent partition, management operating system, host?       Hyper-V is isolated through a way called partitioning, where the partition refers to a set of isolation units that are allocated physical memory space with virtual processor resources, which run the operating system.       In addition to the standalone version of Hyper-V servers, general Microsoft Hyper-V requires a parent partition that runs Hyper-V-enabled server operating systems or desktop operating systems. The virtualization stack in the parent partition can access the physical device directly, through the parent partition, you can create the child partition and run the operating system (guest Operating system,guest OS), the partition itself cannot access the physical processor, They only have virtual processors running at the same time in the virtual memory address space, each sub-partition of the virtual memory space is independent of each other.       The hypervisor layer performs a processor interrupt. The sub-partition cannot access any other physical resources, they access the hardware through the virtual device, and the request for the virtual device is transferred to the parent partition through the VMBus or hypervisor layer, which is processed by the parent partition. The Virtual server program (VSP) running on the parent partition handles device requests from the child partition through VMBus. The Virtual service client (VSC) running in the child partition passes the request to VSP with VMBus. The process of these operations is transparent to the guest OS.   Iv. Technical features of Hyper-V? 1. The new 64-bit hypervisor architecture supports a large number of hardware devices for better security and efficiency. 2.32-bit or 64-bit operating systems that support various server platforms. 3. Symmetric multiprocessor support, which can support 4 processors in a virtual machine (note, not quad-core).   4. Network Load Balancing.   5. New hardware sharing architecture with virtual service Provider/virtual service client (VSP/VSC) for high performance. 6. Fast migration.? 7. Virtual Machine snapshot. 8. Extensibility, support for standard WMI interface and API, convenient for developers. 9. Extendable features.    V. Two types of Hyper-V? 1) as a component of Windows Server 2008/2012 exists; If you do not have Hyper-V, you can add Hyper-V components in Management in Server Manager.
2) separate server Edition? Separate server Edition, Windows Hyper-V server, only two windows for the standalone service version, which can be executed on the cmd command line when executing a command. Execute the command systeminfo to see the system condition. When exiting to the command line, execution Sconfig.cmd can be returned to the selection interface. Five. Adding Hyper-V    1. Sign up        ?     Microsoft Hyper-V Server can enroll to Microsoft Windows Server 2008/2012 R2 (with Hyper-V component) Manager for remote administration.     ? The protocol used by remote management is: Remote Desktop is the RDP protocol, the WinRM protocol used by PowerShell (CVS already supports this protocol, and the protocol is selected for scanning when scanning)?      winrm  is the function of the windows  remote management component. With the Web protocol, the default port 5985  2.hyper-v server  add      ? Add step:        to manage Hyper-V server  in Windows server in Hyper-V? A), on the Windows 2012 Management Server, Power Shell run the following command            ? Set-item wsman:\localhost\client\trustedhosts win-hyper-v-server2012 or ipaddress  -concatenate– force       ? B), add the server in Server Manager on the Windows 2012 Management Server, select DNS join, if the lookup fails, you can ignore,?        C), Right-click on the added server, select Windows pwower shell , link on server after executing shutdown firewall netsh firewall set op di  or add Firewall rule (3389)   3. Problems with the Add process

Issue 1: Cannot find the Hyper-V server host

Workaround: Close the firewall on the Hyper-V server or join the related rule, and close the command as follows: netsh firewall set op di

Question 2: Does the add server appear "WinRM negotiation authentication"?

Workaround:

Enable WinRM on 1.HYPER-V server and execute (seemingly no need, execute 2.2 to connect, manage)

WinRM set Winrm/config/client @{trustedhosts= "win-hyper2012,win-ob2g2qok640, 192.168.12.17,192.168.12.16"}

2. Execute on Windows Server:

On the Windows 2012 Management Server, Power Shell runs the following command

Set-item wsman:\localhost\client\trustedhosts win-hyper2012 or Ipaddress-concatenate–force

Can solve the above problem.

Note: Make sure that the Trustedhosts list in the WinRM client has IP to connect to the remote machine.

Reference URL:http://www.cnblogs.com/dreamer-fish/archive/2013/03/15/2961497.html

3: Management mode, prompt to enter the account password format?

WORKAROUND: Correct format: local client computer name \ server Administrator name

namely: win-hyper2012 \administrator

Question 4. If the account name is not entered correctly in the management mode, some related errors are reported when the power shell is opened.

Workaround: Enter the correct name.

WinRM set winrm/config/client @{trustedhosts= "win-hyper2012"}

Six. Hyper-V Security Configuration

1. Operating system Security Configuration

1) Basic security hardening of the operating system?    2) Use a Server Core installation of the management operating system?    3) Use a minimum of 2 network adapter interfaces 4)? Disable installing other unnecessary applications on Hyper-V systems?    5) Use BitLocker Drive Encryption to protect Resources 2. Virtual machine Security Configuration 1)? Virtual machine memory allocation? 2) virtual machines using processor restrictions? 3) store virtual hard disks and snapshot files, configuration files in a secure location?    4) Access to virtual hard disks and snapshot files, profiles?    5) Allow assigning default credential configuration 6)? Enable Windows Firewall to block unnecessary firewall rules? 7) Auditing operations and management events for virtualized environments

Hyper-V Virtualization Management