I've noticed when I quit parallels, suspend seems to take forever. So much so that when choosing restart without quitting parallels first results in the restart being canceled due to parallels taking too long. I did a search here and came across the causes being: > Depends on memory allocated to VM, free disk space, and Applications running on Mac OS I have 512MB allocated to the VM, 20 GB free disk space & parallels is the ONLY running application on the Mac. I'm assuming the time should be reduced when the VM memory is lower, the HD space is higher and fewer mac applications are running, which should mean there shouldn't be such a pause... Under 3.0 it took nowhere near as long to suspend. And when I was running 3.0 I actually only had around 3 GB of disk space remaining (as I've since moved one of my VM's off my drive to free up space)... I notice that the suspend bar shoots though around 95% of the way in a couple seconds, then it sits forever with 5% remaining. Assuming the bar actually indicates real progress I dunno if this helps identify what part of the save process its freezing on...
Plus one more detail, number of applications running on Windows, eg pagefile size + memory size it is from the Windows side
3 windows apps total (MSN Messenger, Avast (Anti-Virus), AVG Free (Anti-Virus)... Most of the time all 3 are idle... Page file is system managed at 757MB. Would turning this down to 512 Max speed up suspend??? Also, if it matters, my system's total ram is 2GB...
Hello, bobbyt Try to remove (not disable, but remove) at least 1 of the antiviruses and see if the is any positive result.
