Page 1 of 1
Configuring the BIOS DMI information
Posted: 3. Sep 2014, 17:26
by king
Hello
Thanks to dmidecode i know that some system informations are set by default in the VM. I know that one may change them, but i was wondering, if it is possible to reset them, so that they appear unknown or unspecified. I tried:
VBoxManage setextradata “MyXP_VM” “VBoxInternal/Devices/pcbios/0/Config/DmiProcVersion” “Pentium(R) III”
but it doesn't seem to work.
Thanks again for the help, and sorry for being a pain...
Best regards,
Re: Configuring the BIOS DMI information
Posted: 3. Sep 2014, 18:55
by Perryg
If you have set extradata and now you want it to go back to default just run the same command without a value.
IE:
VBoxManage setextradata “MyXP_VM” “VBoxInternal/Devices/pcbios/0/Config/DmiProcVersion” “Pentium(R) III”
to remove the above run the following
VBoxManage setextradata “MyXP_VM” “VBoxInternal/Devices/pcbios/0/Config/DmiProcVersion”
Re: Configuring the BIOS DMI information
Posted: 4. Sep 2014, 04:00
by rpmurray
Actually I believe in order to have them appear as unknown or unspecified you need to use:
VBoxManage setextradata “MyXP_VM” “VBoxInternal/Devices/pcbios/0/Config/DmiProcVersion” "<EMPTY>"
From the User Manual:
If a DMI string is not set, the default value of VirtualBox is used. To set an empty string use "<EMPTY>".
Re: Configuring the BIOS DMI information
Posted: 4. Sep 2014, 10:00
by dlharper
No, Perry is right here. If you do what rpmurray suggests you will get a processor called "<EMPTY>".
The reason it is put this way in the manual is quite simply that is difficult to write a sentence that seems to make sense but includes the null string. To write:
or something like that make people think there is a typographical error.
Re: Configuring the BIOS DMI information
Posted: 4. Sep 2014, 15:12
by rpmurray
My bad. I thought there might be a difference between sending an empty string "" which removes the setextradata entry in the vbox setting file (and therefore VirtualBox will use the default value for DmiProcVersion) and sending "<EMPTY>" which I assumed meant that instead of using the default value the VM would report it as undefined. I should have tested this first.