cprise wrote on 2014-04-01: > When booting via the Qubes OS anti-evil maid process, which relies on > tboot, I have nearly 3GB less total RAM available to the system > according to xen 'xl info' command. (See discussion in this thread after > March 30: > https://groups.google.com/forum/#!topic/qubes-devel/EBc4to5IBdg ). > > Synopsis it that it doesn't matter whether or not the 'antievilmaid' > module is activated: Simply booting into Xen via tboot results in only > 5GB available instead of the full 8GB. Removing tboot.gz from boot > process results in full RAM (actually 7884MB) availability. > > The system is a Thinkpad T430s i5-3320M / QM77 chipset with VT-d enabled > in the BIOS (which has been updated to the latest). Qubes version is R2 > beta 3 using tboot 1.7.3-3-fc18, Xen 4.1.6.1 and Linux 3.7.4 or 3.11.10.
Can you help running txt-stat and sending out the result? And/Or, send out the output of "xl dmesg". Meanwhile, you may have a try to add below option in the grub.cfg for tboot.gz line: min_ram=0x2000000 The RAM missing is caused by some MMIO region allocated by the BIOS which is near 1G edge. This option may help pulling the missing RAM back, but whether the kernel booting can still work will depends on what device that MMIO are allocated for. Usually it is allocated for igfx, then this option may help. Thanks Jimmy
smime.p7s
Description: S/MIME cryptographic signature
------------------------------------------------------------------------------
_______________________________________________ tboot-devel mailing list tboot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tboot-devel
