[vbox-dev] Modified BIOS identification

Michal Necasek michal.necasek at oracle.com
Mon Dec 26 10:52:57 UTC 2016

 Yes, the information is in VBox.log already. The "VMMDev: Guest Log: BIOS: VirtualBox 5.1.12" line is not it, that is simply a log message from the BIOS itself. It doesn't say anything about whether the BIOS was modified or not.

 But if there is an entry that says "PcBios: Using BIOS ROM <pathname>" then a non-default BIOS image was loaded. That reflects the CFGM key /Devices/pcbios/0/Config/BiosRom. If that line isn't there, it means the built-in BIOS image shipped with VirtualBox was loaded. 

    - Michal

----- Original Message -----
From: socratisk at gmail.com
To: vbox-dev at virtualbox.org
Sent: Saturday, December 24, 2016 11:43:40 AM GMT +01:00 Amsterdam / Berlin / Bern / Rome / Stockholm / Vienna
Subject: [vbox-dev] Modified BIOS identification

There have been two discussions so far (that I remember of) about end users providing their own BIOS.
• https://forums.virtualbox.org/viewtopic.php?f=6&t=79336https://forums.virtualbox.org/viewtopic.php?f=6&t=81155

If more and more people are modifying the default BIOS, expect all hell to brake loose in terms of support. There needs to be a way to identify the "rebels" that have modified the BIOS. Anything in place so far? Is the line:
	"00:00:09.363662 VMMDev: Guest Log: BIOS: VirtualBox 5.1.12"
good enough? Or maybe there should be a checksum (SHA?) in the [/Devices/pcbios/0/Config/] section of the log? Something like the "OSE" or "_Distro" flags about VirtualBox itself?
vbox-dev mailing list
vbox-dev at virtualbox.org

More information about the vbox-dev mailing list