Heya, I couldn't get the tboot output to the serial output so instead I took some photos.
The box I've has an E820 that looks like swiss-cheese. If I boot Linux or Xen without any modification it looks as so: 0000000000000000 - 000000000009ac00 (usable) 000000000009ac00 - 00000000000a0000 (reserved) 00000000000e0000 - 0000000000100000 (reserved) 0000000000100000 - 0000000020000000 (usable) 0000000020000000 - 0000000020200000 (reserved) 0000000020200000 - 0000000040000000 (usable) 0000000040000000 - 0000000040200000 (reserved) 0000000040200000 - 00000000ba537000 (usable) 00000000ba537000 - 00000000ba540000 (ACPI data) 00000000ba540000 - 00000000ba58b000 (ACPI NVS) 00000000ba58b000 - 00000000ba593000 (usable) 00000000ba593000 - 00000000ba8c5000 (reserved) 00000000ba8c5000 - 00000000ba8c6000 (usable) 00000000ba8c6000 - 00000000ba8d6000 (reserved) 00000000ba8d6000 - 00000000ba8f5000 (ACPI NVS) 00000000ba8f5000 - 00000000ba919000 (reserved) 00000000ba919000 - 00000000ba95c000 (ACPI NVS) 00000000ba95c000 - 00000000bab7c000 (reserved) 00000000bab7c000 - 00000000bad00000 (usable) 00000000bad00000 - 00000000bb000000 (reserved) 00000000bb800000 - 00000000bfa00000 (reserved) 00000000fed1c000 - 00000000fed40000 (reserved) 00000000ff000000 - 0000000100000000 (reserved) 0000000100000000 - 000000043e600000 (usable) Or more easily visualized (skipping some of them): 0-640K RAM 1MB->512MB RAM 514MB->1GB RAM 1GB+2MB->3GB RAM when tboot loads, it marks the 514MB->3GB as reserved so Xen, Linux and the initramfs can't find within the 512MB region and the bootup fails. Here is a photo of what the original E820 looks from the tboot standpoint:http://darnok.org/tboot/tboot-e820-original-1.JPG and it decides to protect its region around 2MB: http://darnok.org/tboot/tboot-e820-preamble.JPG and the modifications: http://darnok.org/tboot/tboot-e820-2.JPG where the region from 514MB->1GB gets marked as reserved instead of RAM(1) Here is what the Xen hypervisor and Linux thing of the E820 when they start: http://darnok.org/tboot/tst018-tboot-fail.log The thing that caught my eye was the: "[ 0.000000] initrd too large to handle, disabling initrd" which definitly explained why the bootup failed to continue. Here is a bootup log without tboot: http://darnok.org/tboot/tst018-xen-ok.log for easy comparison. The sdiff between those two also points at this: http://darnok.org/tboot/normal-vs-tboot.log Any thoughts or are there some patches you might have for this? ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ tboot-devel mailing list tboot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tboot-devel
