From: Daniel De Graaf <dgdegra@tycho.nsa.gov>
To: quan.xu@aliyun.com
Cc: xen-devel@lists.xensource.com, "quan.xu" <quan.xu@intel.com>
Subject: Re: some problem with XSM enable
Date: Tue, 04 Jun 2013 10:12:20 -0400 [thread overview]
Message-ID: <51ADF5C4.501@tycho.nsa.gov> (raw)
In-Reply-To: <2e1ce839-b29c-462f-9a1b-fc40fdc161fa@aliyun.com>
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
next prev parent reply other threads:[~2013-06-04 14:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-04 3:32 some problem with XSM enable quan.xu
2013-06-04 14:12 ` Daniel De Graaf [this message]
2013-06-05 9:05 ` Xu, Quan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51ADF5C4.501@tycho.nsa.gov \
--to=dgdegra@tycho.nsa.gov \
--cc=quan.xu@aliyun.com \
--cc=quan.xu@intel.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.