DmiBIOSFirmwareMajor set to incorrect value
After running setslic on my VM, I get the following error in VirtualBox
Configuration error: Querying "DmiBIOSFirmwareMajor" as an int failed (VERR_CFGM_NOT_INTEGER).
seems like an error message ended up in my config:
<ExtraDataItem name="VBoxInternal/Devices/pcbios/0/Config/DmiBIOSFirmwareMajor" value="ERROR: Cannot find value for BIOS"/>
<ExtraDataItem name="VBoxInternal/Devices/pcbios/0/Config/DmiBIOSFirmwareMinor" value="ERROR: Cannot find value for BIOS"/>
<ExtraDataItem name="VBoxInternal/Devices/pcbios/0/Config/DmiBIOSReleaseDate" value="10/12/2016"/>
<ExtraDataItem name="VBoxInternal/Devices/pcbios/0/Config/DmiBIOSReleaseMajor" value="1"/>
<ExtraDataItem name="VBoxInternal/Devices/pcbios/0/Config/DmiBIOSReleaseMinor" value="4"/>
<ExtraDataItem name="VBoxInternal/Devices/pcbios/0/Config/DmiBIOSVendor" value="Dell Inc."/>
<ExtraDataItem name="VBoxInternal/Devices/pcbios/0/Config/DmiBIOSVersion" value="1.4.10"/>
After changing the values to match ReleaseMinor/Major, I get
Configuration error: Querying "DmiSystemSKU" as a string failed (VERR_CFGM_NOT_STRING).
Which corresponds to
<ExtraDataItem name="VBoxInternal/Devices/pcbios/0/Config/DmiSystemSKU" value="0704"/>
Adding a space to the start of that value 'fixes' it. Haven't tried activating VM Windows yet, though.
Seems like VirtualBox bugs to me but I thought it was worth reporting anyway.
I have submitted a pull request to fix issue number one, as I have seen this on my dell system as well.
With the SKU not sure though, for me it worked. No idea how we could detect that.
In order to make SKU work I had to prepend string: - something like:
<ExtraDataItem name="VBoxInternal/Devices/pcbios/0/Config/DmiSystemSKU" value="string:1234"/>