search for: vtpms

This patch adds a new option for xen config files for directly mapping hardware io memory into a vm. Signed-off-by: Matthew Fioravante <matthew.fioravante@jhuapl.edu> diff --git a/docs/man/xl.cfg.pod.5 b/docs/man/xl.cfg.pod.5 index 013270d..428da21 100644 --- a/docs/man/xl.cfg.pod.5 +++ b/docs/man/xl.cfg.pod.5 @@ -496,6 +496,17 @@ is given in hexadecimal and may either a span e.g.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, 4.2 and 4.1 suffers from SEGV during xl network-attach in libxl__device_nic_add. In 4.3-unstable it is fixed by: 5420f2650 libxl: Set vfb and vkb devid if not done so by the caller So either the patch need to be backported to 4.1 and 4.2, or fixed by this one: - ------ libxl: Fix SEGV in network-attach When "device/vif" directory

...doc http://xenbits.xen.org/docs/unstable/misc/vtpm.txt I found the tpm emulator 0.7.4 and build it into centos 5.9 x64 PV vm. I have access from that VM to the TPM as well via trousers. What I cannot find is the vTPM manager that distributes vTpms to domains. Is this feature deprecated ? Nobody anywhere is talking about it. I am a little confused as there was measurement boot module supporting TXT boot released by citrix not long ago but there is no doc that can give me any info on how to/ or where from...

Hi again! Succeeded in creating vtpmmgr-stubdom.gz from the source RPM with some shortcuts. ow the next problem seems to be that the libvirt we have will not support the XEN vtpm:s For example: virsh dumpxml <vm-machine> will not contain any info on the vtpm :-( Am I really the first one around with a need for TPM support in the VM:s ?? Best Dag

...not contain any info on the vtpm :-( > > Am I really the first one around with a need for > TPM support in the VM:s ?? Almost certainly the first Virt SIG user to try it. :-) 4 years ago, I don't think any of the big enterprises contributing to Xen (Citrix, SuSE, Oracle) cared about vTPMs; only niche players like the NSA, who typically downloaded and ran things themselves. (This is probably why vTPM is disabled in RH's KVM.) This will be changing in the future, as Windows requires vTPM (version 2 in fact) for some features, so that's in the process of being implemented. I...

...9;consoles'' (''array'')) (''VIFs'' (''array'' ''OpaqueRef:ad3fb92b-4261-87c5-d94d-3c958b90dca6'')) (''VBDs'' (''array'')) (''crash_dumps'' (''array'')) (''VTPMs'' (''array'')) (''PV_bootloader'' ''/usr/bin/pygrub'') (''PV_kernel'' '''') (''PV_ramdisk'' '''') (''PV_args'' '''') (''PV_bootloader_args&...

...39;' (''array'' ''OpaqueRef:428a44bb-4056-911a-f6ba-245a216fd37d'')) (''VBDs'' (''array'' ''OpaqueRef:bde0a76d-a0e4-f656-8adf-2bb1b1c17520'')) (''crash_dumps'' (''array'')) (''VTPMs'' (''array'')) (''PV_bootloader'' ''eliloader'') (''PV_kernel'' '''') (''PV_ramdisk'' '''') (''PV_args'' ''graphical utf8'') (''PV_bootload...

..."mac": "00:16:3e:fd:44:a6", "bridge": "dsip_ext_br0", "script": "vif-bridge", "nictype": "vif_ioemu" } ], "vtpms": [ { "backend_domname": "vtpm01", "devid": 0, "uuid": "163088d1-1565-49a0-8e0b-64dfc62460bc" } ], "on_reboot": "...

Hi community, there are some problems to start vTPM vtpm-stubdom following docs/misc/vtpm.txt. When I start vtpm-stbdom, the vtpmmgr-stubdom will print out: === ERROR[VTPM]: LoadKey failure: Unrecognized uuid! 69743ae0-9d4a-4ad6-9819-e602085b6792 ERROR[VTPM]: Failed to load key ERROR in vtpmmgr_LoadHashKey at vtpm_cmd_handler.c:78 code: TPM_BAD_PARAMETER. === I start vtpmmgr-stubdom with

Hi community, there are some problems to start vTPM vtpm-stubdom following docs/misc/vtpm.txt. When I start vtpm-stbdom, the vtpmmgr-stubdom will print out: === ERROR[VTPM]: LoadKey failure: Unrecognized uuid! 69743ae0-9d4a-4ad6-9819-e602085b6792 ERROR[VTPM]: Failed to load key ERROR in vtpmmgr_LoadHashKey at vtpm_cmd_handler.c:78 code: TPM_BAD_PARAMETER. === I start vtpmmgr-stubdom with

...-p1 < ../$(VTPM_PATCH); \ + mkdir build; cd build; cmake -DCMAKE_INSTALL_PREFIX=${PREFIX} .. + touch $@ .PHONY: build_sub -build_sub: $(VTPM_DIR)/tpmd/tpmd - set -e; if [ -e $(GMP_HEADER) ]; then \ - $(MAKE) -C $(VTPM_DIR); \ - else \ - echo "=== Unable to build VTPMs. libgmp could not be found."; \ - fi - +build_sub: $(VTPM_DIR)/build + set -e; \ + cd $<; $(MAKE) tpmd diff --git a/tools/vtpm/Rules.mk b/tools/vtpm/Rules.mk --- a/tools/vtpm/Rules.mk +++ /dev/null @@ -1,26 +0,0 @@ -# Base definitions and rules (XEN_ROOT must be defined in includin...

Hi, I‘m trying to install vTPM based on Xen-4.2.2, linux-kernel 3.9.1 (Dom0) and TPM emulator. However, I cannot find the TPM backed driver in this version of Dom0 linux kernel. There is no CONFIG_XEN_TPMDEV_BACKEND in the kernel config file. The config file for Dom0 is attached. Maybe it provides some useful information. So, how to install a Xen TPM backend driver in the Dom0 linux-kernel.

Hi Folks: I am having trouble creating a Fedora 14 domU on a XCP 1.0 dom0 hypervisor and am hoping that someone can help me figure out what I am doing wrong. Here is what I did (per the user''s guide and reference manual): ## Step 1. Create the VM: # uuid=$(xe vm-install template=''Other install media'' new-name-label=''test'') ## Note: I also tried

This adds a backend_domname field in libxl devices that contain a backend_domid field, allowing either a domid or a domain name to be specified in the configuration structures. The domain name is resolved into a domain ID in the _setdefault function when adding the device. This change allows the backend of the block devices to be specified (which previously required passing the libxl_ctx down

Since the vTPM implementations are being incorproated into Xen and possibly upstream Linux, I would like to see if this protocol change could be added before we have significant legacy implementations. If not, I still think it would be useful as either a v2 or negotiated protocol change. The current vTPM protocol is a copy of the network protocol. This was likely done for ease of implementation,

...nterface and the new interface. Automatic vTPM shutdown is removed by patch #9; however, since patch #8 makes it safe to destroy the vTPM at any point, the cleanup of a vTPM upon guest shutdown can be relocated to the layer that starts the vTPM. This is necessary even without these patches because vTPMs have never automatically shut down if a guest encoutners an error in early boot or simply does not load (or have) the frontend driver. Locality-5 PCRs have been dropped since v4: this patch is not really suited for upstreaming until there is a domain using the extra PCRs. Mini-os driver patches:...

A character device for accessing (in user-space) pages that have been granted by other domains. Signed-off-by: Derek Murray <Derek.Murray@cl.cam.ac.uk> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel