Summary of common exception handling methods for Windows Server R2 Hyper-V virtualization _hyper-v

Recently to the customer to do a Hyper-V virtualization server, in line with the love of Microsoft, with confidence installed a set of Windows Server R2 Hyper-V, but Microsoft does not seem to love me!! Unusual lot!

Problem One: Virtual machine memory Footprint 100%

Virtual machine boot memory usage is normal, but if you open any one application, memory will be 100%, too scary! Ping will!

I tried to adjust the dynamic memory allocation but was not able to resolve this, and then the dynamic memory allocation function turned off to use the normal normal use! This is not the case in previous deployments, and is estimated to be related to server hardware (this server hardware uses Dell R720) for unknown reasons;

Problem two: "Unknown Device" appears in virtual machine Device Manager

I am a person with obsessive-compulsive disorder, do not want to see any flaws on the server, how to do?

Reason:

This problem is caused by the fact that this virtual device is used to provide AVMA automatic virtual machine activation and remote communication with the host, while AVMA only supports virtual machines running on Windows Server R2 or later operating systems, and we are using Windows Server 2008 R2 virtual machines, so the two virtual devices will not be able to activate normally;

Workaround:

According to Microsoft's official instructions is that the unknown device is harmless, you can ignore it, this for us to have obsessive-compulsive disorder how can, no, absolutely not, still have to solve;

In fact, the method is relatively simple:

1) Click "Install Integration Service"

2 and then find the corresponding windows6.2-hypervintegrationservices-x64 file, decompression it;

3 Right click "Unknown Device" select "Update Driver", select the corresponding decompression drive directory;

4 will prompt you to drive compatibility, security issues, select "Always install this driver software"

5 The same method activates another unknown device;

6 At this time we can see that two devices have been normal drive, to solve the problem;

Question three: In the virtual machine FTP upload download data when the speed is very slow

This download, upload speed is really let the heart cold Ah! How did this happen? In fact, if there are some network based friends can probably think of the reason, is obviously tcp\ip data checksum cause, later in the Microsoft Official E community found a document written to the relevant solution;

RELATED links:

https://social.technet.microsoft.com/Forums/windowsserver/en-US/29c669db-30fe-4196-9b95-a9d5e48ac318/ Slow-network-performance-after-adding-hyperv-role-to-windows-server-2008-r2?forum=winserverhyperv

Workaround:

1 The physical network card IPv4 hardware check and shutdown

2 "TCP Test and Uninstall (IPV4)" To disable the virtual network card at the bottom of Hyper-V;

3 and then test the FTP speed of the current lever, you can normally use, fix;

This article originates from the system Operation Dimension Systemdevops "blog