sticker
Contributor
Contributor

El Capitan Dev Beta and Boot Camp VM

I upgraded to 10.11 and was not able to run my boot camp vm. The fix is to disable SIP a.k.a System Integrity Protection a.k.a Rootless a.k.a Worthless. I tried cmd + R on boot and disabling through Security Configuration as stated at WWDC but recieved Mach error -536870212. A quick search on the apple dev site produced a working fix.

Open Terminal.

sudo su

[enter password]

nvram boot-args="rootless=0"

reboot

I had to reset my shared folders but other than that all seems ok... other than the USB driver error.

this was done on a late 2013 rMBP fusion 7.1.1

Tags (1)
7 Replies
System755
Contributor
Contributor

Thank you. Confirmed the above fix for MBPr Mid 2014 running VMware Fusion 7.1.2 and Boot Camp.

0 Kudos
ccalabro
Contributor
Contributor

did not work for me, fresh boot camp install of windows 10 and fusion 712 on OS X 10.11 beta

0 Kudos
sticker
Contributor
Contributor

what error(s) are you getting? What is the output from running "nvram boot-args"? I've been running since DP1 w/Win10, I'm on 15A244d right now still working.

0 Kudos
ccalabro
Contributor
Contributor

complete terminal commands, no errors, reboot

open fusion and add boot camp machine, option to access boot camp directly.

receive 'a failure occurred during Boot Camp volume preprocessing Internal Error, you may not be able to boot your Boot Camp volume as a virtual machine.=' error.

then when it tries to run it gives a 'operation not permitted error'

one point is that is does seem to think it is a windows 7 os not windows 10.

0 Kudos
wealthcharlie
Contributor
Contributor

Hi Guys, i found the solution.

The "rootless" will not work for El Capitan. We have to use below step to disable it.

  1. Boot into the recovery partition.
  2. Choose Security Configuration from the Utilities menu.
  3. Uncheck Enforce System Integrity Protection, click Apply Configuration
  4. Restart Mac.

Good Luck.

0 Kudos
ccalabro
Contributor
Contributor

thanks that did the trick.

0 Kudos
jwalbers
Contributor
Contributor

Thanks for the solution!  (I'm adding this note with additional detail to make it easier for others to find it.)

VMWare Fusion 7.1.2 and 7.1.3 (and likely earlier) cannot run BOOTCAMP VM on El Capitan 10.11.1 with System Integrity Protection (SIP) enabled.

Here are a few things I found out:

1. The Recovery System on my MBP2011 with El Capitan 10.11.1 does not have a Security Configuration Utility.  Use the alternate method: Start Terminal utility, run 'csrutil disable' at the command line, and restart.

2. One of the consequences of 'rootless' System Integrity Protection is that the system no longer allows writes to /dev/rdisk0.   This prevents malware from attacking via the bootloader.

3. There are cases where only the EFI volume showed in the available partitions list in the 'Choose a Bootcamp Volume' dialog.  Clear the BOOTCAMP metadata by deleting the BOOTCAMP subfolders of /Users/<user>/Library/Application Support/Virtual Machines/ directory and restart. The BOOTCAMP partition will then show up.  (See other VMWare KB articles for how to do this.)

It appears that when you create the BOOTCAMP VM, Fusion needs to write something to the MBR, or something, and that fails.   So you get an initial error:

-------------------------------------------

A failure occurred during Boot Camp volume preprocessing: Internal error

You may not be able to boot your Boot Camp volume as a virtual machine.

[OK]

-------------------------------------------

Sure, enough, if you try to start the new BOOTCAMP VM, you get this error:

-------------------------------------------

Operation not permitted

Cannot open the disk '/Users/<user>/Library/Application Support/VMware Fusion/Virtual Machines/Boot Camp/Boot Camp.vmwarevm/Boot Camp.vmdk or one of the snapshot disks it depends on.

Module Disk power on failed.

Failed to start the virtual machine.

[OK]

-------------------------------------------

You will also get this error if you successfully create the BOOTCAMP VM with SIP disabled (or in Yosemite, pre-upgrade), then try to run it with SIP enabled.

I couldn't find a log produced when Fusion creates the BOOTCAMP VM, but the log for BOOTCAMP shows these errors:

2015-11-15T00:44:27.475-06:00| vmx| I120: DISK: OPEN ide0:0 '/Users/<user>/Library/Application Support/VMware Fusion/Virtual Machines/Boot Camp/Boot Camp.vmwarevm/Boot Camp.vmdk' persistent R[]

2015-11-15T00:44:27.476-06:00| vmx| I120: DISKLIB-DSCPTR: Opened [0]: "Boot Camp-pt.vmdk" 0 (0x1a)

2015-11-15T00:44:27.478-06:00| vmx| I120: RawDiskAuthReadPrivilegesDictionary: processing 'always ask' UIDs: ''

2015-11-15T00:44:27.478-06:00| vmx| I120: RawDiskAuthReadPrivilegesDictionary: processing 'never ask' UIDs: '501, 502'

2015-11-15T00:44:27.478-06:00| vmx| I120: DISKLIB-FLAT  : opening raw device /dev/rdisk0

2015-11-15T00:44:27.478-06:00| vmx| I120: DISKLIB-DSCPTR: Opened [1]: "/dev/disk0" 34 partitionUUID @disk:diskModel=OWC|20Mercury|20Electra|206G|20SSD,diskSerialNumber=OW141221AS1653204,diskSize=960197124096 (0x1a)

2015-11-15T00:44:27.479-06:00| vmx| I120: DISKLIB-FLAT  : opening raw device /dev/rdisk0

2015-11-15T00:44:27.624-06:00| vmx| I120: DISKLIB-FLAT  : Unmounted "/dev/disk0" on open.

2015-11-15T00:44:27.626-06:00| vmx| I120: FileIOErrno2Result: Unexpected errno=1, Operation not permitted

2015-11-15T00:44:27.626-06:00| vmx| I120: AIOGNRC: Failed to open '/dev/rdisk0' : Operation not permitted (10002) (0x10103).

2015-11-15T00:44:27.626-06:00| vmx| I120: OBJLIB-FILEBE : FileBEOpen: can't open '/dev/rdisk0' : Operation not permitted (65540).

2015-11-15T00:44:27.626-06:00| vmx| I120: DISKLIB-FLAT  : "/dev/rdisk0" : failed to open (65545): ObjLib_Open failed.

...

2015-11-15T00:44:27.639-06:00| vmx| I120: Msg_Post: Error

2015-11-15T00:44:27.639-06:00| vmx| I120: [msg.literal] Operation not permitted

2015-11-15T00:44:27.639-06:00| vmx| I120: [msg.disk.noBackEnd] Cannot open the disk '/Users/<user>/Library/Application Support/VMware Fusion/Virtual Machines/Boot Camp/Boot Camp.vmwarevm/Boot Camp.vmdk' or one of the snapshot disks it depends on.

2015-11-15T00:44:27.639-06:00| vmx| I120: [msg.moduletable.powerOnFailed] Module Disk power on failed.

2015-11-15T00:44:27.639-06:00| vmx| I120: [msg.vmx.poweron.failed] Failed to start the virtual machine.

0 Kudos