I downloaded beta 3 of Parallels and hit an oddity just now. I was working on a boot camp virtual machine and put the laptop to sleep. I later woke the laptop using external display/keyboard/mouse and the system was near unresponsive with WindowServer using 100% cpu. After about 10-15 minutes it finally caught up to my request to shut down Windows XP in Parallels. As soon as Parallels had closed the system went back to normal and was usable again. Anyone else had a similar issue?
I have noticed close to the same thing occurring on my MacBook Pro. I would close the laptop lid while Parallels is still running with my Windows XP BootCamp loaded, then sometime later I would open the lid and expect the username/password dialog to come up (I have my OSX set as such). Sometimes it comes up immediately, sometimes it takes a minute or so. When the username/password dialog does come up, I type in my password and it then shows the desktop for about 2 seconds, then blacks out showing nothing but the mouse cursor. After letting it sit there for a good 3-4 minutes, I decided to close the lid and then reopen after a few seconds. Once doing that I was prompted for my username/password again, put in my password, and the desktop showed up just fine now. Another thing I noticed is that the MacBook Pro really bogs down simply by having Parallels beta running (did it in beta 1, 2, and now 3). It seems to take longer to load anything in OSX than normal. I do have the 2GB RAM being split between the two OSes (1GB per) so I know that's part of it. I also know this is a beta and possibly is compiled as debug which might use a lot of RAM as well. I'm only mentioning this in the hopes that things get a bit more optimized for lower RAM systems (i.e. those of us without high-RAM Mac Pros).
