Forum Home
Press F1
Thread ID: 114189	2010-11-22 00:33:00	ESXi - Help with Memory Configuration	WarNox (8772)	Press F1

Post ID	Timestamp	Content	User
1155197	2010-11-22 22:02:00	ESXi Console > Configuration tab > System Resource Allocation > Advanced View > Host > VIM > Edit settings > Memory Resources What is the reserved memory amount?	inphinity (7274)
1155198	2010-11-22 22:39:00	I believe its 512mb, see attached. Thanks again.	WarNox (8772)
1155199	2010-11-22 23:22:00	Error from the Event Log on the ESX server included below. Also included is a screenshot of the configuration I got to work. 1gb on one VM and 2.25gb on the other but anymore than that and I get the same error. I set the limit the same as the reservation or a swap file is created on the datastore and there isn't enough space left on the datastore for this. Therefore I want to assign each VM a certain amount of physical ram. What I got now works fine but I want to know why its not letting me assign more than 3.2gb since there is 5gb in the server. VM o?S swap file has nothing to do with Memory limit and reservation. Reservation is amount that VM much have and will not share, limit is total amount of RAM for VM and is usually larger than configured memory in the VM... You set swap file from within the VM O/S	SolMiester (139)
1155200	2010-11-23 00:58:00	If I set the Memory of the VM on the hardware tab to 1.5GB and leave the Memory Limit as 'Unlimited' it creates a *.vswp file on the datastore. If I set the memory reservation and the limit to the same value as the Memory for the VM the vswp is still created but its 0 bytes, see attached, which works fine. Although I cannot assign all the physical memory. --- Are you wanting me to try the following? eg: VM1: 1024mb, Reserved: 1024, Limit: 1536 VM2: 2048mb, Reserved: 2048, Limit: 2560	WarNox (8772)
1155201	2010-11-23 01:09:00	If I set the Memory of the VM on the hardware tab to 1 . 5GB and leave the Memory Limit as 'Unlimited' it creates a * . vswp file on the datastore . If I set the memory reservation and the limit to the same value as the Memory for the VM the vswp is still created but its 0 bytes, see attached, which works fine . Although I cannot assign all the physical memory . --- Are you wanting me to try the following? eg: VM1: 1024mb, Reserved: 1024, Limit: 1536 VM2: 2048mb, Reserved: 2048, Limit: 2560 Yeah, something along those lines . . . . if I bring my limit down to the reserve i get same error!	SolMiester (139)
1155202	2010-11-23 01:24:00	Yeah, something along those lines....if I bring my limit down to the reserve i get same error! Alright, I'll give it a go tonight and let you know how it goes. That is weird though, can't see a reason for it.	WarNox (8772)
1155203	2010-11-23 09:24:00	Couple of things you may also want to try. 1) increase the physical RAM. 2) assign less cores to your VM's, you can't assign all 4 CPU's to them as ESX needs this as well you may need to run 1 core for ESX and then split the other 3 between your VM's cheers,	chiefnz (545)
1155204	2010-11-23 10:44:00	Couple of things you may also want to try. 1) increase the physical RAM. 2) assign less cores to your VM's, you can't assign all 4 CPU's to them as ESX needs this as well you may need to run 1 core for ESX and then split the other 3 between your VM's cheers, 1. There is 5gb of physical ram in the server which is enough. 2. Already done that, from 4 down to 2. --- SolMiester: That last suggestion seemed to have worked, sort of :) Thanks for all your help. Just have one more question :D New config: VM1: 1536mb, Reserved: 1024, Limit: 1536 VM2: 3072mb, Reserved: 2048, Limit: 3072 I actually did the opposite of the what was suggested above, it logically makes more sense to me. I set the LIMIT to be the same as the VM Memory and set the reservation to be slightly lower than that, as you can see above. What exactly does this mean for VM 1. .. 1. Maximum memory that VM1 can ever use is 1536mb? 2. Its guaranteed to always have 1024mb available? 3. I don't really understand what the limit shows? Would there be any point to set the Limit above the VM Memory? Thanks again!	WarNox (8772)
1155205	2010-11-23 19:00:00	New config: VM1: 1536mb, Reserved: 1024, Limit: 1536 VM2: 3072mb, Reserved: 2048, Limit: 3072 What exactly does this mean for VM 1. .. 1. Maximum memory that VM1 can ever use is 1536mb? 2. Its guaranteed to always have 1024mb available? 3. I don't really understand what the limit shows? Would there be any point to set the Limit above the VM Memory? Thanks again! VM1 has 1GB of Physical RAM permanently reserved exclusively for its use, and is allowed to use other non-reserved Physical RAM to a maximum total of 1. 5GB. VM2 has 2GB of Physical RAM permanently reserved exclusively for its use, and is allowed to use other non-reserved Physical RAM to a maximum total of 3GB. Guest OS can still use a paging file within it's VHD to provide total virtual memory to the guest OS of greater than the VM Memory Limit - e.g. VM1 can have it's 1. 5GB of RAM, as well as creating a pagefile as the OS normally would. Reserved is the amount of RAM dedicated solely for the use of that VM, Limit is the total maximum RAM that VM is allowed access to. There are ratios and rules around how much of the machines actual physical RAM can be reserved, but the Limit can be much higher as the hypervisor can use its own swapfile to simulate additional physical RAM as far as the Guest OS is concerned, as well as sharing non-reserved RAM among multiple VMs depending on load.	inphinity (7274)
1155206	2010-11-23 19:04:00	Ok, that makes sense but what is the difference between the VM Memory setting (VM1 1536) and the Limit (VM1 1536)?	WarNox (8772)
1 2 3