Browse Source

Tfw forgot to complete a sentence xdxd

Wazakindjes 1 year ago
parent
commit
fca4b37180
1 changed files with 2 additions and 2 deletions
  1. 2 2
      qemu/fix_uefi_shell_boot.md

+ 2 - 2
qemu/fix_uefi_shell_boot.md

@@ -1,12 +1,12 @@
 # fix\_uefi\_shell\_boot
-__Note:__ I usually rock Debian wherever I can, so this """article""" is based off that shit. ;]
+__Note:__ I usually rock Debian wherever I can, so this """article""" is based off that shit. ;] It might work for other distros but some steps will pr0lly be different.
 
 # pr0blelm?
 A UEFI-based VM drops into UEFI shell instead of booting normally from disk. Even trying to force it to boot by manually specifying a boot option or changing the boot options within QEMU don't seem to work. ISOs can be booted just fine however. In my case this shit happened after messing with (restoring) snapshots to test a backup routine (kek).
 
 * Go to `Boot Maintenance Manager` > `Boot Options` > `Add Boot Option`
 * First select the device your OS resides on, in my case there's only one and it matches the virtual disk
-* Then browse to `EFI` > `debian` and pick `shimx64.efi`, of course the `debian` directory will be different if you're
+* Then browse to `EFI` > `debian` and pick `shimx64.efi`, of course the `debian` directory will be different if you're on a different OS
 * For the description libvirt always uses `debian` on my end (for other VMs), but it prolly should match the name of the directory where `shimx64.efi` resides
 * `Commit Changes and Exit`
 * It should drop you back at the `Boot Options` screen, from here go to `Change Boot Order`