Cloned VM stuck in UEFI Shell

Apps and Virtualization
,
1

I can successfully create a VM “vm0” from scratch and install the OS from debian-12.8.0-amd64-netinst.iso. After installation I had to remove the CDROM/isofile from devices so that the VM boots from the zvol data/vm0-gvydza and that works perfectly.

When I clone “vm0” into “vm1” zvol data/vm0-gvydza_vm1 gets created. Try to start vm1 results in getting stuck in the UEFI shell. On the Spice console:
image

OTOH, when attaching the newly cloned data/vm0-gvydza_vm1 to vm0 it works: the zvol seems ok.
Attaching the initial zvol data/vm0-gvydza to vm1 does not work either.

While the cloned zvol seems ok there must be some invisible difference between the VM configurations. From the GUI both VM configurations look identical.

This is with TrueNAS Scale ElectricEel-24.10.1 . I had the same result with 24.10.0.2 . Same result with disk Types AHCI and VirtIO.
I just noticed when creating another VM from scratch and reusing a preexisting zvol does not work either.
When choosing Legacy BIOS as boot method then VM cloning works. I can stick to BIOS, but should I?

Any hints?

2

Type “FS0:”, then in there you can tab complete “efi\boot\filename.efi”, filename being something like bootx64.efi. Hit enter and it should start up. Once in the OS, I’m assuming it’s linux, run install-grub /dev/sda if sda is your primary disk and using grub.

If that’s windows it’s basically the same to boot, just different paths to the .efi file and I think a different .efi filename, and you’d have to look up how to repair hte windows boot environment.