Performance degradation after the migration from a physical server to an Hyper-V virtual machine

Performance degradation after the migration from a physical server to an Hyper-V virtual machine

Physical server was migrated to an Hyper-V virtual machine

The output of the command:
C:\Windows\System32\msinfo32.exe" /report sysinfo.txt 
executed from inside the Hyper-V virtual machine where the performance degradation is observed shows negative amounts of RAM :

Total Physical Memory: -1 bytes
Available Physical Memory: -1 bytes
Total Virtual Memory: 2147352576 bytes
Available Virtual Memory: 2072465408 bytes
Total Page File Space: -1 bytes
Available Page File Space: -1 bytes

(the same information is also present in the file Sysinfo.log generated by the command _proinventory in OpenEdge 11.2 and higher).

The '-1 bytes' entries means the host machine does not have enough memory for all his guest Hyper-V machines and that this Hyper-V guest machine was not allocated a dedicated fixed amount of RAM from the host machine. 

 

For production systems where consistent good performance is important it is highly recommended to allocate a dedicated fixed amount of RAM from the Windows host machine to the guest Hyper-V virtual machine. 

References to Other Documentation:
http://windowsitpro.com/virtualization/q-what-does-negative-memory-available-counter-mean-hyper-v-r2-sp1-management-console

Progress Article(s):
P153991, Performance considerations when running OpenEdge databases/applications on a virtualized environment.