Hi
This issue is something i've just put up with for ages but after updating to the latest build today and it still happening decided it was time to post about it here.
I have Parallels 7 running on OSX 10.6.8 (MacBookPro Late 2009 Model - Core 2 Duo 2.8ghz, 8gb RAM, NVidia GT 9600/9400M) and I have been using with it Windows 7 (Bootcamp), OSX Lion VM and Chrome OS VM.
Thing is regardless of whether the VM boots and is suspended via the Parallels UI, the VM fails to boot (i.e. only a BIOS boot screen is shown but the DOS-like terminal indicates there is no working OS installation to boot), or boots and I select Force Shutdown (via Parallels dialogue boxes that pop-up when selecting to shutdown) the processes from the VMs hang around and every time I open a new VM it creates a new process too, even when it's the same VM.
In addition to this even when the application itself has been quit (Parallels), the processes just sit there as zombie processes chewing memory and CPU. For the last few years my only 'solution' has been to kill the process via Activity Monitor, but this is a really poor way to have to address the issue.
PS. I have attempted things like disabling the Windows Application folder within OSX, i've re-launched the process for the launch demon from the command line and more, but nothing has resolved the issue.
If Parallels is unaware of this issue can they please contact me so we can investigate and see this issue resolved ASAP. If anyone else has any tips that may help it would also be welcome.
A screenshot from Activity Monitor today (*after* having quit Parallels too!) - http://screencast.com/t/PAj3mEl5XrE
Thanks!
This issue is something i've just put up with for ages but after updating to the latest build today and it still happening decided it was time to post about it here.
I have Parallels 7 running on OSX 10.6.8 (MacBookPro Late 2009 Model - Core 2 Duo 2.8ghz, 8gb RAM, NVidia GT 9600/9400M) and I have been using with it Windows 7 (Bootcamp), OSX Lion VM and Chrome OS VM.
Thing is regardless of whether the VM boots and is suspended via the Parallels UI, the VM fails to boot (i.e. only a BIOS boot screen is shown but the DOS-like terminal indicates there is no working OS installation to boot), or boots and I select Force Shutdown (via Parallels dialogue boxes that pop-up when selecting to shutdown) the processes from the VMs hang around and every time I open a new VM it creates a new process too, even when it's the same VM.
In addition to this even when the application itself has been quit (Parallels), the processes just sit there as zombie processes chewing memory and CPU. For the last few years my only 'solution' has been to kill the process via Activity Monitor, but this is a really poor way to have to address the issue.
PS. I have attempted things like disabling the Windows Application folder within OSX, i've re-launched the process for the launch demon from the command line and more, but nothing has resolved the issue.
If Parallels is unaware of this issue can they please contact me so we can investigate and see this issue resolved ASAP. If anyone else has any tips that may help it would also be welcome.
A screenshot from Activity Monitor today (*after* having quit Parallels too!) - http://screencast.com/t/PAj3mEl5XrE
Thanks!