Kali-Linux does not support UEFI install?

[CaffeineAddict]

I've read Kali manuals regarding whether to install in BIOS or UEFI mode here:

Installing Kali Linux | Kali Linux Documentation

Installing Kali Linux (single boot) on your computer is an easy process. This guide will cover the basic install (which can be done on bare metal or guest VM), with the option of encrypting the partition. At times, you may have sensitive data you would prefer to encrypt using Full Disk...

www.kali.org

• Ensure that your computer is set to boot from CD/DVD/USB in your BIOS/UEFI.
• In the UEFI settings, ensure that Secure Boot is disabled. The Kali Linux kernel is not signed and will not be recognized by Secure Boot.

I'm installing in QEMU where I'm presented options to choose BIOS/UEFI or UEFI with secure boot.
BIOS works, UEFI does not work regardless if I choose with or without secure boot.

Why does UEFI install not work?

I get error that bootable media is not found (where bootable media is ISO file from which to install)

 

[dos2unix]

This looks like Qemu/KVM, I sometimes have to change the chipset to i440FX.

@f33dm3bits

Change the chipset to

 

[gvisoc]

For your bootable media to be found in EFI mode, its partition table must be GPT --it won't work with MBR.

 

[dos2unix]

For your bootable media to be found in EFI mode, its partition table must be GPT --it won't work with MBR.

That doesn't seem right. Sometimes, it's just whatever the iso is, and you don't have a choice.

 

[gvisoc]

@dos2unix those modes apply to the way we format the bootable media before burning the ISO, not to the ISO itself --see Rufus' options "partition scheme" and "target system" (for the lack of a better place to check there's a screenshot right at https://rufus.ie/en/)

 

[dos2unix]

I suppose that may be true in Rufus. But not in dd, etcher, or media-creator. They don't give you an option.
Whatever partition type the iso has, is what gets burned to the USB. It over-writes any existing partition table.

Not only that, I usually resizes my partition table. My 8GB USB drive, becomes a 2.5GB disk drive for example.

 

[gvisoc]

I suppose that may be true in Rufus. But not in dd, etcher, or media-creator. They don't give you an option.
Whatever partition type the iso has, is what gets burned to the USB. It over-writes any existing partition table.

It is about the partition table, not the partitions themselves. Those tools won't do, because they expect the partition table to exist already. With those, you have to prepare the USB beforehand yourself with other tools for partition creation. See for example the KDE Partition Manager, when selecting "New Partition Table":

 

[dos2unix]

With those, you have to prepare the USB beforehand yourself with other tools for partition creation:

I never do.

 

[gvisoc]

I never do.

You do, but you don't realise. Most of the time the factory default, or the tool's default, just works.

I was only pointing out that an MBR partition table won't boot on an EFI machine.

 

[dos2unix]

You do, but you don't realise. Most of the time the factory default, or the tool's default, just works.

99.99% of the USB drives I buy are mbr/dos exfat/fat32 drives. I don't change them to gpt before burning an iso image to them.
In this case i recognize the "Tiano Core" logo in the first picture in the OP. He is not using a USB drive at all. This is a Qemu/KVM VM running from a downloaded iso on their hard drive.

 

[CaffeineAddict]

This looks like Qemu/KVM, I sometimes have to change the chipset to i440FX.

This doesn't seem to work, unless I'm missing something:

Note that I don't set BIOS option below but UEFI which is having this problem, BIOS option works fine.

 

[CaffeineAddict]

@gvisoc
I'm installing in QEMU using ISO, there is no way to change partition table of target virtual disk prior booting the ISO which does not work.

Booting ISO doesn't work, and that's the first step before install to virtual disk.

 

[dos2unix]

This doesn't seem to work, unless I'm missing something:

I've never gotten it to work, when I change the existing, I usually have to start new from scratch.

 

[CaffeineAddict]

I've never gotten it to work, when I change the existing, I usually have to start new from scratch.

I'll just stick to BIOS setting for now. it's VM so not a big deal, but Kali-Docs are not complete regarding QEMU:

Kali inside QEMU/LibVirt with virt-manager (Guest VM) | Kali Linux Documentation

We understand there are a lot of options for interfacing with KVM and QEMU to create different VMs, however for the purposes of this guide we will be using the most common option. To get a Debian based system prepared for this, we can simply run the following command: kali@kali:~$ sudo apt...

www.kali.org

It doesn't cover "customize install" checkbox.
Default setup from docs uses BIOS.