Parallels 10 running slow on Yosemite

My apologies. I did send the issue over to apple per your link.

Since you guys know this is a problem can't you execute this command as part of the installation process though?
 
The boot argument also solved the issue for me.

I'd just like to add you should run "nvram -p" in the terminal first and look for any existing boot arguments you are using.
For example, I was already using "kext-dev-mode=1" (because I'm adding TRIM support for a non apple ssd and have a modified unsigned kext)
In my case I needed to run this command "sudo nvram boot-args="debug=0xd4e kext-dev-mode=1"
if your computer needs "mbasd=1" then you would add that to any additional boot arguments.

For example:
sudo nvram boot-args="debug=0xd4e mbasd=1 kext-dev-mode=1"
(typically you will not need/want kext-dev-mode=1)

In regards to this I hope to receive an email when this has been properly solved as I would like to remove the extra boot argument. It just feels like a hackintosh to me :p

The boot arg seem to work at first but now Parallels 10 (Mid 2009 macbook pro, Removed optical drive and added SSD which i have all of my process running off of + OSX 10.10.1) will only work if I turn my computer on and then restart the computer. If I just turn on and open parallels it will lag and freeze up. Im glad ive figured out how to get it working but it is a bit of a pain in the ass to have to restart every time I want to open Parallels.

Any thoughts? Anyone?
 
Thank you Fred. It worked like a charm. I was ready to dump Parallels and get my money back but thanks to your solution, the problem is now resolved.
Thanks for your reply Fred, I did receive an explanation from Parallels. I'll copy and post it here.
Hi Sir,
Im disturbing you regarding the performance issue.
As from the symptoms, the issue can lie in NVRAM preferences of your particular Mac.

Please do the following to solve:
open Terminal application on Mac (Applications/Terminal.app)
please type this command (you may copy-paste it to the terminal from this message):

sudo nvram boot-args="debug=0xd4e"

Hit Enter.
You will be prompted to enter Mac user password. Please type it and hit Enter.
Note: you won't see what you are typing, just type and hit Enter. If you don't have Mac user password, please create a temporary one.

Then you may restart your Mac and the issue should be solved.
If not - please reply me here and I'll create a ticket for you in Support.
 
This remedy appears to resolve the same issues for me. Interestingly, 3 or 4 calls to the Parallels help desk never revealed the fix. I bet I wasted 20 hours of time and a couple of hundred dollars in vain attempts to remedy the problem. While I'm thankful the fix is achieved, I must admit that (1) I am shocked that Parallels did not immediately remedy its installation program, and (2) the help desk did not recognize the issue.
 
Hi John,

As you may have noticed from my previous posts, I was upset like you are now about this Parallels 10 features.
I usually use Parallels to compile ROM's in Linux (as it is almost impossible to set-up a reliable build environment under OsX !) and so I really need the full power of my computer because that eats up A LOT of resources.
Well, some weeks ago I had to perform a complete reinstall of my system... Downloaded the latest Parallels version and got not problems whatsoever running and using the 16 hyperthreaded cores of my Mac Pro right out of the Box. So : no problems here anymore with Parallels.
Now I am really waiting for Parallels to FULLY support Arch Linux so I may be able to build with Arch, which is supposed to be more efficient for the task !

So here's one simple question : did you experience the problems with the latest version of Parallels ? I believe one has been released in the last few days...

Regards.

FRED
 
I think Apple fixed this issue in 10.10.2
I updated the Mac OS X then for giggles removed the boot argument.
So far it has been running without issues.
 
Hi John,

As you may have noticed from my previous posts, I was upset like you are now about this Parallels 10 features.
I usually use Parallels to compile ROM's in Linux (as it is almost impossible to set-up a reliable build environment under OsX !) and so I really need the full power of my computer because that eats up A LOT of resources.
Well, some weeks ago I had to perform a complete reinstall of my system... Downloaded the latest Parallels version and got not problems whatsoever running and using the 16 hyperthreaded cores of my Mac Pro right out of the Box. So : no problems here anymore with Parallels.
Now I am really waiting for Parallels to FULLY support Arch Linux so I may be able to build with Arch, which is supposed to be more efficient for the task !

So here's one simple question : did you experience the problems with the latest version of Parallels ? I believe one has been released in the last few days...

Regards.

Fred,
Thanks for both your help and concern.
I consider myself more or less an idiot when it comes to these technical issues. So my rule is "If it isn't broken, don't mess with it." Therefore I was afraid to install any new item UNTIL my computer again slowed to a crawl last week and crashed multiple times. The Windows Taskmaster showed my CPU at 100% usage almost continually. Desperate, I installed both the 10.10.2 update and the new parallels release yesterday. Both seem to be working fine, although the Windows Taskmaster reflects a 90% plus use of Physical Memory.
 
I think Apple fixed this issue in 10.10.2
I updated the Mac OS X then for giggles removed the boot argument.
So far it has been running without issues.
I think Apple fixed this issue in 10.10.2
I updated the Mac OS X then for giggles removed the boot argument.
So far it has been running without issues.
How do you remove the boot argument? My machine keeps crashing after about 1/2 hour on the windows side. I wonder if it's because I haven't remover the boot argument.
 
How do you remove the boot argument? My machine keeps crashing after about 1/2 hour on the windows side. I wonder if it's because I haven't remover the boot argument.
 
I have a MacBook Pro Early-2011. I experienced the same slow performance described here. The 0xd4e setting seems to have fixed it for me. I queried my existing NVRAM settings and did not already have any boot-args, so I did not need to preserve anything.

My question is: what is this debug setting actually doing? I have seen several questions on the web about this - Parallels is not the only software with the issue, some VMWare versions have it too. The answers I have seen all want to tell people what sudo does, what NVRAM is, and what a debug setting is. None seem to explain this specific hex value - what it is, or what the bits it represent are turning on and off. Parallels people, please let us know exactly what this does and why we need it, so we can be informed of its potential side effects and interactions with other software.

Thank you.
 
I just downloaded Mac Yosemite, I'm currently running the latest Parallels 10. Updated everything. Restarted from complete shutdown. Starting my virtual machine to run Windows 7 on which my business software is located is slower than molasses in winter. I do notice that if I move my mouse around in a circle on the screen everything loads quicker. HELP PLEASE

I agree. I've been running Windows 7 on Parallels 10 and it is painfully slow. I've tried all the tricks posted on this forum and nothing has improved. I've been using since Parallels 6 and this is the worse version yet... slow and unstable... it will be my last upgrade! I'm working desperately to get all my applications off the Windows environment and using only native Mac applications.
 
I have a MacBook Pro Early-2011. I experienced the same slow performance described here. The 0xd4e setting seems to have fixed it for me. I queried my existing NVRAM settings and did not already have any boot-args, so I did not need to preserve anything.

My question is: what is this debug setting actually doing? I have seen several questions on the web about this - Parallels is not the only software with the issue, some VMWare versions have it too. The answers I have seen all want to tell people what sudo does, what NVRAM is, and what a debug setting is. None seem to explain this specific hex value - what it is, or what the bits it represent are turning on and off. Parallels people, please let us know exactly what this does and why we need it, so we can be informed of its potential side effects and interactions with other software.

Thank you.
Hello RSWorden,
Please check your Private message.
 
I agree. I've been running Windows 7 on Parallels 10 and it is painfully slow. I've tried all the tricks posted on this forum and nothing has improved. I've been using since Parallels 6 and this is the worse version yet... slow and unstable... it will be my last upgrade! I'm working desperately to get all my applications off the Windows environment and using only native Mac applications.
Hi Ronald,
Please check your Private message.
 
I have a MacBook Pro Early-2011. I experienced the same slow performance described here. The 0xd4e setting seems to have fixed it for me. I queried my existing NVRAM settings and did not already have any boot-args, so I did not need to preserve anything.

My question is: what is this debug setting actually doing? I have seen several questions on the web about this - Parallels is not the only software with the issue, some VMWare versions have it too. The answers I have seen all want to tell people what sudo does, what NVRAM is, and what a debug setting is. None seem to explain this specific hex value - what it is, or what the bits it represent are turning on and off. Parallels people, please let us know exactly what this does and why we need it, so we can be informed of its potential side effects and interactions with other software.

Thank you.
Hi Ronald,
Please check your Private message.

Why is this being addressed in a private message? I think everyone deserves to know what they're running at the command line. People that come to this thread via Google are going to want to know the same.
 
Back
Top