The hiperiso_boot() function and hiso_hv_mode checkpoints in grub.cfg
were defined but never reached because:
1. The deployed grub.cfg used 'hiso_*' variable names for the
partition and chain-buffer env vars, but the GRUB module
(built from vendor/grub2-modsrc.tar.xz) only reads the original
Ventoy 'vtoy_*' names. Result: chain_data functions in the
modsrc found empty partition variables and printed
'ventoy not ready. chain empty failed'.
package_release.sh now mirrors every / to the
matching / in the deployed grub.cfg, so the
modsrc's chain_data commands see the partition layout.
2. hiso_hv_mode was declared in the env-var export list at the end
of grub.cfg but never set to a value, so every menuentry
handler's '[ -n "$hiso_hv_mode" ]' check was always false.
grub.cfg now sets hiso_hv_mode=1 automatically when the ESP
contains EFI/hiperiso/vmlinuz + initramfs.cpio.gz (the payloads
are already there from build_all.sh). Sentinel
/hiperiso/no_hv_mode on the data partition disables it.
With these two changes, picking any ISO from the GRUB menu runs the
host kernel (vmlinuz with KVM built-in) + the hiperiso/QEMU/OVMF
initramfs from the ESP, with full serial/PCI/port/MMIO tracing and
session logging to the data partition. The killer feature is now
the default boot path.
vasilito
ce1e1ad677