I got MB 12inch 2015 and installed Win8.1 with bootcamp, making new VM with bootcamp. But VMware fusion said can't find Bootcamp partition. Of cause, Win8.1 can boot from bootcamp partition and I can use it. I also checked /Volumes/BOOTCAMP in OSX terminal. Why Fusion can't find Bootcamp partition? Any solution?
Below is results of diskutil command.
$ diskutil list
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.3 GB disk0
1: EFI EFI 314.6 MB disk0s1
2: Apple_CoreStorage 249.4 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
4: Microsoft Basic Data BOOTCAMP 250.0 GB disk0s4
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: Apple_HFS Macintosh HD *249.0 GB disk1
Logical Volume on disk0s2
004E22E3-0759-417F-8E0C-C703F376B675
Unencrypted
Apple could have dropped support for BOOTCAMP
SEE
System requirements to install Windows on your Mac via Boot Camp - Apple Support
Have the exact same problem. Hope VMware can address soon.
When i run the command (under sudo) - "./vmware-rawdiskCreator print /dev/disk0" I get the response "Unable to scan the partition table of "/dev/disk0"."
I looked at the Apple link the other poster provided, but as that links states, using Boot Camp Assistant (5.1.4 in my case), is supported, for Win 8.1 (what i'm using), and i had an MS-DOS USB drive for drivers (which load fine), bottom line, there is no issue at all loading Win 8.1 on the Macbook, i can boot into it fine.
The problem is entirely with VMware reading the partition and setting up a VM to use from within OS X. VMware need to fix presumably, looking at forums, seems they had similar work todo a couple of years ago with previous versions.
FWIW - I'm using Fusion 7.1.1
I have the exact same issue. Brand new 12inch MacBook. Successfully installed Windows 8.1. Booting to Windows partition and coming back to Mac works fine. I can see the Windows partition as a separate hard drive in Finder. But VMware Fusion says there is no bootcamp partition when I try to create a vm based on bootcamp.
Same here, but on a Mac Pro. I can setup a Bootcamp VM in Fusion, but when I try to create an additional mapping from a partition to a new disk within the VM, I find that 'vmware-rawdiskCreator' isn't working properly:
$ diskutil list
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.3 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_HFS Macintosh HD 436.0 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
4: Microsoft Basic Data Windows 8 63.4 GB disk0s4
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *4.0 TB disk1
1: EFI EFI 314.6 MB disk1s1
2: Microsoft Basic Data LaCie 3.5 TB disk1s2
3: Apple_HFS Macintosh Extension 499.4 GB disk1s3
/dev/disk2
#: TYPE NAME SIZE IDENTIFIER
0: Scratch *4.0 GB disk2
/dev/disk5
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *499.8 GB disk5
1: EFI EFI 209.7 MB disk5s1
2: Apple_HFS Time Machine Backups 499.4 GB disk5s2
$ sudo ./vmware-rawdiskCreator print /dev/disk0
Nr Start Size Type Id Sytem
-- ---------- ---------- ---- -- ------------------------
1 40 409600 GPT EE Efi System
2 409640 851562496 GPT EE Apple HFS
3 851972136 1269536 GPT EE Unknown
4 853241856 123863040 GPT EE Basic Data
$ sudo ./vmware-rawdiskCreator print /dev/disk1
Unable to scan the partition table of "/dev/disk1".
$ sudo ./vmware-rawdiskCreator print /dev/disk2
Unable to open "/dev/disk2": 16
$ sudo ./vmware-rawdiskCreator print /dev/disk3
Unable to open "/dev/disk3": 16
$ sudo ./vmware-rawdiskCreator print /dev/disk4
Unable to open "/dev/disk4": 16
$ sudo ./vmware-rawdiskCreator print /dev/disk5
Nr Start Size Type Id Sytem
-- ---------- ---------- ---- -- ------------------------
1 40 409600 GPT EE Efi System
2 409640 975409040 GPT EE Apple HFS
What I'm trying to do is create a VMDK to allow the VM direct access to /dev/disk1s2... and for some reason I'm getting the 'Unable toscan the partition table' error.
I'll take a look to see whether VIrtualBox includes a tool which can generate this for me... but this really shouldn't be necessary
I also am experiencing this issue on a new MacBook. The one difference i see is PMBR instead of MBR on my other macs. Is this the reason why? Is there another tool that will create the vmdk?
sudo ./vmware-rawdiskCreator hasBootCamp /dev/disk0
Unable to scan the partition table of "/dev/disk0".
sudo gpt show -l /dev/disk0
start size index contents
0 1 PMBR
1 1 Pri GPT header
2 4 Pri GPT table
6 76800 1 GPT part - "EFI System Partition"
76806 97498133 2 GPT part - "Customer"
97574939 158692 3 GPT part - "Recovery HD"
97733631 1
97733632 24404480 4 GPT part - "BOOTCAMP"
122138112 15
122138127 4 Sec GPT table
122138131 1 Sec GPT header
The interesting thing about the new MacBook (12-inch, Retina, Early 2015) is that it ships with an SSD exposing 4Kb sectors. The virtualization in VMware Fusion exposes 512-byte sectors. The Mac's GPT is based on 4Kb sectors, and the installation of Windows in your Boot Camp is based on that too, so we have a mismatch. Fusion is interpreting the GPT in 512-byte sectors (which is wrong; we're working on that) which is why it doesn't find your Boot Camp partition.
This is under active investigation here at VMware, but I don't have a workaround at this time. I'm sorry, we were caught by surprise on this too.
Thank you for the reply, good to know it's under investigation. Appreciate your honest and open response and taking accountability.
Is there an issue number so we can track when this will be resolved?
I am having this problem with my 2015 12" MacBook as well..
Any word if this is just the 12" or if the new 13" and 15" models have a similar problem?
I don't believe the Fusion team has gotten one of the new Macs in yet, but I suspect that they use the same SSD as the 12", in which case yes, they would have the same problem.
Any update on a fix for this problem?
At least on the 15', diskutil info still reports 512 blocks.
Is there any updates on this issue? I'm facing this on 2015 macbook 12-inch as well...
Tested today on a brand new Macbook and was also unable. I rebooted into recovery, and did a full wipe and reinstall of the OS 10.10.x and everything worked fine after. Not sure why.
After reinstall you were able to see the bootcamp partition in vmware fusion and boot to it?
So your macbook 12-inch 2015 is able to boot into windows via virtual machine and bootcamp now?
I did a full reinstall (with creating new partitions) of the macbook with the same result... bootcamp + fusion won't work.
Hence I wonder how he/she can get the vmware works on bootcamp partition.