From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel De Graaf Subject: Re: some problem with XSM enable Date: Tue, 04 Jun 2013 10:12:20 -0400 Message-ID: <51ADF5C4.501@tycho.nsa.gov> References: <2e1ce839-b29c-462f-9a1b-fc40fdc161fa@aliyun.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <2e1ce839-b29c-462f-9a1b-fc40fdc161fa@aliyun.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: quan.xu@aliyun.com Cc: xen-devel@lists.xensource.com, "quan.xu" List-Id: xen-devel@lists.xenproject.org On 06/03/2013 11:32 PM, quan.xu@aliyun.com wrote: > > hi community > when I want to enable XSM for vtpm, there are some problems in xen boot up. > Xen version xen-4.3.0-rc2, dom0 is linux-3.7.10 without tpm drivers. I configure xen-source-tree/Config.mk > > XSM_ENABLE ?= y > FLASK_ENABLE ?= $(XSM_ENABLE) > > And make dist, make install > Then I make the policy in xen-source-tree: make -C tools/flask/policy > > When XSM is enabled, the xen boot-up stops at a lot of hex printout: This looks like a crash, in which case the interesting parts would be above the hex - which you didn't copy very accurately. If possible, using a serial console will be helpful in getting the text without needing to retype output. The most important part is the value of RIP and the backtrace (if one is present); log messages leading up to the crash may also be useful. >>>>> > Fff82*********** Fff82*********** Fff82*********** > ~ ~ ~ ~ ~~ ~~ ~ ~ ~ ~ ~ ~ ~ ~~~~~~ ~~~~~~~~~~~~~ ~ > 000000000000000 000000000000000 0000000000000000 > 000000000000000 0000000000fff000 0000000000000000 > <<<< > I make sure if "XSM_ENABLE ?= n and FLASK_ENABLE ?= $(XSM_ENABLE)", the xen can work properly. > > Thanks > > Quan Xu > xen-users dropped to BCC -- Daniel De Graaf National Security Agency