[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Xen-devel] Xen 3.0.5 Second Release Candidate
I've updated and re-assigned the bug back to Jan, but for those who are
interested and don't monitor Bugzilla:
I wasn't able to reproduce this with the -unstable tip. As a BKM for
working with the vTPM system, one should always delete the
/var/vtpm/VTPM and /var/tpm/tpm_emulator-* files before starting any new
tests or debugging a failure. If using the hardware TPM, then you might
also want to clear it so that the vtpm_manager can take ownership (it
works without this, but it guarantees that the SRK auth matches what the
That said, I did find a bug with failure to initialize a variable, and
I'll bundle that fix in with the 1.1b fix (shortly).
Cihula, Joseph <> scribbled on Monday, April 23, 2007 9:36 AM:
> Keir Fraser <> scribbled on Monday, April 23, 2007 2:55 AM:
>> This is a bug for either Vinnie Scarlata or Stefan Berger to look
>> into, I think. That code hasn't been touched in quite a while, so I'm
>> not even sure it's being actively maintained any more (in which case
>> we'll remove it).
> I've taken over vTPM maintainership from Vinnie and will have a look
> at this today. Please cc me on any future vTPM bugs or questions.
> P.S. It would be nice if the Bugzilla had a sub-component field that
> could be used for finer-grained reporting (and also email
> notification) of bugs.
>> Thanks for the bug report!
>> -- Keir
>> On 23/4/07 10:43, "Jan Peter Stotz"
>> <Jan-Peter.Stotz@xxxxxxxxxxxxxxxxx> wrote:
>>> Keir Fraser schrieb:
>>>> Well, that didn't take long! This candidate fixes a regression
>>>> which causes 32-bit x86 builds not to work out of the box (Xen is
>>>> built for PAE, but the Linux kernels are not). Also includes Tim
>>>> Deegan's fix for SDL HVM save/restore.
>>> I found a bug in the tools part of xen: The vtpm_manager fails to
>>> establish a correct connection to the tpm_emulator (activated
>>> DDUMMY_TPM flag). In xen-3.0.4-1 it works but not in the release
>>> candidates of xen-3.0.5
>>> See bug ID 966:
>> Xen-devel mailing list
> Xen-devel mailing list
Xen-devel mailing list