Hyper-V as a new bright spot for Windows Server 2008 is a growing concern because it satisfies the need for people to run a lot of services on a single physical server, much more than the functionality provided by a single server. The goal of transitioning from a single server to a multifunction server without needing more hardware is what every unit manager would like to see, and all the work can be done by building a Hyper-V server.
The particularity of the position determines the improvement of the performance.
In the past we used virtual software, such as VirtualBox, virtual PC, its structure and hyper-V is different, the difference in the former is from low to high for hardware->os-> virtualization software-> virtual machine, The data on the virtual machine needs to go through three layers to the hardware, because the difference between the standard and the interface of each layer causes the data to be converted back and forth, which makes it slow to start and run. and Hyper-V is placed on the physical hardware, only 300k, but very powerful, it is connected to the hardware and virtual machines, its location than the system core also rely on, from which it can be considered a virtual machine, including Windows Server 2008. The short and vmbus speed of integrated Hyper-V is much more advanced than the original virtualization product in emulation (analog layer), so it is very easy to run virtual machines in Windows Server 2008.
Second, CPU and the requirements of the kernel
Today's CPU products, whether AMD or Intle, indicate support for virtualization products, as long as it is labeled Amd-v or Intel VT. On the operating system, hyper-V requirements are 64-bit, and 32-bit is abandoned because running more than 10 virtual machines on a server that only has the highest support for 4G of memory, shows that it is a spent, not much meaning.
Short summary: Hardware requirements for running Hyper-V:
1, Server 2008 Enterprise or Datacenter version;
2, processor 64-bit support virtualization;
3, memory at least 4G or above;
4, multiple hard disk partitions;
5, the network card at least 2, one is for the virtual machine sharing, one for the real physical machine;
Third, the application of Hyper-V
1, create a new partition to store the virtual machine, after volume naming, System file definition, format the final form of a VHD device. As shown in Figure 1.
2, in the Server Manager to add the role of Hyper-V, in the Add Role Wizard, check the "Hyper-V" entry to determine the virtual machine with the network card for future communication use. As shown in Figure 2. After a short processing, Hyper-V was installed successfully.