VMware Communities
WhiteKnight
Hot Shot
Hot Shot

Can't launch two VMs with less RAM requirements than physically available RAM - why?

On my Windows 10x64 host, equipped with 32 GB RAM and virtual memory disabled, I have two VMs set up with 12 GB RAM alloted to each of them (first is Workstation 15 hardware, the second one is Workstation 16 hardware).

When I try to run both of them, I get the following error message when trying to start the second one:

WhiteKnight_0-1606916798030.png

 

There should be enough free RAM available:

WhiteKnight_1-1606916879244.png

 

What's causing this error?



[VMware]: Workstation 17 Pro; --
[host]: Windows 10x64 host; --
[guests]: Windows 10x64, Windows 8x64.
Reply
0 Kudos
13 Replies
bluefirestorm
Champion
Champion

I think the anonymous paging file is referring to the .vmem file that is created upon power on of the VM. Its default location is where the VM is located and its size is equal to the configurated RAM of the VM. So the 12GB VM power up will create a 12GB vmem file. So make sure that there is enough available free SSD/HDD space. There is a way to turn it off but that's a different discussion.

Reply
0 Kudos
WhiteKnight
Hot Shot
Hot Shot

I don't think that's the case in my situation. I have 244 GB of free space on the drive that's hosting my virtual machines:

 

D drive.png

 

Does my config.ini perhaps chime a bell:

.encoding = "UTF-8"
mainMem.useNamedFile = "FALSE"
devices.hotplug = "FALSE"
authd.client.port = "903"
authd.proxy.nfc = "vmware-hostd:ha-nfc"
installerDefaults.autoSoftwareUpdateEnabled = "yes"
installerDefaults.autoSoftwareUpdateEnabled.epoch = "18954"
installerDefaults.componentDownloadEnabled = "yes"
installerDefaults.dataCollectionEnabled = "yes"
installerDefaults.dataCollectionEnabled.epoch = "18954"
prefvmx.minVmMemPct = "100"
priority.grabbed = "high"



[VMware]: Workstation 17 Pro; --
[host]: Windows 10x64 host; --
[guests]: Windows 10x64, Windows 8x64.
Reply
0 Kudos
a_p_
Leadership
Leadership

I have about the same hardware specs, and running several VM is not an issue.
I've configured the memory setting as follows:

a_p__0-1606932830002.png

André

Reply
0 Kudos
continuum
Immortal
Immortal

Why are you surprised ?

You cant have

physicalRAM = 32gb
pagefile = 0
memfile = 0
total VM RAM = 24gb
prefvmx.minVmMemPct = "100"

it may work with

physicalRAM = 32gb
pagefile = 0
memfile = 0
total VM RAM = 16gb
prefvmx.minVmMemPct = "100"

With
mainMem.useNamedFile = "true"
you should be able to run 2 VMs a 12gb

With
prefvmx.minVmMemPct = "50"
mainMem.useNamedFile = "true"
you should be able to run 3 VMs a 12gb

With
pagefile = 32gb
prefvmx.minVmMemPct = "10"
mainMem.useNamedFile = "true"
you should be able to run 5 VMs a 12gb or even more

Read
http://faq.sanbarrow.com/index.php?action=artikel&cat=78&id=116&artlang=en
http://faq.sanbarrow.com/index.php?action=artikel&cat=78&id=76&artlang=en
http://faq.sanbarrow.com/index.php?action=artikel&cat=78&id=78&artlang=en

 

 


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
WhiteKnight
Hot Shot
Hot Shot

Nice to see you again, Ulli 😊

 

Actually, this is my memory setting:

Memory settings.png

 

In Workstation 15 this wasn't an issue yet.

 

I'd expect the following to be true: 2 * 12 GB = 24 GB. 28 GB is larger than 24 GB. So, both VMs should launch flawlessly. Where's my mistake?



[VMware]: Workstation 17 Pro; --
[host]: Windows 10x64 host; --
[guests]: Windows 10x64, Windows 8x64.
Reply
0 Kudos
continuum
Immortal
Immortal

Hi
you forgot to also add the video RAM - and keep in mind that with pagefile = 0 the host needs to be extra careful  when allocating RAM to applications.

Ulli

 


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
WhiteKnight
Hot Shot
Hot Shot

Ah, yes, Workstation 16 raised the default value from 1GB to 8GB. I lowered it to 1GB now, so both VMs use 1GB.

 

Still, it doesn't work. 2 * (12 + 1)GB ... are there still some hidden requirements?

 

BTW: The label for this option reads: "Maximum amount of guest memory that can be used for graphics memory:" So, I tend to believe the value entered here is taken from the guest memory amount, not added...?



[VMware]: Workstation 17 Pro; --
[host]: Windows 10x64 host; --
[guests]: Windows 10x64, Windows 8x64.
Reply
0 Kudos
continuum
Immortal
Immortal

> 28 GB is larger than 24 GB

That  slider in the UI was created when the host operating system was NT , Win2000 or XP - compared to those  light-weight systems Windows 10 is a big fat behemoth.
I bet that the calculation available RAM minus 10 % equals RAM-available for VMs is way to optimistic for Windows 10 hosts.


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
WhiteKnight
Hot Shot
Hot Shot

Maybe ... But have a look at my Task Manager screenshot above. After having started VM #1 I still have 14 GB of free memory.

That should be more than enough to launch VM #2, don't you think so?



[VMware]: Workstation 17 Pro; --
[host]: Windows 10x64 host; --
[guests]: Windows 10x64, Windows 8x64.
Reply
0 Kudos
xishengzhang
VMware Employee
VMware Employee

Hello, WhiteKnight

 

Thanks a lot for your posting.  Can I confirm with you whether you have your hyper-v or vbs enabled on your host?  Could you please check the value of working set for vmx process in task manager on your host after you have the 12G memory VM started up?  Thanks.

Reply
0 Kudos
WhiteKnight
Hot Shot
Hot Shot

Hi @xishengzhang 

thank you for taking the time.

On my host I don't have Hyper-V enabled. I've got it enabled in the guest, though.

Here's a screenshot of Task Manager, depicting all the VMware parts:

VMX.png

 

Does this information help you?



[VMware]: Workstation 17 Pro; --
[host]: Windows 10x64 host; --
[guests]: Windows 10x64, Windows 8x64.
sorspet
Contributor
Contributor

Workaround is to add following into C:\ProgramData\VMware\VMware Workstation\config.ini.

prefvmx.useRecommendedLockedMemSize = "FALSE"
prefvmx.minVmMemPct = "0" 

 

Restart!

Done!

Reply
0 Kudos
jen2
Enthusiast
Enthusiast

It is most likely because of this bug https://communities.vmware.com/t5/VMware-Workstation-Player/BUG-4GB-Graphic-memory-will-be-reserved-...

Every machine will use more 4GB to the ram for the 3D Graphic support!

If you run 2 machines that is 8 more GB.

Don't expect this bug to be fixed anytime soon, a temporary fix is to disable 3d support but you will get slower machine

Tags (1)
Reply
0 Kudos