Instead, just set the boot-args value to whatever you originally had. That will delete the entire boot-args setting. When Apple fixes this issue and you want to remove this option, you will not want to use the sudo nvram -d boot-args command as Darius mentioned later. Now reboot your Mac and enjoy your improved VM experience. If the command was successful (no errors were reported), run the nvram -p command to confirm both arguments have been added. $ sudo nvram boot-args='debug=0x10 kext-dev-mode=1' They are simply joined with spaces and wrapped in double quotes. If it returned an existing value (shown here in red), then you will need to modify the new command to include the existing values.

If the nvram -p command didn't return anything, you are fine to run the sudo nvram boot-args=debug=0x10 command.

The command Darius posted above would remove any existing options and replace it with only the debug=0x10 option. Setting the boot-args debug option immediately resolved it on both laptops.Īlso to note, before running the above nvram command, you should check if there are any existing boot-args values (this is rare but possible). I've been fighting with this problem on two MacBook Pro laptops, 1 early and 1 late 2011 models. I'd like to mention that this issue and fix is not only for the 2011 iMacs. They also recommended trying a disk permissions check following this which I have yet to do. So that is where I am at the moment - any suggestions anyone as Apple don't know what it is but their recommendation did help a bit so thought I would share it with you. Next boot - boot into os fine - open fusion 7 pro - fine - start guest - slow and jittery as before - once guest is up several minutes later - ran IE in the guest which was very slow but NO FREEZE. Power on and hold down CMD+ALT+P+R - after the first chime - let go. So I then raised a call with Apple (as I have a care plan) they don't know what the problem is and have not heard of it but after raising a case (Case Number 6866-99809) the engineer suggested doing something to completely reset the boot-args. Then tried putting down guest, shutdown vmware fusion - reboot - open vmware fusion (and not guest) - then sleep the host - then wake from sleep - then run the guest (which was fast) - then try the network connection in the guest which froze again. Then tried the sudo command recommended here which made the boot process slow again as expected and still had guest freezing on any network connection Update to my case if it helps anyone - Since applying the sudo command as I last responded my windows 7 guest booted fine and very quickly - however if I ran anything in the guest that involved a network connection such as internet explorer the entire guest would then complete freeze - only option then would be to shutdown the guest.

Suitcase fusion 7 slow