Running VMWare workstation (Win7Pro64 Host, WinXpPro32 Guest), VMware constantly writes to the vmem file. This causes losts of disk seeks back and forth and slows down the entire machine.
My understanding is that vmem is a backup of the memory... is there any way to tell it to only make this backup periodically. Or some other way to speed it up?
If anyone needs more info on this, please let me know.
Can you check via Resource Monitor (or equiv. on Linux) if you're experienceing the same behavior?
add this line to the vmx-file - then this problem is history
mainmem.useNamedFile = "false"
Add the same line to the config.ini if you want this behaviour for all your VMs
___________________________________
VMX-parameters- Workstation FAQ -[ MOA-liveCD|http://sanbarrow.com/moa241.html] - VM-Sickbay
Ulli Hankeln wrote:
add this line to the vmx-file - then this problem is history
mainmem.useNamedFile = "false"
Add the same line to the config.ini if you want this behaviour for all your VMs
___________________________________VMX-parameters- Workstation FAQ -[ MOA-liveCD|http://sanbarrow.com/moa241.html] - VM-Sickbay
I have the same problem when the Windows 7 (64 bit) host wakes from sleep.
Is there a down side to disabling this?
Yes - you can run less VMs at the same time and need lonher for suspend and resume operations
see http://faq.sanbarrow.com/index.php?action=show&cat=78 for mor notes on this
Ulli Hankeln wrote:
Yes - you can run less VMs at the same time and need lonher for suspend and resume operations
see http://faq.sanbarrow.com/index.php?action=show&cat=78 for mor notes on this
Thanks Ulli.
Most of our hosts only have one VM on them so this info was very helpful. Odd I never noticed this problem on hosts running OSX Fusion or 2003 Workstation, only on Windows 7 (64 bit) after the host woke from sleep. Thanks again.
Steve
windows 7 / 2008 sucks as host platform for Workstation - 2003 just runs one league higher