Hello etung,

Pause and suspend are not the same thing, at least not on parallels. Pause on parallels simply halts the guest while keeping all the ram in memory. It is very quick. Suspend actually writes the memory out to the file system and is much slower.

Why would you want to use pause over suspend? Well I used to use it when Vista was chewing away my CPU for no apparent reason. I would pause it, continue what I was doing in OSX and go back to it when I was ready... I don't know if that is a valid use case, maybe others could give a better reason.

Take care,

Hi Pat, I also see 4-6% idle time for my XP SP2 VM both in single window and unity mode.

But if I have Visual Studio 2005 open, then idle usage in unity goes up to 10-15%, but only in unity mode. In single window mode with Visual Studio 2005 open, idle usage stays at 4-6%. Is this something that could be looked at for an optimistation in a future release?

(Not all apps cause this, as explorer windows don't put the idle usage up at all when in unity mode).

Cheers

Russell

Suspend Guest is greyed out for me in any mode -- Do I have to do something to enable it?

So, I currently use Windows Hibernate function in a Boot Camp VM when I want it and it has worked great for me without having to enable Suspend/Resume.

NOTE: You will still have the same issue if you reboot the VM into native Boot Camp mode with out of date hardware/memory to cause data loss if you hibernate. You can only hibernate if you plan on staying in the VM. If you want to go to Boot Camp, resume the hibernated VM and then shut it down.

Pat