To be honest only having 200M free space will most likly cause you other problems..

Are these all locally stored VMs or are they SAN attached..

yes you can, you need to use the sched.swap.dir parameter for the vm. See page 141 in the Resource Management PDF.

I did a test on one of our VMs.. just added these to .vmx

sched.swap.dir

/vmfs/volumes/43e8b777-ecf41a8a-958e-000d60eb81e4/testDIR/

sched.swap.derivedName

/vmfs/volumes/43e8b777-ecf41a8a-958e-000d60eb81e4/testDIR/test-408f9806.vswp

Worked a treat, although might be easier to configure through VC..

1. Select VM --> Edit Settings --> Options Tab --> Advanced

2. Click Configuration Parameters Button.

3. Add new Row --> Enter Name Field = sched.swap.dir

4. In Value Field Enter full path..

Make sure "sched.swap.derivedName" also reflects changes..

This will add the lines to the .vmx..

I was only really referring to loosing HA etc if your location was of the SAN..

Remember its christmas, we do this for the points (some times just for the love of it..!!)

Hi Kit,

From the start i had the 'sched.swap.derivedName' in my .vmx file (actually all my .vmx files) and its path points to the same dir as my all the VM files..

So i added the 'sched.swap.dir parameter', and pointed it to a different directory on my VMFS partition..

But as long as the 'sched.swap.derivedName' pointed to the original path, my VC always reported 'error unable to start VM cache not found'..

I edited the 'sched.swap.derivedName' to have the same path as 'sched.swap.dir' and everything worked ok..

I played with the posistion of these, i.e putting one above the other etc, as long as 'sched.swap.derivedName' did not reflect the same path as 'sched.swap.dir parameter' i always got the error..

If i removed 'sched.swap.dir parameter' everything was ok and regardless of how i changed 'sched.swap.derivedName' it would always default back to its original settings..(as long as 'sched.swap.dir' didnt exist)

hope this is clear..

Ah, never tried that one..