Hal My fault, since you have no chance to run into Xen or kernel. I suspect it is the BIOS issue.
I am not sure whether it is convenient for you to downgrade the BIOS and have a try. Shane Hal Finney wrote: > Hi Shane - I'm not sure what it would do to add these switches, since > tboot doesn't get as far as launching the kernel, since it hangs in > SENTER. However I can try doing it and then just booting into the > kernel, in case I get any error reports about VT-d. > > Are there any MSRs or other registers I can patch tboot to dump out, > to indicate whether VT-d is turned on? > > My HP dc7800 was one of the very first commercially released systems > to support TXT. I bought one as soon as they became available in order > to experiment with this technology. It has an E6550 "Conroe" processor > with a Q35 "Bearlake" chipset. > > Hal > > On Thu, Jul 30, 2009 at 12:24 AM, Shane Wang<shane.w...@intel.com> wrote: >> Hal, >> >> If you work with Xen, please try to add "iommu=1 vtd=1" in Xen command line >> (i.e. the end of "module /boot/xen.gz ...") >> If you work with Linux, please try to add "iommu=on" in the command >> line (i.e. the end of "module /boot/vmlinuz-2.6.30 ..." >> >> PS: do you know which platform HP dc7800 is? *Field or *Dale? >> Can you see VTd lsoc (Azalia) WA in BIOS or somewhere? >> >> Thanks. >> Shane >> >> Hal Finney wrote: >>> Thanks for the reply, Shane. VT-d is enabled in the BIOS; in fact, the >>> BIOS automatically enables VT-d when TXT is enabled. >>> >>> I don't know of anything I would do in any grub configuration file to >>> enable VT-d for tboot and SINIT. Do you have any suggestions? >>> >>> Hal >>> >>> On Wed, Jul 29, 2009 at 10:04 PM, Shane Wang<shane.w...@intel.com> wrote: >>>> Hi Hal >>>> >>>> The error code means VTd is disabled. >>>> Is your VT-d enabled in your new BIOS and grub.conf? >>>> >>>> Thanks. >>>> Shane >>>> >>>> Hal Finney wrote: >>>>> I haven't run tboot in a while, but I'm trying it on my HP dc7800 and >>>>> finding it hangs in GETSEC[SENTER]. This is even true with old >>>>> versions of tboot that used to work. My system has no USB ports >>>>> plugged in, and no hardware changes. >>>>> >>>>> The one change is I recently updated my BIOS. I suspect this has to be >>>>> the cause. One nice thing about the new BIOS is that the tboot hang >>>>> actually reboots the machine with the ERRORCODE register intact. Its >>>>> value is c00020a1. This is progress code 0ah, error code 1000, >>>>> meaning: "device scope of VT-d DMAR ACPI table is invalid". Not clear >>>>> what this means. >>>>> >>>>> My log is attached, including the hang and the relaunch of tboot. This >>>>> is version 20090330 of tboot. Thanks very much - >>>>> >>>>> Hal Finney >> ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ tboot-devel mailing list tboot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tboot-devel
