I just wrote Ventoy to my megastick, wrote FreeBSD and Debian Install images, and it works. Debian Bullseye install image complains about low-memory mode, but the booted machine had >500MB still available. Abstraction breaks somewhere, I would love to know why/how.
Without diving into the source code. :) Has anyone seen architecture/design documents on how it actually mounts the ISO file and "boots" from it? What does prevent "the other 10%" from not working?
I looked through the docs, found these so far:
Memdisk[1] section mentions:
> In normal mode, Ventoy will only read the iso file at booting time, and only read the content needed for boot.
Ventoy Compatible?[2] mentions a hook. What does this mean?
> Once Ventoy treats the iso file as Ventoy Compatible, it will just make the virtual disk and will not do the hook.
Without diving into the source code. :) Has anyone seen architecture/design documents on how it actually mounts the ISO file and "boots" from it? What does prevent "the other 10%" from not working?
I looked through the docs, found these so far:
Memdisk[1] section mentions:
> In normal mode, Ventoy will only read the iso file at booting time, and only read the content needed for boot.
Ventoy Compatible?[2] mentions a hook. What does this mean?
> Once Ventoy treats the iso file as Ventoy Compatible, it will just make the virtual disk and will not do the hook.
[1]: https://www.ventoy.net/en/doc_memdisk.html
[2]: https://www.ventoy.net/en/doc_compatible_mark.html