Hello,
On Qubes OS 3.2rc2, a tboot-based boot sequence will fail with a system reset unless the 'min_ram=0x2000000' parameter is specified in grub. See Qubes issue #2155: https://github.com/QubesOS/qubes-issues/issues/2155 Currently, Qubes uses tboot version 1.8.2 from the Fedora 23 repository. The other relevant components are Linux kernel 4.4.14 and Xen 4.6.1. If Linux is downgraded to 4.2 then the system is able to boot without crashing. This parameter would normally be used to rectify a milder condition where the system boots with less memory available than it should. Using it to avoid a catastrophic crash does not seem right, so I'd like to ask what is the best course of action from the tboot devs: Is this a bug in tboot or Linux? Should Qubes devs consider using 'min_ram' for all tboot installations? Would it be worth the trouble to try upgrading tboot to the current version? And if so, are signatures available for the tboot code? Chris ------------------------------------------------------------------------------ _______________________________________________ tboot-devel mailing list tboot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tboot-devel
