Hi, Has anyone found this behaviour? When you are using an application that has a pop-up window come up as a dialog for confirmation, does your VM hang? Mine does. Seems to happen usually after I have suspended a VM and try to restore it. Any assistance is greatly appreciated. Sajid
Yep, I'm getting the same thing. Running Windows XP in the VM. If I suspend it and sleep my laptop, then later resume Parallels, XP will lock up hard the next time I get a message pop up from Microsoft Messenger. I have to restart the VM to recover. I thought it was network related, but from your post is sounds like its actually pop-up windows causing it.
Shutdown your VM, remove the sound card definition from your VM configuration and reboot it. Your XP is now unable to emit a single beep, but it won't lock up after suspend/resume of the VM. This is a well-known issue of Beta 6. At least this is true for Windows XP guests.
With sound driver completely removed, I still experience lockups of Windows XP. So... this is not the solution for all lockups. The lockups occur after Mac OS X has kicked in the screen saver and then went to sleep. When I wake up OS X, the Windows XP VM clock shows the time the system suspended and it does not update. Mouse clicks are ineffective. When I try to power off the VM, Parallels hangs and I am required to do a Force Quit. Note: If I suspend my Mac and then wake up after a very short interval, the VM does not hang. I have not determined the critical time interval, but it appears to be something greater than 5 minutes.
I am not seeing those other lock-ups after longer sleep period (it just sleeped for 45 minutes and woke up just fine). When you say sound driver removed, do you mean you removed 'sound' from the VM configuration or did you uninstalled sound drivers from within the guest ? Running XP SP2 here. There's no smoke without fire, but I wonder what triggers those issues on your configuration that I luckily seem not being affected by. For sure I won't touch my setting even by a iota before a next beta. ;-)
Energy Saver Random guess: Window's Energy Saver is trying to sleep the machine and that kills it? I'm guessing that's too simple a solution, but it's worth a check to your Windows control panel to see...
Random answer: no way, cause the PW emulate a non-ACPI BIOS. XP has no opportunity to even think it could save poor lonesome recycled electrons by sleeping.
