Question: How to rebrand the EFI firmware used by VirtualBox

Discussions related to using the OSE version of VirtualBox.
Post Reply
fluoriteByte
Posts: 1
Joined: 2. Jan 2025, 20:42
Primary OS: Linux other
VBox Version: OSE other
Guest OSses: Various Linuxes, some old windows versions

Question: How to rebrand the EFI firmware used by VirtualBox

Post by fluoriteByte »

Hello, this one comes here asking for assistance, is making a VirtualBox soft-fork rebrand for flatpak distribution, ik from the licensing FAQ that this one mustn't use the VirtualBox name in any branding capacity for distributing modified binaries (contains patches to remove PAM dependency, cyberus technologies's KVM backend patched and some other stuff), and have tried to rebrand it, so far, have successfully changed many images and strings, (even in the translation files), but this one has been stuck trying to rebrand the UEFI used by VirtualBox, this one has tried many things including: trying to replace the bmp file directly (correctly set to 24-Bit) and replacing the EFI firmware with OVMF's, none of these have worked, this one wishes to find a way change it,
thanks for reading this topic, and apologies for the lengthy post
:D
klaus
Oracle Corporation
Posts: 1648
Joined: 10. May 2007, 14:57

Re: Question: How to rebrand the EFI firmware used by VirtualBox

Post by klaus »

Check the commit log for the EFI logo... I think it contains the ImageMagick command line used to produce the current image. The BMP format is very tricky because it exists in many incompatible variants. Of course you could also go for the instructions in EDK2.
Post Reply