VMware vSphere

 View Only
  • 1.  Installed Physical Memory vs Total Physical Memory

    Posted Nov 13, 2012 10:15 AM

    Good morning all;

    I have been running a Windows Server 2008 (VM) for about a year with no real issues. We have some software (written by a 3rd party) which uses a SQL database.

    The software has started hanging randomly during the day for all users, other applications are not effected just this software. I handed the issue back to the people that wrote the program and they uncovered something in their search for a resolution.

    When you open msinfo32 on the server the following is reported.

    Installed Physical Memory (RAM)    10.0 GB
    Total Physical Memory                    2.00 GB
    Available Physical Memory              708 MB
    Total Virtual Memory                       20.2 GB
    Available Virtual Memory                 8.82 GB
    Page File Space                             10.3 GB
    Page File                                       C:\pagefile.sys

    Should the Installed Physical Memory be the same as Total Physical Memory?

    When you go to System it shows 10 Gb as expected and task manager also shows Physical Memory as 10238.

    I read somewhere about the MAXMEM being set in Msconfig. I had a look here, all the boxes where unchecked. When you check the Maxmem, 10238 is displayed. When you "ok" out, then go back in it shows 2048 (strange) so i have left this unchecked.

    This host is ESXi 5.0 on a ML350 G5

    30GB of RAM

    2.5 Quad

    Hopefully someone can help me understand this, maybe I was suppose to do something when the VM was first installed?

    Thanks in advance



  • 2.  RE: Installed Physical Memory vs Total Physical Memory
    Best Answer

    Posted Nov 13, 2012 10:20 AM

    You can apply this hotfix to address this issue;

    http://support.microsoft.com/kb/950233



  • 3.  RE: Installed Physical Memory vs Total Physical Memory

    Posted Nov 13, 2012 10:58 AM

    Hi jrmunday

    Thanks for your quick reply that sorted it out for me..

    Just for anyone else that is having the same issue,

    I also needed to run the hotfix on a Server 2008 R2 machine.. For this i needed a different hotfix

    http://support.microsoft.com/kb/2492536

    Thanks again jrmunday