qralarm-android VS Ventoy

Not exactly the same but maybe QRAlarm is close enough. User must scan a QR code to dismiss the alarm. Idea is to print the QR code and place it somewhere far enough from your bed that you have to get up to go scan it.

QRAlarm: Disable alarms with a QR scanner

QRAlarm

QRAlarm: alarm clock requiring you to turn off alarms by scanning the QR Code

Ventoy is an open-source tool to create a bootable USB drive for ISO/WIM/IMG/VHD(x)/EFI files. Using Ventoy, we can create live USB for multiple distros in one flash disk. This is a revolutionary feature compared to other tools, e.g., Etcher, Rufus, etc, that can only create one live USB at a time. This tool is so important. Don't call yourself a distro hopper if you don't know this tool.

I'm thinking you mean Ventoy? They say they can load vhd and img files, though I've only tried ISO's myself.

https://www.ventoy.net/

View on GitHub

I faced it too. There is a PR on the ventoy GitHub repository that fixes Proxmox boot.

https://github.com/ventoy/Ventoy/actions/runs/7088423200

> While this works, I find this method a bit tedious to use, at least compared to Ventoy [0].

I find ventoy more tedious, because you can't use it on your hard drive with a sane partitioning scheme.

The only reason is because of how the ventoy detection hardcode the partition boundaries in its checks, and it means Ventoy can only run with the partitions set in a way that may lead to alignment issues like write-amplification: I've detailed that in https://github.com/ventoy/Ventoy/issues/1342

Ideally I'd have a 10G partition after the EFI (or it could even be the EFI itself) with a few ISOs for rescue purposes + a UEFI entry to avoid having to use a bootable USB, but that's not possible with Ventoy unless I accept Ventoy choices of partition boundaries:

                (pMBR->PartTbl[0].StartSectorId != 2048 ||