Running: VMware Fusion Player Version 12.0.0 (16880131)
on software: macOS Big Sur Version 11.0 beta (beta 6, beta 7, beta 8, beta 9, beta 10)
macOS Big Sur Version 11.0.1 beta
on hardware: MacBook Pro (15-inch, 2016)
Boot Camp VM from Fusion 11 encountered error: The operation on file "/dev/disk0s1" failed.
This error occurs when "Attempting to start up from: -> EFI VMware Virtual SATA Hard Drive (0.0) ..."
The problem persists when starting fresh and creating a new Boot Camp VM.
All non-BootCamp VMs seem to work fine so far (with the exception of sound).
What I've tried:
- Completely removing and recreating Boot Camp partition
- Granting Full Disk Access to VMware Fusion 12
- Deleting the VM are starting anew with VMware Fusion 12
- Disabling SIP
- Reset NVRAM
- Running First Aid on all disks/volumes from Recovery Mode
- Launching VMware Fusion as root (sudo)
- Booted MacBook directly into boot camp partition and:
- verified free space
- verified no file system problems/errors
- installed updates
Notable/relevant errors in vmware.log:
vmx| I005: DEVCREAT: Found a device: /dev/disk0s1
vmx| I005: HOSTDISK-MACOS:Whole disk device path for /dev/disk0s1 is /dev/disk0.
vmx| I005: FILE:open error on /dev/disk0: Operation not permitted
vmx| I005: AIOGNRC: Failed to open '/dev/disk0' : Operation not permitted (10002) (0x101).
vmx| I005: OBJLIB-FILEBE : FileBEOpen: can't open '/dev/disk0' : Operation not permitted (65540).
vmx| I005: FILE:open error on /dev/disk0: Operation not permitted
vmx| I005: OBJLIB-FILEBE : FileBEOpen: can't open '/dev/disk0' : Operation not permitted (65540).
Notable/relevant errors in Console App:
client error 19:20:26.109292-1000 vmware-vmx unable to normalize volume: "<private>", tmp_result: <private>
client error 19:20:26.109386-1000 vmware-vmx Failed to get available space for volume <private>: Error Domain=CacheDeleteErrorDomain Code=10 UserInfo={Volume=<private>}
client error 19:20:26.109509-1000 vmware-vmx unable to normalize volume: "<private>", tmp_result: <private>
client error 19:20:26.109654-1000 vmware-vmx validatedCachedResults: unable to create keyName from: {
"CACHE_DELETE_AVAILABLE_SPACE_CLASS" = 3;
"CACHE_DELETE_VOLUME" = "/dev";
}
(See attachment for more from Console.)
I assume this is due to some new security feature in macOS 11 preventing programs from taking control of partitions/volumes.
Is this a known issue? Is there a fix or workaround?
Message was edited by: Jason_MC Attached vmware.log
Message was edited by: Jason_MC. Updated OS versions. Problem still exists.
Message was edited by: Jason_MC. Updates OS versions. Added apparently relevant lines from vmware.log.
Message was edited by: Jason_MC to include having tried recreating Boot Camp partition.
Message was edited by: Jason_MC. Updated OS Versions. Now tested on Big Sur betas 6 through 10. Problem remains the same.
Message was edited by: Jason_MC. Updated OS Versions tested. Same problem and symptoms on macOS 11.0.1 beta