On Wed, Mar 15, 2023 at 02:51:36AM -0000, Aaron Rainbolt wrote:
> Oddly, when I got to this step, the 20.04.5 boot was indeed blocked, but
> *not* with a security violation error. My virt- manager VM with Secure
> Boot simply silently failed to boot the ISO.
ovmf doesn't print a message when this happens, it just moves on to the next
boot option (probably the shell). You can forcibly get a message by running
fs0:\efi\boot\bootx64.efi from the shell.
On real hardware with production firmware, there is no shell so the boot
stops and you see the security violation message.
On Wed, Mar 15, 2023 at 02:51:36AM -0000, Aaron Rainbolt wrote:
> Oddly, when I got to this step, the 20.04.5 boot was indeed blocked, but
> *not* with a security violation error. My virt- manager VM with Secure
> Boot simply silently failed to boot the ISO.
ovmf doesn't print a message when this happens, it just moves on to the next boot\bootx64. efi from the shell.
boot option (probably the shell). You can forcibly get a message by running
fs0:\efi\
On real hardware with production firmware, there is no shell so the boot
stops and you see the security violation message.