[Xen-devel] [rumpuserxen test] 50328: regressions - FAIL

flight 50328 rumpuserxen real [real] http://logs.test-lab.xenproject.org/osstest/logs/50328/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-i386-rumpuserxen5 rumpuserxen-build fail REGR. vs. 33866 build-amd64-rumpuserx

[Xen-devel] [libvirt test] 50325: tolerable FAIL - PUSHED

flight 50325 libvirt real [real] http://logs.test-lab.xenproject.org/osstest/logs/50325/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-amd64-i386-libvirt-xsm 9 guest-start fail never pass test-amd64-amd64-libvirt-xsm 9 guest-start

[Xen-devel] [qemu-upstream-4.4-testing test] 50323: tolerable FAIL - PUSHED

flight 50323 qemu-upstream-4.4-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/50323/ Failures :-/ but no regressions. Tests which are failing intermittently (not blocking): test-amd64-i386-freebsd10-i386 14 guest-localmigrate/x10fail pass in 50306 test-amd64-i386-freeb

[Xen-devel] [ovmf test] 50324: regressions - trouble: blocked/broken/fail/pass

flight 50324 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/50324/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-i3865 xen-build fail REGR. vs. 36764 build-amd64-xsm

[Xen-devel] [xen-unstable test] 50322: regressions - trouble: broken/fail/pass

flight 50322 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/50322/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-freebsd10-i386 11 guest-localmigrate fail REGR. vs. 36514 test-amd64-i386-free

[Xen-devel] [linux-next test] 50321: regressions - FAIL

flight 50321 linux-next real [real] http://logs.test-lab.xenproject.org/osstest/logs/50321/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-qemuu-debianhvm-amd64-xsm 5 xen-boot fail REGR. vs. 50276 test-amd64-i386-xl-win

[Xen-devel] [qemu-mainline test] 50320: regressions - FAIL

flight 50320 qemu-mainline real [real] http://logs.test-lab.xenproject.org/osstest/logs/50320/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-freebsd10-amd64 11 guest-localmigrate fail REGR. vs. 36709 test-amd64-i386-fre

[Xen-devel] [PATCH 1/2] vtpm: deep quote flags

Currently, the flags are not interpreted by vTPM. They are just packed and sent to vtpmmgr. The new implementation is backward compatible, if it receives a request without flags, it continues the request to vtpmmgr with extraInfoFlags=0. Signed-off-by: Emil Condrea --- stubdom/Makefile

[Xen-devel] [PATCH 0/2] vtpm deep quote in locality 0

Right now, deep quote functionality is enabled just when vtpm manager is started with locality=2. This requirement is enforced by the current implementation which uses PCRs that can be reset in locality 2: 20,21,22,23. Since some TPM chips do not enable access to other locality than 0 this patch e

[Xen-devel] [PATCH 2/2] vtpmmgr: execute deep quote in locality 0

Enables deep quote execution for vtpmmgr which can not be started using locality 2. The VTPM_ORD_GET_QUOTE command is backwards compatible. When receives flags=0 from vTPM it extends additional information into the PCRs as it did before. Flags are interpreted as a bitmask of: * VTPM_QUOTE_FLAGS_HA

[Xen-devel] [linux-3.16 test] 50319: regressions - FAIL

flight 50319 linux-3.16 real [real] http://logs.test-lab.xenproject.org/osstest/logs/50319/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-credit2 15 guest-localmigrate/x10fail REGR. vs. 34167 Tests which are failin