Opened 8 years ago
Closed 8 years ago
#15884 closed defect (worksforme)
Attaching a BIOS file to a VM does not work in VirtualBox 5.1.4
| Reported by: | bmn | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.1.4 |
| Keywords: | Cc: | ||
| Guest type: | other | Host type: | other |
Description
In VirtualBox 5.0.x it is possible to use the command
VBoxManage.exe setextradata MyVM VBoxInternal/Devices/pcbios/0/Config/BiosRom C:\bios.bin
to attach a BIOS file to a VM.
This feature is broken in VirtualBox 5.1.4. When the command is applied, the VM hangs during startup and does not boot the guest OS. (The same VM does boot the guest OS when no BIOS file is attached to it.)
The problem seems to be independent from the BIOS file, since it occurs even if the file bios.bin is an unaltered copy of VirtualBox 5.1.4's own BIOS (as it can be extracted from VBoxDD2.dll).
Attachments (2)
Change History (5)
by , 8 years ago
by , 8 years ago
comment:1 by , 8 years ago
comment:2 by , 8 years ago
Thank you very much for pointing me in the right direction. I extracted the BIOS file from VB 5.1 the same way that had worked with VB 5.0, but I did not consider that in 5.1 more than one image exists in the system. But now I managed to obtain the 386+ BIOS image and the function to attach a custom BIOS is shown to work correctly.
The BIOS file you extracted from VBoxDD2.dll and attached here seems to be for one of the old CPU profiles VBox starts to support with 5.1 (see here and search for --cpu-profile). Using the BIOS image for 386+ CPUs works correctly here even if using it as separate image file. Is it possible that the custom BIOS you are using works with one of the profiles for older architectures?