Yes, I try to enable vTPM in Xen-4.3-unstable. There are some difference between xen 4.3 and previous version. in Xen 4.3 we’ll be moving to a
“stubdomain-only” model, unifying the vtpm system and making it much more secure.
How to deal with migration is an interesting and necessary topic for vTPM. BTW my team will try to enable below 3 topics:
1. enable xen vTPM to allow programs to interact with a TPM in a virtual machine, the same way they interact with a
TPM on the physical system.
2. intergrate xen vTPM in openstack cloud. virtual machine in OpenStack can work with Xen vTPM.
3. promote TPM 2.0 in Xen. Xen vTPM can run on TPM 2.0.
What about trying to enable vTPM together first.
In Xen release note wiki (http://wiki.xen.org/wiki/Xen_4.3_Release_Notes), it noted
‘qemu-upstream is now the default for VMs not using stub domains. You can change this by adding device_model_version = "qemu-xen-traditional" to your config file.’
Maybe it is a good approach to make it work. I will try it this afternoon.
BTW:
XSM should enable first.
Thanks
Quan Xu
From: Bei Guan [mailto:gbtju85@xxxxxxxxx]
Sent: Wednesday, June 26, 2013 2:12 PM
To: Xu, Quan
Cc: xen-devel
Subject: Re: [Xen-devel] How to make xl support the old version of vTPM tools
Do you use the new version of vTPM, which uses the vtpm-stubdom？ I failed to make it work in my computer before. Moreover, it doesn't support the VM migration now. So, I just port the old version
vTPM (got it from the Xen-3.4.2/tools/) to the Xen-4.3-unstable. It doesn't use the vtpm-stubdom.
2013/6/26 Xu, Quan <quan.xu@xxxxxxxxx>
Hi, Guan
Could you enable vTPM now? My vTPM is always print out below error when I enable
vtpm-stubdom.
ERROR[VTPM]: LoadKey failure: Unrecognized uuid! f70b429c-c7e4-41be-948f-76991f57a3bf
ERROR[VTPM]: Failed to load key
ERROR in vtpmmgr_LoadHashKey at vtpm_cmd_handler.c:78 code: TPM_BAD_PARAMETER.
Could you share some experience? Thanks in advance.
Quan
Hi,
I'd like to use some advanced functions of vTPM, such as migration. So, I try to port the old version of vTPM tools (tools/vtpm and tools/vtpm_manager in Xen-3.4.2 )
to Xen-4.3 unstable.
Now, the vtm-manager can communicate with vtmd, but DomU cannot boot when it's configured with a vtpm option in the config file. I think maybe xl doesn't support
the old vTPM tools very well. If this is the case, can you give me some advice on how to modify the xl to support the old vTPM?
--
Best Regards,
