Tuesday 4 October 2022

New Linux VHD\VDI video

I have added a new YouTube video to demo how to make VHDs or VDIs containing fully installed Linux OS's and boot to them from E2B\agFM\Ventoy.

You can also boot to the .VTOY file using your own grub2/grub4dos/rEFInd menu system - see the vdiskchain github project for details.

You can add "VTOY_LINUX_REMOUNT=1" as a kernel parameter to add to the boot parameters. 

I have also updated the 'Getting started with Ventoy' eBook to include a chapter and Exercise on how to make a .vtoy Linux file and how to add the VTOY_LINUX_REMOUNT=1 into the grub.cfg  of the Linux VHD\VDI permanently.

The latest 2.16 Beta of E2B supports .VTOY files. The current latest agFM also supports .VTOY files (as well as the current 'Ventoy for Easy2Boot' 1.0.79).

Beaware of this VentoyPlugson issue!

I have noticed a problem with tab pages in Ventoy's VentoyPlugson web-based app.

Basically, there is no indication of whether or nor a 'mode' section exists in the ventoy.json file.

This is important because if for instance a 'control_uefi' section exists within the ventoy.json file AND YOU UEFI-BOOT then the settings in the first tab page named 'control' will be ignored and only the settings in the 'control_uefi' page will be used. However, if there is NO 'control_uefi' key defined in the ventoy.json file then the settings in the 'control_uefi' tab will be ignored and the settings in the 'control' tab page will be used.

The problem is the web application does not indicate whether a 'control_mode' section exists or not - so it is not clear which tab page will be used by Ventoy!

I discovered this when I found that the VTOY_LINUX_REMOUNT setting did not appear to work in legacy mode but did work in UEFI64 mode. It turned out my ventoy.json file had these settings:

        { "VTOY_WIN11_BYPASS_CHECK": "1" },
        { "VTOY_LINUX_REMOUNT": "1" }
        { "VTOY_DEFAULT_MENU_MODE": "1" }

This means that when I legacy booted, the VTOY_LINUX_REMOUNT setting did NOT take effect because Ventoy used the settings in the 'control_legacy' section and ignored the settings in the 'control' section.

No comments:

Post a Comment