This happens when trying to suspend XP with all SPs and patches. The host is Win7x64 on I7 with 12 GB RAM and the VMs are on a dedicated velociraptor 300. There is plenty of available RAM and disk space.
What now?
Z
Oh, and I also have loaded the new VMWare Tools on the XP VM.
Hi TomZ,
Can you trigger the error, then grab the vmware.log from the VM's directory and attach it to a post here? If you don't want to post the logfile publicly for any reason, feel free to PM me instead.
Cheers,
--
Darius
Before I posted, I tried powering off the VM and restarting, I stopped and restarted Workstation, I rebooted my computer, etc etc. It kept reproducing.
Now, I go to collect a log and .... it is back to working perfectly. I tested it over and over.
Thanks for your intent to help, sorry for the false alarm. (Damn car never makes that funny noise when the mechanic is listening)
TomZ
Hi Shane. I haven't seen this error before. Can you try removing your Working Directory (or set it to the same directory as the .vmx file)?
Hi,
Changing the working directory back to the VM location did resolve the issue.
Thank you sorting this.
If this is a known limitation why is it possible to set the working directory to a custom location?
I changed the working directory to try an save space on the drive.
Once again thanks for your help.
> If this is a known limitation why is it possible to set the working directory to a custom location?
Hi Shane. This isn't a known issue. It should be possible to set the Working Directory. I'll file a bug report and include your logs.