Slow OSX shutdown if Parallels wasn't started

Shutdown behavior

Hy Sandro,

I did some tests and here are my results:
- shutdown of OSX with Parallels NOT (and never before) started: fast
- shutdown of OSX with Parallels NOT started, but before started: slow
- shutdown of OSX with Parallels started AND no vm started: fast
- shutdown of OSX with Parallels started AND VM running (WindXP): fast + VM kill time
- shutdown of OSX with Parallels started AND VM in resumed state (WindXP): slow !!!

I hope this helps in investigating this behavior ...
Best regards
Tom

 

Is the last one with VM in suspended state or running (resumed)? If VM is in suspended state, then it's normal that shutdown is slow - MacOS flushes all the VM data to disk before the shutdown.

Is the 2nd one:
- shutdown of OSX with Parallels NOT started, but before started: slow
is done after VM suspend as well? Or Parallels was not started at all after the host MacOS boot?

 

Hello sandro,
i can specify the issue as follows:

After applying this fix (http://forum.parallels.com/showpost.php?p=380883&postcount=36) my OS X shutdown behaves as follows:
Haven't started Parallels at all: fast
Started Parallels, but only the GUI part without starting a VM: fast
Using Parallels with WinXP, shutdown VM: slow
Using Parallels with WinXP, send VM to Standby: slow
Using Parallels with WinXP, stopped VM: slow

@Thomas Greschitz

How did you managed to kill prl_disp_service manually? I tried via Activity Monitor. prl_disp_service disappear from list, but shutdown is still slow.

 

I made another discovery: Disconnecting the Network Adapter of the VM before shut down the VM leading to a fast(!) OS X shutdown.
Hope this helps to find the bug.

 

Sebastian, Tom.

Thank you very much for provided information. Please also answer on support requests: we need problem reports to deep into the problem.

PS
Tom, i saw your support ticket and want to notify that it'll be passed to the next support level in nearest time. So please be patient and provide us all necessary technical info for problem investigation.

 

@Sandro

Sorry for my late reply, had a flue :-( ... but have just replied to support team.

@Sebastian

There's no difference in killing it via Activity monitor or through sudo kill, in both cases shutdown is very fast.

Best regards from Vienna
Tom

 

I have the same Problem, so i went back to bulid 3810 and it works fine.

But if theres a solution. Iam also intrested

Best regards & Thx

Thilo

 

same issue here

Hello I´m getting the same error …
But with the newest version of Parallels Desktop 5 on my new Mid 2010 Macbook Pro using the latest System of Snow Leopard.
I did also have this problem on my old Macbook with a different User Account …
Can I also try what you postsed on Page 2 (replacing the files etc.?)
Thanks!

 

now working fine

Hello!
I´ve had the same issue with parallels 5. Now it works fine (after replacing the file).
I didn´t do it via the terminal. you can replace it manually after killing the process.
Thank you!

 

nope i was wrong …
it didn´t work …
only deinstall works … that sucks!

 

Jonas.

Please try solution from http://forum.parallels.com/showpost.php?p=369808&postcount=18 but use:

1. latest PD 5.0 build 5.0.9344
2. attached file instead of one from mentioned comment

 

Sandro's solution works but steps need to be modified since you will get an error DispatcherService: Not a directory cd "/Library/Parallels/Parallels Service.app/Contents/Resources/ParallelsDispatcherService"

use these steps instead:
1) extract the ParallelsDispatcherService (executable) from the zip folder attached
2) in Terminal navigate to cd "/Library/Parallels/Parallels Service.app/Contents/Resources/"
3) create backup, sudo mv ./ParallelsDispatcherService ./ParallelsDispatcherService.bak
4) use finder to copy the downloaded ParallelsDispatcherService into cd "/Library/Parallels/Parallels Service.app/Contents/Resources"
5) change owner and group for the file using, sudo chwon root:admin ./ParallelsDispatcherService
6) finalize Parallels dispatcher service with command, sudo kill -TERM `ps aux -c | grep prl_disp | awk '{ print $2 }'`
7) Restart and revert to pre-parallels bootup and shutdown times

Hope this was useful

 

Yeah, it really works great!
I didn´t use the terminal at all …
i just navigated to the dispatcher opened the content of the prog and replaced the file manually then restarted and it worked fine!

 

Thanks Sandro! This worked for me as well.
I also didn't use the terminal except to run the final "sudo kill -TERM..." command before rebooting.

 

so what was the problem?

hi!

i wonder, if i have to replace the file again, when a new update is released …
and why is this problem just showing up on some devices?

thanks!

Jones

 

I guess I spoke too soon with this. The issue is still occurring for me. It seems like the issue is alleviated when I manually kill the processes related to Parallels ("prl_disp_service" and "prl_naptd"). This sometimes causes my suspended VM to have a BSOD the next time I try to use it though (only in cases when I've used Parallels). I've filled out a ticket (#944066).

My system specs are:
MacBook 5,1 (late 2008 aluminum)
2.4 Ghz Core2Duo
4GB RAM
OS X v10.6.4

PD 5.0.9344
XP Home Virtual Machine (1 CPU, 1 GB RAM)

 

Same problem here.

Hello.
I have the same problem with the latest version of PD 5 at the moment of writing (5.0.9370 - Revision 589435).
I'm running Leopard 10.5.8 on
Nome modello: Mac Pro
Identificatore modello: MacPro1,1
Nome processore: Dual-Core Intel Xeon
Velocità processore: 2.66 GHz
Numero di processori: 2
Numero totale di nuclei: 4
Cache L2 (per processore): 4 MB
Memoria: 2 GB
Velocità bus: 1.33 GHz
Versione Boot ROM: MP11.005C.B08
Version SMC (sistema): 1.7f10

If I manually stop prl_disp_service process, I get instant shutdown.
Sometimes it happens also if I run and close a VM inside PD, closing PD before shutting down my Mac.
I tried to replicate the exact chain of events, without success, because it's completely random.

Never had this kind of troubles with my dear old PD 3.0.
Please, try to sort out this annoying problem.

Regards.

 

Hi!
The issue is back again with the latest build of snow leopard and parallels desktop 5.
It did not work with the latest file you posted.
Do you have another file/option for us?

Thanks!

Best,
Jonas