4. What in VMM 2008 R2 SP1? Additional support for Windows Server 2008 R2 SP1 Dynamic Memory and RemoteFX Rollup of all previous VMM hotfixes Version:- VMM 2008 R2 - 2.0.4271.0 VMM 2008 R2 SP1 RC - 2.0.4516.0 VMM 2008 R2 SP1 - 2.0.4521.0 (new!)
5. VMM Configuration Analyzer Latest version 1544 support VMM SP1. Pre-requisite Microsoft Baseline Configuration Analyzer (MBCA) Download MBCA - http://www.microsoft.com/downloads/en/details.aspx?FamilyId=DB70824D-ABAE-4A92-9AA2-1F43C0FA49B3&displaylang=en VMMCA - http://www.microsoft.com/downloads/en/details.aspx?FamilyID=02d83950-c03d-454e-803b-96d1c1d5be24&displaylang=en
13. UpgradeSP1 RC to RTM Uninstall VMM 2008 R2 SP1 RC, select retain the DB! Run upgrade utility <installation cd root>386inpgradeVMMR2SP1RC.exe <installation cd root>md64inpgradeVMMR2SP1RC.exe Restart the server Install VMM SP1 RTM, use existing database
16. Windows Server 2008 R2 SP1 Dynamic Memory Dynamic Memory allows the allocation of a range of memory (min and max) to individual VMs, enabling the system to dynamically adjustthe VM’s memory usage based on demand. This provides more consistency in system performance enabling better manageability for administrators
17. Enable Dynamic Memory Make sure the Virtual Machine is not running. Startup : Min 512 MB Maximum: default 64 GB
18. Memory Buffer Ideal target memory value is constantly change. Default is set to 20%
19. Memory Weight Memory weight determine who will get the memory. By default, all VM are created equal in term of memory prioritization. Rules of thumb:- Higher Priority will get memory 1st Taken from Lower Priority VM
20. Reserve Parent Partition Hyper-V (0 GB) DM: 4 GB Configure Hyper V parent partition to avoid freezes when Dynamic Memory VM’s use all RAM. HKEY_LOCAL_MACHINEOFTWAREicrosoftindows NTurrentVersionVirtualization RED_DWORD value Name = MemoryReserve Setting = amount of MB to reserve for the parent partition, e.g. 2GB RAM Lastly, Reboot server. VM 4- 4 GB DM: 4 GB VM 3- 4 GB Physical Server (16 GB RAM) ClusterNode1
23. RemoteFX in Hyper-V R2 SP1 Microsoft RemoteFXleverages the power of virtualized graphics resources and advanced codecs to recreate the fidelity of hardware-assisted graphics acceleration, including support for 3D content and Windows Aero, on a remote user’s device. This allows for a local-like, remote experience.
67. What’s next ? Next week – 30 April 2011 Another webcast- Deep Dive into MS VDI with Citrix Xendesktop on Hyper V Join Community Evaluation Program - https://connect.microsoft.com/site1211
Notes de l'éditeur
diagnostic tool that you can use to evaluate important configuration settings for computers that either are serving or might serve VMM roles or other VMM functions
Assigned memory : Physical memory used by the VM. The minimum value can be 5% and max 2000%. Assigned memory ideally is memory demand+memory buffer Memory demand: Total committed memory in the VM [memory needed to run with reasonable performance] and if this memory is less than assigned memory, VM will use guest paging and you will see a memory warning status in Hyper-V GUI.Memory status: Gives an indication about the memory status of VM for e.g. OK, Low, Warning.
This “ideal target memory value” is constantly changing as the virtual machine is running. Open a new program, the virtual machine needs more memory. Close a program and it needs less. However, it would not be a good idea to actually try and keep the virtual machine exactly at the ideal target memory value for a couple of reasons:This is where the memory buffer comes into play. The memory buffer allows you to specify how much “extra” memory a virtual machine should be given when we are moving memory around between virtual machines. By default this value is set to 20% – but you can make easily make it lower or higher.
The first thing to know is that this setting does not have any real effect if there is enough memory available on the physical computer. With enough memory available in the physical computer – all virtual machines can get the amount of memory that they want. However, when there is not enough memory available in the physical computer, Hyper-V needs to decide who gets the memory and who does not. And this is where the memory priority comes in to play.Specifically there are three effects:Higher priority virtual machines get given more memory. When memory is being given to virtual machines it is given to high priority virtual machines first.Memory is taken from lower priority virtual machines first. Similarly to the first point – when more memory is needed, it is taken from low priority virtual machines before it is taken from high priority virtual machines.The amount of memory removed from already running virtual machines when trying to start a new virtual machine depends on the memory priority of the new virtual machine.There is some extra information to know about this third point.The first is that – yes – Hyper-V will take memory away from already running virtual machines in order to let a new virtual machine start. That is unless the new virtual machine has a very low memory priority. The second is that this “startup effect” of memory priority also applies to virtual machines that do not have dynamic memory enabled. This is to say that if you have a mixture of virtual machines with and without dynamic memory enabled – the memory priority setting on the virtual machines without dynamic memory enabled will affect how much memory is removed from the dynamic memory enabled virtual machines when you try to start the virtual machines without dynamic memory enabled.
Recommended LAN connection -10Mbps. Network consumption high.
Must connect using RDC 7.14 GPU per deviceGPU must R2 be identicalRemoteFX not available for Windows Web Server and Windows Server 2008 R2 for Itanium based system
Microsoft Tested environment:- 12 VM per GPU2 GPU = 24 VM
Deployment ManagementHA VMMSupported upgrade – VMM 2008 R2 SP1Run as accountFabric Management- Allow OOB Bare Metal Provisioning, Hyper V ClusterHybrid management ToolsSupported Hyper V, XenServer , Vmware (with integration)VmwareNo import of data center tree structureImport template metadata, no moving of VMDK into VMM, no delete of templateCitrixInstall integration pack with VMMNetwork Management-Define Logical network, assign ip, mac, VIPIntegrate with Storage and Load BalancerSupported Load Balancer – Citrix Netscaler + F5Storage – HP EVA, EMC, NetApp – SMI-S ProviderUpdate management-WSUS only.-Hyper V Host, VMM, Update Server, PXE ServerServices Management-services templates, profiles, Server-app v-Scale Out-Export/Import Services + Template
Deployment ManagementHA VMMSupported upgrade – VMM 2008 R2 SP1Run as accountFabric Management- Allow OOB Bare Metal Provisioning, Hyper V ClusterHybrid management ToolsSupported Hyper V, XenServer , Vmware (with integration)VmwareNo import of data center tree structureImport template metadata, no moving of VMDK into VMM, no delete of templateCitrixInstall integration pack with VMMNetwork Management-Define Logical network, assign ip, mac, VIPIntegrate with Storage and Load BalancerSupported Load Balancer – Citrix Netscaler + F5Storage – HP EVA, EMC, NetApp – SMI-S ProviderUpdate management-WSUS only.-Hyper V Host, VMM, Update Server, PXE ServerServices Management-services templates, profiles, Server-app v-Scale Out-Export/Import Services + Template
