vmware-fusion-bootcamp
vmware-fusion-bootcamp copied to clipboard
mikew
Doesn't work with High Sierra beta 2 with APFS
When I run fusion-make-bootcamp on high sierra beta 2 all I get is an empty Boot Camp.XXXXXX folder on the desktop, no errors displayed
No real surprise here, you're running beta software after all. PR welcome if this is still an issue on official release.
Been digging a little further, I'm guessing this is the root cause of the issue
Sandbox: vmware-rawdiskCr(28140) System Policy: deny file-read-data /dev/disk0 Violation: System Policy: deny file-read-data /dev/disk0 MetaData: {"build":"Mac OS X 10.13 (17A291m)","action":"deny","target":["dev","disk0"],"hardware":"Mac","platform_binary":"no","profile":"unknown","process":"vmware-rawdiskCr","op":"file-read-data"}
Process: vmware-rawdiskCr [28140] Path: /Applications/VMware Fusion.app/Contents/Library/vmware-rawdiskCreator Load Address: 0x10d689000 Identifier: vmware-rawdiskCreator Version: ??? (???) Code Type: x86_64 (Native) Parent Process: sudo [28139] Responsible: /Applications/Utilities/Terminal.app/Contents/MacOS/Terminal [400] User ID: 0
Date/Time: 2017-07-06 19:49:02.258 GMT+1 OS Version: Mac OS X 10.13 (17A291m) Report Version: 8
Thread 0 (id: 563818): 0 libsystem_kernel.dylib 0x00007fffa6eb7d6a __open + 10 1 vmware-rawdiskCreator 0x000000010d689fc6 2 libdyld.dylib 0x00007fffa6d69ff9 start + 1 3 vmware-rawdiskCreator 0x0000000000000006
Binary Images:
0x10d689000 - 0x10d809fff vmware-rawdiskCreator (0) <0a69e465-d271-3dfc-8830-597c2f88905d> /Applications/VMware Fusion.app/Contents/Library/vmware-rawdiskCreator
0x7fffa6d69000 - 0x7fffa6d84ffb libdyld.dylib (513.2)
Oh wow, thanks for digging into this!
Looks like they've tightened up the security of raw disk access. I wonder if running vmware-rawdiskCreator with sudo yields anything different.
Hopefully we won't have to disable SIP just to get this working.
On Jul 6, 2017, at 3:53 PM, Nic Bedford [email protected] wrote:
Been digging a little further, I'm guessing this is the root cause of the issue
Sandbox: vmware-rawdiskCr(28140) System Policy: deny file-read-data /dev/disk0 Violation: System Policy: deny file-read-data /dev/disk0 MetaData: {"build":"Mac OS X 10.13 (17A291m)","action":"deny","target":["dev","disk0"],"hardware":"Mac","platform_binary":"no","profile":"unknown","process":"vmware-rawdiskCr","op":"file-read-data"}
Process: vmware-rawdiskCr [28140] Path: /Applications/VMware Fusion.app/Contents/Library/vmware-rawdiskCreator Load Address: 0x10d689000 Identifier: vmware-rawdiskCreator Version: ??? (???) Code Type: x86_64 (Native) Parent Process: sudo [28139] Responsible: /Applications/Utilities/Terminal.app/Contents/MacOS/Terminal [400] User ID: 0
Date/Time: 2017-07-06 19:49:02.258 GMT+1 OS Version: Mac OS X 10.13 (17A291m) Report Version: 8
Thread 0 (id: 563818): 0 libsystem_kernel.dylib 0x00007fffa6eb7d6a __open + 10 1 vmware-rawdiskCreator 0x000000010d689fc6 2 libdyld.dylib 0x00007fffa6d69ff9 start + 1 3 vmware-rawdiskCreator 0x0000000000000006
Binary Images: 0x10d689000 - 0x10d809fff vmware-rawdiskCreator (0) <0a69e465-d271-3dfc-8830-597c2f88905d> /Applications/VMware Fusion.app/Contents/Library/vmware-rawdiskCreator 0x7fffa6d69000 - 0x7fffa6d84ffb libdyld.dylib (513.2) /usr/lib/system/libdyld.dylib 0x7fffa6e9c000 - 0x7fffa6ec1ff7 libsystem_kernel.dylib (4481.0.0.1.1) <6d4ca4c4-82d1-3c58-b383-b6fd3c789de7> /usr/lib/system/libsystem_kernel.dylib
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/mikew/vmware-fusion-bootcamp/issues/4#issuecomment-313486765, or mute the thread https://github.com/notifications/unsubscribe-auth/AAASeY14_FpGJWWe5DVHH8Bn8KylOetBks5sLS0ugaJpZM4OOt86.
diskutil list
/dev/disk0 (internal):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme 500.3 GB disk0
1: EFI EFI 314.6 MB disk0s1
2: Apple_APFS Container disk1 440.0 GB disk0s2
3: Microsoft Basic Data Windows 10 59.9 GB disk0s3
/dev/disk1 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +440.0 GB disk1
Physical Store disk0s2
1: APFS Volume macOS High Sierra 362.3 GB disk1s1
2: APFS Volume Preboot 21.0 MB disk1s2
3: APFS Volume Recovery 519.7 MB disk1s3
4: APFS Volume VM 2.1 GB disk1s4
sudo /Applications/VMware\ Fusion\ Tech\ Preview.app/Contents/Library/vmware-rawdiskCreator hasBootCamp /dev/disk0 Unable to open "/dev/disk0": 1
Fusion Tech Preview works perfectly creating and running bootcamp with SIP Disabled
i then tried to re enable SIP with --without fs and it still works
Hi there... Yesterday I installed the release of MacOS High Sierra and the very first thing I tried was to launch my Windows 10 from the boot camp partition via VMware. Occurred this error:
"Cannot open the disk '/Users/felipe/VMware/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."
I was able to boot from the boot camp partition and run my Windows 10, but I couldn't tell boot camp app inside Windows 10 to restart the machine using the MacOS, which is not a huge problem at all. The problem is that I can't launch my Windows 10 from the VMware!
Fortunately, restoring the Time Machine to MacOS Sierra put everything back. @mikew, would your software fix this in High Sierra?
This very issue is about the fact that this script doesn't work at all in High Sierra. You can give it a try but it looks like they've hardened some security around disks in High Sierra.
Luckily, @C4Wiz mentions that the Fusion Tech Preview is working fine on High Sierra. Maybe give that a shot? I'm still waiting to upgrade my machines.
You can get the VMWare Fusion Tech Preview here.
Thanks @mikew! The Fusion 10 is about to be released early in October, I'm going to wait for it instead of installing High Sierra one more time. Cheers!
Luckily, @C4Wiz mentions that the Fusion Tech Preview is working fine on High Sierra. Maybe give that a shot? I'm still waiting to upgrade my machines.
But you MUST Disable SIP
FYI, on macOS Catalina, you need to grant com.vmware.DiskHelper full disk access, in Security and Privacy for this to work:
