A “DelayAtStartup” parameter would, perhaps, fill the bill. However, there is a need to specify a ’time period” value, specified by the user. For some users, five seconds is an eternity, while for others, twenty seconds is not be enough
The startup keys that you refer to are part of the Apple-custom-EFI. In order for VBox to "capture" those special Apple-specific-key-combinations, it would mean that the VBox developers would have to "mimic" the Apple-custom-EFI. It then wouldn't comply with the EFI specification which (IMHO) is more important than mirroring the Apple-custom-EFI setup.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
You mean this part on page 230 of the User Manual?
– By default, the VirtualBox EFI enables debug output of the Mac OS X kernel to help you diagnose boot problems. Note that there is a lot of output and not all errors are fatal (they would also show on your physical Mac). You can turn off these messages by issuing this command:
You do realize that some boot arguments rely on Apple's EFI to function, and that VirtualBox is not implementing or emulating Apple's EFI but a more generic version of UEFI.
rpmurray wrote:You do realize that some boot arguments rely on Apple's EFI to function, and that VirtualBox is not implementing or emulating Apple's EFI but a more generic version of UEFI.
I read this as Linux distributions do not have a Safe Mode and therefore this is not an issue
You're not reading it correctly. The "Safe mode" option in Linux and the rest of the BIOS-booting OSes comes as a part of the OS itself, not something that is happening at the BIOS boot phase. The Cmd-S for OSX is happening at the EFI boot phase. My comment back in November, which rpmurray echoed as well, outlines the reason why you don't get to invoke those special modes in VBox's EFI implementation.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
socratis wrote:You're not reading it correctly. The "Safe mode" option in Linux and the rest of the BIOS-booting OSes comes as a part of the OS itself, not something that is happening at the BIOS boot phase. The Cmd-S for OSX is happening at the EFI boot phase. My comment back in November, which rpmurray echoed as well, outlines the reason why you don't get to invoke those special modes in VBox's EFI implementation.
socratis wrote:...outlines the reason why you don't get to invoke those special modes in VBox's EFI implementation.
I found this conversation quite interesting, since I'm wondering exactly how VBox implements EFI (or even UEFI for that matter.) Where in the sources can I look for this?
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.