VMware Communities
pj1001
Contributor
Contributor

workstation 7 (linux) and mainMem.useNamedFile = "FALSE"

hi all,

i am looking into i/o performance problem under workstation 7. I have tried to follow the recommendation from article: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=100888...

When I add the mainMem.useNamedFile = "FALSE" to configuration of the vm, the .vmem file is created anyway.

Am I missing something?

--pawel

6 Replies
continuum
Immortal
Immortal

don't read outdated documentation - look here Smiley Wink

http://sanbarrow.com/vmx/vmx-advanced.html#mainmem

I guess you use a Linux 32bit-host - on a Windows-host this should still work.

To avoid users reading outdated guides for performance-tuning the vmx-parameter mainmem.useNamedFile no longer

works with Workstation 7 on Linux

New way to assign the path to the vmem-file on Linux in Workstation 7 is listed below.

Keep in mind - you always get a vmem-file - you just select the path to store it

mainmem.backing = "swap" --- works on Linux 64bit only - vmem file is stored in RAM/swap

mainmem.backing = "named" --- vmem file is stored with the VM

mainmem.backing = "unnamed" --- vmem file is stored in /tmp






___________________________________

VMX-parameters- VMware-liveCD - VM-Sickbay


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

ca2longoria
Contributor
Contributor

Hello.  Using VMware Player alone, I have a situation where this phrase...


"When I add the mainMem.useNamedFile = "FALSE" to configuration of the vm, the .vmem file is created anyway."

... applies, but I *am* using Windows 7.

Are there cases where Windows 7's VMware Player simply ignores the config.ini file?  Thank you.

0 Kudos
sunnyzh2012
Contributor
Contributor

Hi Continuum,

How about workstation 9 on Linux 64-bit host? What should we do to prevent *.vmem?

According to http://faq.sanbarrow.com/index.php?action=artikel&cat=14&id=50&artlang=en, the parameter "mainmem.backing" doesn't work in workstation 9.

Thanks very much!

Sunny

0 Kudos
continuum
Immortal
Immortal

where do you read that ?
when I wrote that WS 9 has not been released


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

0 Kudos
sunnyzh2012
Contributor
Contributor

Well, I found the article by Google search...

Do you know what should we do in workstation 9 on Linux 64-bit host to prevent *.vmem? Thanks.

0 Kudos
continuum
Immortal
Immortal

The new settings (introduced in WS 7) should apply for WS 8, 9 and 10.


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