Hot answers tagged memory
I think you may have a VMware memory ballooning issue. There's a chance that memory overcommitment across the vSphere infrastructure is too high. You won't be able to remediate this without access to the vSphere vCenter, but you should be able to detect this from within your virtual machines, assuming vmtools are installed: Can you please post the output of ...
Please look at your server's ILO4 interface. It will detail each RAM module, its slot number, HP Part Number, capacity, frequency, load (rank) and heath status.
Of course. Why wouldn't it? I think the more relevant question is whether or not using a 32 bit OS makes sense these days, but I digress. First, yYou're under the mistaken impression that 32 bit operating systems can only address 4 GB of memory, which isn't actually the case. 32 bit systems can address more than 4 GB of memory through the use of Physical ...
Yes, Hyper-V will pick the node (processor and memory) which has the most capacity when starting a VM. If the VM fits within the node, then it will run optimally. To avoid fragmentation, you might want to configure your machine to start the big VMs first. Keep in mind, though, the penalty for remote access of memory on your machine is probably quite ...
From page 86 of the T110 II Manual: "Your system supports DDR3 ECC unbuffered memory modules (UDIMMs)." The Samsung module you mentioned appears to be unbuffered ECC, while the Corsair modules are not. The solution is to install unbuffered ECC memory, as indicated in the manual.
It indicates that the referenced memory DIMM is [probably] bad. IBM suggests verifying the seating and connection for the DIMM, checking for a firmware update, and if those things don't work, replacing the DIMM.
If you want to "know 100% that it will work", you should not only look at the modules already installed but also at which module configurations are listed as supported in your Proliant's QuickSpecs (I assume this is a DL380p G8), the User Guide or the HP Memory Configurator. An excerpt from the relevant QuickSpecs' section: General Memory Population ...
Assuming you're running VMware ESXi/vSphere, you can run console commands to get more detailed information on the hardware components. Specifically, you should be able to get the part number, and look that up online. http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003587 Note from point 2 in ...
dmidecode -t 17 Linux dmidecode|less for esxi 4.x smbiosDump for esxi 5.x also see this for vmware http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003587
Only top voted, non community-wiki answers of a minimum length are eligible