Shulou(Shulou.com)06/03 Report--

Windows failover + Hyper-V virtual machine automatic migration is high

Available

Windows failover + Hyper-V virtual machine automatic migration is high. 1

First, the system principle. 3

1.1 efficient VMbus architecture. 3

1.2 perfect support for Linux system. 4

Second, the architecture topology. 5

2.1 Network and system architecture topology. 5

2.2 Domain structure topology. 5

Third, the list of experimental resources. 6

3.1 Network equipment. 6

3.2 Server equipment. 6

IV. Hyper-v failover cluster configuration process. 6

4.1 AD Domain. 7

4.1.1 installation process for the AD domain. 7

4.1.2 AD configuration process. 13

4.2ISCSI Storage. 18

4.2.1 ISCSI Storage. 18

4.2.2 configure ISCSI and create ISCSI 19

4.2.3 join a domain group. 27

4.3Hyper installation. 29

4.3.1 ISCSI initiator. 29

4.3.2 Hyper-V installation process. 31

4.3.3 failover cluster management. 34

4.3.4 New virtual machine. 40

Fifth, the verification result. 44

5.1 Live Migration. 44

5.2 failover. 45

Sixth, the experimental results. 47

6.1 considerations. 47

6.2 Summary. 47

I. system principle

Hyper-V adopts the architecture of microkernel, which takes into account both security and performance requirements. The underlying Hypervisor of Hyper-V runs at the highest level of privilege, which Microsoft calls ring-1 (while Intel calls it

Called root mode), while the OS kernel and driver of the virtual machine run on ring 0, and the application runs under ring 3, this architecture does not need to use complex BT (binary privileged instruction translation) technology, which can further improve security.

1.1 efficient VMbus architecture

Because the underlying Hypervisor code of Hyper-V is very small, it does not contain any third-party drivers.

It is very compact, so it is more secure. Hyper-V adopts VMbus-based high-speed memory bus architecture, hardware requests from virtual machines (graphics card, mouse, disk, network) can be directly through VSC, through the

The VMbus bus sends the VSP,VSP call to the root partition to the corresponding device driver and accesses the hardware directly without the help of Hypervisor.

This architecture is very efficient, unlike the previous Virtual Server, every hardware request requires

It has to go through multiple switches in user mode and kernel mode. What's more, Hyper-V can now support

The Virtual SMP,Windows Server 2008 virtual machine can support up to 4 virtual CPU;

Windows Server 2003 can support up to 2 virtual CPU. Each virtual machine can be used at most

64GB memory, and can also support the X64 operating system.

1.2 perfect support for Linux system

Unlike many friends, Hyper-V can support Linux very well, and we can install it.

With Xen's Linux kernel, Linux can know that it is running on Hyper-V, and it can also install Integrated Components specially designed for Linux, which contains VMbus drivers for disk and network http://baike.baidu.com/view/7756.htm adapters, so that Linux virtual machines can also achieve high performance. The following figure shows Novell

SUSE Linux 10 SP1, in which the network card driver, its bus type is VMbus.

This is a boon for enterprises that adopt Linux systems, so that we can unify all servers, including Windows and Linux, into the latest Windows Server 2008 platform, take full advantage of the latest advanced features brought by Windows Server 2008, and keep the original Linux key applications unaffected.

Similar to the previous Virtual PC and Virtual Server, Hyper-V is also a virtualization technology solution of Microsoft, but it has made great progress in all aspects.

Hyper-V can adopt paravirtualization (Para-virtualization) and full virtualization

(Fullvirtualization) there are two simulation ways to create a virtual machine. The paravirtualization approach requires the virtual machine to be the same as the physical host's operating system (usually the same version of Windows) to achieve high performance, while the full virtualization approach requires CPU to support full virtualization features (such as Inter-VT or AMD-V) so that virtual machines can be created using different operating systems, such as Linux and Mac OS.

Architecturally speaking, Hyper-V has only three layers of "hardware-Hyper-V- virtual machine", which is very small.

Coincidentally, the code is simple, and does not contain any third-party drivers, so it is safe and reliable, high execution efficiency, can make full use of hardware resources, and make the performance of the virtual machine system closer to the real system performance.

Architecture Topology 2.1 Network and system Architecture Topology

2.2 Domain structure topology

Third, the list of experimental resources

3.1 Network equipment

A Huawei 5752-SI

3.2 Server Devic

Two G6S

Two virtual machines of xenserver

IV. Hyper-v failover cluster configuration process

The following screenshots have the details of each step. I will skip the repetitive screenshots. If there is no picture, I can go straight to the next step.

Or by default.

4.1 AD domain

A brief introduction to the domain: members in a scope will agree by default that the time requirements of the domain controller, clustering and failover can also be met.

4.1.1 installation process for AD domain

Add roles and Features Wizard

Or feature-based installation (default next step and available)

Select local server

Since the AD domain requires components of the DNS service, we need to select the DNS service.

Select feature (default next)

Add roles and featur

Confirm installation of the service

DNS service installation completed

Installation of AD domain

AD domain installation is complete and this server is promoted to a domain controller

4.1.2 AD configuration process

Create a new domain and specify the root domain name (at this point the DNS service is already used)

Configure directory restore mode password

DNS option (ignore, next step is fine)

Configuration of domain name

Conditional check for domain configuration (as shown in the figure)

Enter the management interface of the AD domain and begin to configure the AD domain

Create a new organizational unit (OU)

Create a new organizational unit and name

Add domain group members

4.2ISCSI Storage 4.2.1 ISCSI Storage

Repeated skipped, choose to schedule ISCSI server

By default, the installation is complete.

4.2.2 configure ISCSI and create ISCSI

Create an ISCSI target

Select a partition to create a new ISCSI virtual disk

Name the virtual disk

Create an arbitration disk for Hyper-v

Create a new ISCSI target

Specify the target host name

Specify which host has access

Give permissions to the main ones that need to be connected.

Whether CHAP security certification is required

Confirm that the relevant information is correct, and start creating

Wait for the progress bar to finish reading and close the current menu

Create another disk

The disk is named Date (data disk)

Assign a size to a disk

Others are similar to the creation of arbitration disks, so omit them and simply follow the above settings (so both disks have been created)

4.2.3 join a domain group

Set the first DNS to the domain controller IP (because it is also a DNS service provider)

In the system, change the computer name and modify it. It needs to correspond to the root domain name you created earlier (DNS should also be set to the domain control server IP, otherwise you cannot join the domain)

Enter the user name and password of the domain service (the following Hyper-v1 and v2 need to be joined to the domain in the same way)

4.3Hyper installs 4.3.1 ISCSI initiator

Select the ISCSI initiator in the dashboard. If you need to pay attention, you must join the domain first, and the domain will be restarted.

The ISCSI server must join the domain and start running the service before it can be used by other clients (clients must also join the domain)

Select the Discovery tab and enter the ISCSI service to provide IP

Choose to connect to the target

Two disks will appear. Just choose automatic configuration.

Turn on the disk management in computer management, online and format the ISCSI disk (formatting only needs one machine to do it)

4.3.2 Hyper-V installation proc

The steps of the two sets are basically the same, so they will not be subdivided.

Choose to install the Hyper-V service

Select the failover cluster in the add role

Select the next step to continue

If you select a network card to act as the network card of the virtual switch, you need to have the same name of the two network cards, otherwise the migration will fail.

Allow switches to migrate in real time

By default, you still need to modify this item after the shared disk for subsequent failover is set up.

The installation is complete.

4.3.3 failover cluster management

Start setting up a failover cluster

Verify the failover cluster configuration, and if it is configured and normal, the cluster will be created automatically.

Default next step

All servers, you can see from the figure that both servers have joined the domain

Select to run all tests

Confirm the configuration that needs to be verified, and you can move on. (default to the next step)

The verification process takes about 5 minutes.

As shown in the figure, the configuration passed.

Start creating a cluster

The wizard for creating the cluster, and names and sets the cluster's Vip for the cluster, and automatically adds the member within the domain group.

Confirm creation

Creation of cluster completed

Create a cluster shared volume. After it is created, it will be automatically generated to the ClusterStorage\ Volume1\ directory of the C disk.

Store virtual hard disks and virtual machines in a shared storage directory

4.3.4 New virtual machine

Create a new virtual machine

Allocate memory for virtual machines

Assign the network, or the same, emphasize that the names of the network cards of the two hosts are the same.

Assign hard disk size to virtual machine

Mirror boot

After the virtual machine was created, I created a test machine named on each mother machine, and then I began to verify it.

5. Verification results 5.1 Real-time migration

As can be seen from the figure, the migration starts at 22:00 and uses live migration.

From the figure, as shown in the figure, the time can match. In the screenshot of Ping, you can see that no package has been dropped. In the moment of real-time migration, the delay will be a little large, and a packet may be dropped.

5.2 failover

It can be seen from the picture that the Hyper-v2 machine is running normally at 21:49 and has been running normally for more than 4 days.

I restarted Hyper-v2 's server at 21:52, mimicking the scenario when the failure occurred.

The Hyper-V2 is offline, and the virtual machine is migrated normally, and there will be nearly 20 packet swaps in the migration process. However, in the current environment, the one-minute business interruption is relatively good. In Hyper-V 's commercial products, there is the concept of data center virtualization, and the virtual cluster of one data center is dead, and the cluster of another data center is opened accordingly. If you look at it from this perspective, the one-minute outage of Hyper-V is excellent data.

VI. Experimental results

Judging from the above verification results, the Windows failover + Hyper-V virtual machine automatic migration in this experiment is successful.

6.1 considerations

Hyper-v already has this service in windows 2008 R2, but there is a substantial update in windows 2012, so it is recommended that windows 2012 or above be used in a new cluster project, so that the stability of the system, business availability and service maneuverability are greatly guaranteed.

All roles in a failover must be in the same scope. Default server roles under the domain

The time will be synchronized automatically. The default is once every 45 minutes, and the server after joining the domain cannot be synchronized.

Time on Inter.

6.2 Summary

This document is applicable to windows 2012 and windows 2012 R2 and does not apply to other versions of the operating system.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.