Use Hyper-V to build a virtual OS environment
summary
Learn how to use Hyper-V, which is provided with Windows Server, to create a virtual OS environment that is independent of the physical PC.
Operating Environment
Operation check environment
| Windows Server Version | Windows Server 2008 R2 DataCenter |
| Hyper-V Version | Hyper-V 2.0 |
| CPU | Core 2 Duo P8400 2.26GHz 1066MHz 3MB 64bit support VT support TXT support DEP support |
| memory | 4GB (2GB DDR2-800 × 2) |
| HDD | 500GB Serial-ATA 5400rpm 8MB |
| NIC | One (Gigabit LAN) |
| Chipset | Mobile Intel GM45 Express Chipset |
System requirements required
| Windows Server Version |
|
| Hyper-V Version | Hyper-V 1.0 or later |
| CPU |
|
| memory | 2GB or more |
| other | OS to act as a guest server (see the official Hyper-V website separately for supported operating systems) |
substance
In this case, we will use Hyper-V 2.0 to build a guest OS environment in a Windows Server 2008 R2 environment. Hyper-V 2.0 is built by default in Windows Server 2008 R2 and does not need to be downloaded separately. Servers that provide Hyper-V are commonly referred to as "hosts" and virtual OS environments that ride on Hyper-V are referred to as "guests."
By the way, the number of server licenses required for virtual instances differs depending on the version of Windows Server, so please check separately.
Installing Hyper-V
Windows Server does not have most features installed. Hyper-V is similar, so install Hyper-V first.
To complete the installation, click Server Manager on the taskbar. You can also start it from Server Manager in the Administrative Tools in the Start menu.
When Server Manager opens, select Roles from the tree on the left.
From the roles displayed on the right, select Add Role in the red circle on the right.
The Add Role Wizard appears. Click Next.
When the list of roles to be installed is displayed, check "Hyper-V" and click "Next".
Click Next.
To connect a guest OS to a network, you must assign one physical network as a virtual network. Check the physical network you want to assign from Network Adapters and click Next.
Click Install.
The installation will start, so wait for a while.
When the installation is complete, click the Close button.
When you close the wizard, you will be prompted to restart, so select "Yes" to restart. The reboot is done twice.
A wizard appears when the restart is complete. Click the "Close" button to close it.
Building a Virtual OS Environment
Open Server Manager and see the Hyper-V role added under Roles from the tree on the left. The host server is listed under Hyper-V Manager, right-click, and select New → Virtual Machine to create a virtual machine.
By the way, you can also configure Hyper-V from "Hyper-V Manager" which can be launched from the management tools in the Start menu. The content is almost identical.
The New Virtual Machine Wizard appears, so click Next.
Set Name to arbitrary. If you want to save the virtual machine to any folder, check "Store the virtual machine in another location" and specify the location to be saved. When you are finished, click "Next".
Allocate as much memory as you need to use in the virtual OS. Since the memory specified here is consumed from the memory of the host server as it is, set it with a value that is not wasted. You can also change the amount of memory used later (if the guest OS is shut down).
Specifies the virtualized network. If you do not specify a network here, you will not be able to connect the guest OS to the network. You can also change the network you use later (if the guest OS is shut down).
When creating for the first time, there is no virtual hard disk, so check "Create virtual hard disk". The file name is the name you specified when you created the virtual machine, but you can change it. The file extension of the virtual hard disk is ". VHD". You can also specify a location of your choice.
The "size" specified here is the disk size that can be used by the OS you created. By the way, since the virtual hard disk file created here is created as a variable size, the virtual hard disk file size is not reserved for the specified disk size. The virtual hard disk file size automatically increases to match the disk size used (consumed) in the guest OS.
Since you won't start the OS installation immediately, check "Install the operating system later". If you want to be ready for installation immediately, please set other items according to your application.
Once confirmed, click the "Finish" button.
When you create a virtual machine, the virtual machine you created appears in a central list. Before starting it, right-click on the virtual machine and select "Configure".
The virtual machine settings dialog appears. There are various setting items, so please try it by yourself. Here we have changed the number of processors that can be used in the guest OS to two.
When you're done, right-click the virtual machine and select Connect from the menu.
The Virtual Machine Operations Viewer window appears. When you click Start on the toolbar, the virtual machine starts as if you had actually turned on your PC. However, if you have not yet turned on the OS, it will be in the BOOT waiting state even if you turn it on. If the OS is already in place, the OS will be started as usual, and it is possible to operate with a keyboard or mouse from the viewer.
If you want to install the OS from a DVD or similar, you can temporarily assign the host server's drive to a virtual machine by selecting Media→ DVD Drive, → Capture (Drive Letter) from the menu.
After the DVD capture, you can click the Start button to start the OS installation. (If you capture a DVD after it's already turned on, you can restart it with the Ctrl+Alt+Delete button on the toolbar.)
After the virtual machine is up and running, it behaves in the same way as a normal OS, so you can access the OS in the virtual machine without having to from Hyper-V by setting up networking, sharing, remote, etc.
Since it is not necessary to prepare a physical PC for each OS, I think that machine and OS virtualization is a very useful function considering the cost and location control.