Here's what I've got (username removed from path), I've tried both CustomTable and (for 6.0.0) CustomTable0. Code: <ExtraDataItem name="VboxInternal/Devices/acpi/0/Config/CustomTable0" value="/Users/******/slic.bin"/> <ExtraDataItem name="VboxInternal/Devices/pcbios/0/Config/DmiBIOSFirmwareMajor" value="0"/> <ExtraDataItem name="VboxInternal/Devices/pcbios/0/Config/DmiBIOSFirmwareMinor" value="0"/> <ExtraDataItem name="VboxInternal/Devices/pcbios/0/Config/DmiBIOSReleaseDate" value="07/01/2016"/> <ExtraDataItem name="VboxInternal/Devices/pcbios/0/Config/DmiBIOSReleaseMajor" value="0"/> <ExtraDataItem name="VboxInternal/Devices/pcbios/0/Config/DmiBIOSReleaseMinor" value="0"/> <ExtraDataItem name="VboxInternal/Devices/pcbios/0/Config/DmiBIOSVendor" value="Dell Inc."/> <ExtraDataItem name="VboxInternal/Devices/pcbios/0/Config/DmiBIOSVersion" value="A14"/> <ExtraDataItem name="VboxInternal/Devices/pcbios/0/Config/DmiBoardProduct" value="0HHV7N"/> <ExtraDataItem name="VboxInternal/Devices/pcbios/0/Config/DmiBoardVendor" value="Dell Inc."/> <ExtraDataItem name="VboxInternal/Devices/pcbios/0/Config/DmiBoardVersion" value="A00"/> <ExtraDataItem name="VboxInternal/Devices/pcbios/0/Config/DmiChassisType" value="0x7"/> <ExtraDataItem name="VboxInternal/Devices/pcbios/0/Config/DmiChassisVendor" value="Dell Inc."/> <ExtraDataItem name="VboxInternal/Devices/pcbios/0/Config/DmiSystemProduct" value="Precision Tower 5810"/> <ExtraDataItem name="VboxInternal/Devices/pcbios/0/Config/DmiSystemSKU" value="string:0617"/> <ExtraDataItem name="VboxInternal/Devices/pcbios/0/Config/DmiSystemSerial" value="2DD3LM3"/> <ExtraDataItem name="VboxInternal/Devices/pcbios/0/Config/DmiSystemVendor" value="Dell Inc."/>
Is the path correct? Mac OS is UNIX-like and has a case sensitive file system. Do you run the Guest as EFI? My EFI Guests (although on Windows Host) also see no SLIC table.
The path is correct (case as well). I've tried changing the case (in case) to no avail. The weird thing is that even if I change it to something I know is wrong (e.g. slic.bix instead of slic.bin) it doesn't grumble and doesn't show anything in the logs. It's a non-EFI guest, although the host system is a MacBook Pro so it's an EFI host. Changing to ICH9 adds more stuff for RWEverything to find, but still no SLIC.
Maybe it's not implemented in the Mac version? But it should, given it's mentioned in the manual... Cannot check, unfortunately. Best would be to ask them directly. Maybe someone else with the Mac version could shed some light on this?
Just for the fun of it i tried to OEM activate Windows server 2016 using a SLIC and MSDM in new VirtualBox 6.0.2 which supports multiple 'CustomTable' entries Code: <ExtraDataItem name="VBoxInternal/Devices/acpi/0/Config/CustomTable0" value="/path/to/slic.bin"/> <ExtraDataItem name="VBoxInternal/Devices/acpi/0/Config/CustomTable1" value="/path/to/msdm.bin"/> slic.bin (DELL 2.4) Code: 53 4C 49 43 76 01 00 00 01 A6 44 45 4C 4C 20 20 50 45 5F 53 43 33 20 20 09 20 07 01 41 4D 49 20 13 00 01 00 00 00 00 00 9C 00 00 00 06 02 00 00 00 24 00 00 52 53 41 31 00 04 00 00 01 00 01 00 7F F6 C1 05 BE 5C 57 63 A5 8A 68 F3 6E 8F 06 FA AF B4 9F 68 82 23 EC 50 40 5A 73 7F EC E4 07 CB DC 25 1A 9C E3 E3 66 11 E0 A5 98 06 C5 80 0A FA 42 93 86 98 E7 D5 1B D4 D7 3A A4 0B EE E2 7D BE 5F 5B 15 0C AB D0 21 DE BF E9 B5 6E A4 57 B9 8C 0C D2 BA 3A 69 30 76 94 71 A2 64 D7 4C D8 85 BF DF A5 6A C8 DC 45 D5 4D 8C B8 8C 05 2F FC 2E 23 C4 29 C5 6F 3F 29 6C 6D 57 79 0E B6 75 ED 21 95 01 00 00 00 B6 00 00 00 00 00 02 00 44 45 4C 4C 20 20 50 45 5F 53 43 33 20 20 57 49 4E 44 4F 57 53 20 04 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0C 38 B7 C3 1B 3C 6E 85 C6 6A 64 A2 08 13 B7 24 93 1B B8 66 C4 0C B9 45 33 91 1C 9E 94 63 B1 1F 7E 52 31 E6 E2 D0 DC 99 DD B7 0D 5B 7B A1 1C 2C 62 EB 65 35 C2 DB BC 29 39 63 8E 14 58 CB 63 B4 D7 7F 3A 12 63 7E CA FE B4 03 B0 CF 49 21 AD DA D5 CF 3E C0 57 6F 2B A7 55 1F 01 CB 73 20 6D 19 26 DB 9A 6B AE 03 1A 9D C9 8D A3 9F 71 49 39 B2 FA 07 3B 01 47 28 43 C5 D8 C2 4C 8C AC 7F BA F8 msdm.bin (key from here) Code: 4D 53 44 4D 55 00 00 00 03 82 44 45 4C 4C 20 20 50 45 5F 53 43 33 20 20 09 20 07 01 41 4D 49 20 13 00 01 00 01 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 1D 00 00 00 32 34 39 39 4E 2D 42 43 47 58 33 2D 46 48 4A 4B 46 2D 44 48 39 51 52 2D 38 42 36 33 57 After installing certificate, it was activated immediately (after reboot) as it uses the key from msdm.bin
Maybe i have to revoke the above claim, i tried it with DataCenter as well, that failed, then after turning back to Standard that won't (auto)activate anymore either. Very strange...
Just wanted to report that I tried VB 6.0.4 on macOS 10.13.6 host for an XP Mode VM, no BIOS change. Works fine! "Already activated".
Anyway, here's recompiled BIOS for XPMode with latest VBox: http[://]s000.tinyupload.com/?file_id=20583976423065390451 Code: BiosAlternative.7z 32666 Bytes CRC32: F93E745D MD5: 3EDBB201554D5075856399CFDD2505C9 SHA1: 5D646D07086F33A6ABF54B8AC37BE67260E92873 Password: mdl2019 cK