Bootcamp guest fails to boot after upgrade to MacOS High Sierra

Discussions related to using VirtualBox on Mac OS X hosts.
MattLC
Posts: 3
Joined: 17. Feb 2018, 00:41

Re: Bootcamp guest fails to boot after upgrade to MacOS High Sierra

Post by MattLC »

Thanks Socratis, "still" refers to me trying everything on the discussion thread and not cracking it
As requested:

Code: Select all

MLC$ diskutil list
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *251.0 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk1         180.8 GB   disk0s2
   3:       Microsoft Basic Data BOOTCAMP                70.0 GB    disk0s3

/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +180.8 GB   disk1
                                 Physical Store disk0s2
   1:                APFS Volume Macintosh HD            159.9 GB   disk1s1
   2:                APFS Volume Preboot                 33.4 MB    disk1s2
   3:                APFS Volume Recovery                509.9 MB   disk1s3
   4:                APFS Volume VM                      2.1 GB     disk1s4
Before the High Sierra update, the VMDK was working fine
Last edited by socratis on 19. Feb 2018, 12:22, edited 1 time in total.
Reason: Enclosed the information in [code] tag for better readability
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Bootcamp guest fails to boot after upgrade to MacOS High Sierra

Post by socratis »

OK, thank you for that. I'm going to need two more things (sorry, I should have asked earlier):
  1. The contents of the VMDK. It's a simple text file, so open it with a text editor and post its contents.
  2. The output of the command:
    • ls -al /dev/disk*
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
MattLC
Posts: 3
Joined: 17. Feb 2018, 00:41

Re: Bootcamp guest fails to boot after upgrade to MacOS High Sierra

Post by MattLC »

OK, here is the info
1/ This is for the newly created one, RawWinDisk:

Code: Select all

# Disk DescriptorFile
version=1
CID=139d9dc0
parentCID=ffffffff
createType="fullDevice"

# Extent description
RW 136716288 FLAT "/dev/disk0s3" 0

# The disk Data Base 
#DDB

ddb.virtualHWVersion = "4"
ddb.adapterType="ide"
ddb.geometry.cylinders="16383"
ddb.geometry.heads="16"
ddb.geometry.sectors="63"
ddb.uuid.image="ea379f68-f532-4ea4-9a38-45f2c5414ef9"
ddb.uuid.parent="00000000-0000-0000-0000-000000000000"
ddb.uuid.modification="00000000-0000-0000-0000-000000000000"
ddb.uuid.parentmodification="00000000-0000-0000-0000-000000000000"
and this is the for the VM that worked before the upgrade to High Sierra

Code: Select all

# Disk DescriptorFile
version=1
CID=99eb8763
parentCID=ffffffff
createType="partitionedDevice"

# Extent description
RW 40 FLAT "win7raw-pt.vmdk" 0
RW 409600 ZERO 
RW 351836784 ZERO 
RW 1269536 ZERO 
RW 1608 ZERO 
RW 136716288 FLAT "/dev/disk0s4" 0
RW 863 ZERO 
RW 33 FLAT "win7raw-pt.vmdk" 40

# The disk Data Base 
#DDB

ddb.virtualHWVersion = "4"
ddb.adapterType="ide"
ddb.geometry.cylinders="16383"
ddb.geometry.heads="16"
ddb.geometry.sectors="63"
ddb.uuid.image="5fe65d93-a175-45bd-8b60-1b9d8f3fe7d4"
ddb.uuid.parent="00000000-0000-0000-0000-000000000000"
ddb.uuid.modification="4383770f-3ef3-408d-acda-c52204749f93"
ddb.uuid.parentmodification="00000000-0000-0000-0000-000000000000"
ddb.geometry.biosCylinders="1024"
ddb.geometry.biosHeads="255"
ddb.geometry.biosSectors="63"
2/

Code: Select all

MLC$ ls -al /dev/disk*
brwxrwxrwx  1 root  operator    1,   0 16 Feb 22:03 /dev/disk0
brw-r-----  1 root  operator    1,   1 16 Feb 22:03 /dev/disk0s1
brw-r-----  1 root  operator    1,   3 16 Feb 22:03 /dev/disk0s2
brwxrwxrwx  1 root  operator    1,   2 16 Feb 22:03 /dev/disk0s3
brw-r-----  1 root  operator    1,   4 16 Feb 22:03 /dev/disk1
brw-r-----  1 root  operator    1,   5 16 Feb 22:03 /dev/disk1s1
brw-r-----  1 root  operator    1,   6 16 Feb 22:03 /dev/disk1s2
brw-r-----  1 root  operator    1,   7 16 Feb 22:03 /dev/disk1s3
brw-r-----  1 root  operator    1,   8 16 Feb 22:03 /dev/disk1s4
brw-r-----  1 root  operator    1,   9 16 Feb 22:03 /dev/disk2
brw-r-----  1 root  operator    1,  10 16 Feb 22:03 /dev/disk2s1
Last edited by socratis on 20. Feb 2018, 08:49, edited 1 time in total.
Reason: Enclosed the information in [code] tag for better readability
Post Reply