[vbox-dev] Modified BIOS identification
michal.necasek at oracle.com
Mon Dec 26 15:58:05 UTC 2016
For OSE builds, users can modify whatever they like. And they don't get any official support from Oracle.
For Windows and OS X builds, the BIOS image is coming out of a signed binary that users can't modify. On Linux, superusers could modify the image. But I don't see what would be the point because it's far easier to point VirtualBox at an external BIOS image.
----- Original Message -----
From: socratisk at gmail.com
To: michal.necasek at oracle.com
Cc: vbox-dev at virtualbox.org
Sent: Monday, December 26, 2016 2:51:47 PM GMT +01:00 Amsterdam / Berlin / Bern / Rome / Stockholm / Vienna
Subject: Re: [vbox-dev] Modified BIOS identification
On 26/Δεκ/2016, at 12:52, Michal Necasek <michal.necasek at oracle.com> wrote:
> 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.
Thank you Michal,
But what about if you replace the built-in BIOS "in place"? Is there a check for that?
More information about the vbox-dev