Solved

Swapping VMs --> more memory assigned then recommended

Posted on 2008-10-16
2
739 Views
Last Modified: 2008-10-30
In ESX cluster with 3 host I have some WIndows 2003 Server Standard x64 machines with 16GB RAM.
 In VM Settings "Windows 2003 Server x64 Standard" is selected. The recommended max RAM size by VMware is 4GB according to the menu when creating the machine. I assigned 16GB to my machines, because the OS I installed supports up to 32GB. Now the VM are performing very slow, time to boot ist up to 10 minutes. The VMs are creating heavy CPU Load on the Host when booting.

I changed the OS selection to "Windows 2003 Server x64 Enterprise". Now everything is fine.

What causes this behavior? Can it possibly be that ESX is only assigning the recommended RAM as physical RAM to the VM and the rest is swapped to the disk?
0
Comment
Question by:TRITEC-kuen
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 2

Author Comment

by:TRITEC-kuen
ID: 22765792
Nobody knows something on this?
0
 
LVL 4

Accepted Solution

by:
bmonroe44 earned 500 total points
ID: 22826348
Even though you selected a x64 base operating system that is capable of handling 32gb of memory there are specific limitations on the template guest selected. Anytime you are using more than 4gb of memory on any system (x86 or x64) be sure to always select the enterprise template as it is the most compatible with the larger amounts of memory. This is the same issue with XenServer and why they adjust RAM shadowing which increases performance on guest vm's that operate as terminal servers. Consequently, operating system types are strictly enforced in both environment.
0

Featured Post

On Demand Webinar: Networking for the Cloud Era

Did you know SD-WANs can improve network connectivity? Check out this webinar to learn how an SD-WAN simplified, one-click tool can help you migrate and manage data in the cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
Giving access to ESXi shell console is always an issue for IT departments to other Teams, or Projects. We need to find a way so that teams can use ESXTOP for their POCs, or tests without giving them the access to ESXi host shell console with a root …
Teach the user how to install ESXi 5.5 and configure the management network System Requirements: ESXi Installation:  Management Network Configuration: Management Network Testing:
Teach the user how to install and configure the vCenter Orchestrator virtual appliance Open vSphere Web Client: Deploy vCenter Orchestrator virtual appliance OVA file: Verify vCenter Orchestrator virtual appliance boots successfully: Connect to the …

707 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question