I confirm this problem on a Macbook Pro late 2016 with Sierra. Would be very nice if this gets solved.VBoxManage: error: Cannot read the partition information from '/dev/disk0'
VBoxManage: error: The raw disk vmdk file was not created
Thanks
I confirm this problem on a Macbook Pro late 2016 with Sierra. Would be very nice if this gets solved.VBoxManage: error: Cannot read the partition information from '/dev/disk0'
VBoxManage: error: The raw disk vmdk file was not created
You know what would be even nicer? If you read the thread from the beginning and gave us some more details about your setup. We're trying to make a compilation of the circumstances that might cause this error, as you might notice. A simple "me too" doesn't really help...Zillion01 wrote:Would be very nice if this gets solved.
quantor: (1) Host=10.12.4, Upgrade=YES(*), Guest=Win10, VBox=5.1.18, Filevault=Yes, FileVaultBeforeBootcamp=YES, Works = NO (2) Host=10.12.4, Upgrade=YES(*), Guest=Win10, VBox=5.1.12, Filevault=Yes, FileVaultBeforeBootcamp=YES, Works = NO (3) Host=10.12.2, Upgrade=YES(%), Guest=Win8($), VBox=5.1.12, Filevault=Yes, FileVaultBeforeBootcamp=NO, Works = YES (4) Host=10.12.4, Upgrade=YES(*), Guest=Win8, VBox=5.1.12, Filevault=Yes, FileVaultBeforeBootcamp=YES, Works = YES (5) Host=10.12.4, Upgrade=YES(*), Guest=Win8, VBox=5.1.20, Filevault=Yes, FileVaultBeforeBootcamp=YES, Works = YESI'm also going to try it with Win10, but this could take some time until I have results...
quantor: (1) Host=10.12.4, Upgrade=YES(*), Guest=Win10, VBox=5.1.18, Filevault=Yes, FileVaultBeforeBootcamp=YES, Works = NO (1.5) Host=10.12.4, Upgrade=YES(*), Guest=Win10, VBox=5.1.20, Filevault=Yes, FileVaultBeforeBootcamp=YES, Works = NO (2) Host=10.12.4, Upgrade=YES(*), Guest=Win10, VBox=5.1.12, Filevault=Yes, FileVaultBeforeBootcamp=YES, Works = NO (3) Host=10.12.2, Upgrade=YES(%), Guest=Win8($), VBox=5.1.12, Filevault=Yes, FileVaultBeforeBootcamp=NO, Works = YES (4) Host=10.12.4, Upgrade=YES(*), Guest=Win8, VBox=5.1.12, Filevault=Yes, FileVaultBeforeBootcamp=YES, Works = YES (5) Host=10.12.4, Upgrade=YES(*), Guest=Win8, VBox=5.1.20, Filevault=Yes, FileVaultBeforeBootcamp=YES, Works = YES (6) Host=10.12.4, Upgrade=YES(*), Guest=Win10(!), VBox=5.1.20, Filevault=Yes, FileVaultBeforeBootcamp=YES, Works = YES(!) Upgrade from Win8
Take a look at: Virtualbox 5.1.20 application crashes on OSX ≥ 10.12.4.quantor wrote:but VBox does not run anymore?? It crashes after each start
Yes, I installed a fresh Win10 in my Bootcamp on the new Mac. Bootcamp on a new Mac only allows to install Win10. On the old Mac, Bootcamp can only install Win7 or Win8 (which can be updated later to Win10).Did you install a fresh Win10 in your Bootcamp?
That would be a more appropriate and narrower description of the problem, no?Did you install a fresh Win10 in your Bootcamp?
Then the "VBoxManage internalcommands createrawvmdk" might fail.
Yes, that sounds like a reasonable description. But that would also mean this problem is specific to the new MBP's, as they only allow to install a fresh Win10...Did you install a fresh Win10 in your Bootcamp?
Then the "VBoxManage internalcommands createrawvmdk" might fail.
Yes I did, yes I have. After trying out all stuf I found on Google I can only conclude it has to do with the newer models of Macbook Pro.quantor wrote: @Zillion01: Did you install Bootcamp before you tried to read the partition information? Do you have FileVault installed or not? Would be nice if you could contribute to the matrix...
It (meaning VirtualBox) might be having some trouble recognizing the (potentially) new partition scheme employed by a Win10/Bootcamp combination. Once confirmed, you could open a new ticket and hope for the best.quantor wrote:Does that mean it will simply not work on my MBP?
I'm not sure how whoosh is translated, but it does NOT have to do anything with the hardware. It's all in the software.Zillion01 wrote:I can only conclude it has to do with the newer models of Macbook Pro.
Code: Select all
sudo VBoxManage internalcommands createrawvmdk -rawdisk /dev/disk0 -filename win10raw.vmdk -partitions 1,4
Apple themselves had not come up with a resolution for this, they're struggling with Win10 just like everyone else. Do you expect 3rd party software that relies on Apple to be there before Apple? On the newly (two days ago) released 10.12.5, it states:samsonthebrave wrote:Wondering if we've come to a resolution for this issue?
Plus, did you read the thread from the beginning? If so, can you answer the important key question in this thread? In the post just above yours.Adds support for media-free installation of Windows 10 Creators Update using Boot Camp