|
|
|
|
|
|
|
|
|
|
xense-devel
RE: [Xense-devel] Vtpm_manager getting TPM_NOSPACE
Yes, on a sigkill the manager does clean up after itself. When did you
get the TPM_NOSPACE error? Were you running the manager or some other
TPM application before running the manager and getting this error? On
every power cycle, the TPM unloads all it's keys and authorization
sessions automatically.
So if you get this error on a fresh boot, the TPM is not properly
flushing, which is a security issue that they need to fix. If you ran
the vtpm manager, shut it down, and started it again and got this
problem, then you've found a bug in the manager showing that it's not
cleaning up fully. If you ran something else and then the manager, then
that something else isn't properly cleaning up.
-Vinnie Scarlata
-----Original Message-----
From: xense-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xense-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Osborn,
Justin D.
Sent: Wednesday, December 06, 2006 6:09 AM
To: xense-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xense-devel] Vtpm_manager getting TPM_NOSPACE
Hi all,
I've been working on a project for a while that uses xen and the
vtpm. We have a DomU configured to use a vtpm instance. When I brought
up the box this morning, vtpm_manager failed to start, giving me an
error that it received TPM_NOSPACE when trying to load a key. Is this a
bug?
I usually shut the machine down with /sbin/halt or /sbin/reboot, which
just kills vtpm_managerd. I assume vtpm_managerd is supposed to clean
up after itself. So is there a certain way I should kill vtpm_managerd?
Or is this a bug?
Thanks,
Ozzie
--
Justin D. Osborn
Software Engineer
Information Operations
JHU/APL
_______________________________________________
Xense-devel mailing list
Xense-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xense-devel
_______________________________________________
Xense-devel mailing list
Xense-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xense-devel
|
|
|
|
|