This is a clarification request about the "one shot - next boot entry" select feature - the ability to select (preferably using a terminal command), the next boot entry in the same way as systemd e.g. command from arch wiki: systemctl reboot --boot-loader-entry=arch-custom.conf
This feature is essential to me primarily for launching VFIO VMs. In systemd, I have multiple loader entries for same kernel with different sets of kernel parameters like hugepages 1G , binding devices to VFIO-PCI , and even isolcpus. So for e.g. I might run normal linux system with default kernel params, and then reboot into a single GPU passthrough VM using an alias that reboots into a boot loader entry with multiple 1G hugepages allocated, some CPU cores isolated, and Nvidia GPU device IDs bound to VFIO PCI ID etc. Then at VM shutdown, I have scripts to load back into default boot loader entry.
I know there have been requests for this feature from Limine from my search here, particularly - #601 and #531
Going through those feature requests, it is not clear if Limine has implemented this feature or not, and if yes, there is seemingly no clear documentation on how to use it.
In #601, the response is that this is not supported or planned to be supported.
However, in #531, it is said that this is implemented using "One Shot Entry Control" as per #548
In #548, it is not clear how this is implemented. I'm assuming this is using some limine.conf entry like default_entry. So I guess I could use this by putting a tee command to append the one shot entry for next boot into /boot/limine.conf and then reboot. But it is not clear what that /boot/limine.conf entry precisely is.
Could you please help clarify this.
This is a clarification request about the "one shot - next boot entry" select feature - the ability to select (preferably using a terminal command), the next boot entry in the same way as systemd e.g. command from arch wiki:
systemctl reboot --boot-loader-entry=arch-custom.confThis feature is essential to me primarily for launching VFIO VMs. In systemd, I have multiple loader entries for same kernel with different sets of kernel parameters like
hugepages 1G, binding devices to VFIO-PCI , and evenisolcpus. So for e.g. I might run normal linux system with default kernel params, and then reboot into a single GPU passthrough VM using an alias that reboots into a boot loader entry with multiple 1G hugepages allocated, some CPU cores isolated, and Nvidia GPU device IDs bound to VFIO PCI ID etc. Then at VM shutdown, I have scripts to load back into default boot loader entry.I know there have been requests for this feature from Limine from my search here, particularly - #601 and #531
Going through those feature requests, it is not clear if Limine has implemented this feature or not, and if yes, there is seemingly no clear documentation on how to use it.
In #601, the response is that this is not supported or planned to be supported.
However, in #531, it is said that this is implemented using "One Shot Entry Control" as per #548
In #548, it is not clear how this is implemented. I'm assuming this is using some
limine.confentry likedefault_entry. So I guess I could use this by putting a tee command to append the one shot entry for next boot into/boot/limine.confand then reboot. But it is not clear what that/boot/limine.confentry precisely is.Could you please help clarify this.