Bug 11201 - QA: Validate testing TPM(v1.2) support on QEMU has been enabled
Summary: QA: Validate testing TPM(v1.2) support on QEMU has been enabled
Status: RESOLVED INVALID
Alias: None
Product: IoT Reference OS Kit Testing
Classification: QA/Testing
Component: intel-iot-refkit-automated-runtime-testing (show other bugs)
Version: 2.3
Hardware: x86 Multiple
: Medium enhancement
Target Milestone: 2.3 M4
Assignee: Humberto Ibarra
QA Contact: Jair Gonzalez
URL:
Whiteboard:
Depends on: 11080
Blocks:
  Show dependency tree
 
Reported: 2017-03-21 22:54 UTC by Jair Gonzalez
Modified: 2017-05-23 22:04 UTC (History)
1 user (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jair Gonzalez 2017-03-21 22:54:27 UTC
Using swtpm with qemu currently depends on starting swtpm as root before each runqemu invocation. This is incompatible with the "no root" requirement for automated testing. A solution is being developed to connect qemu to swtpm through a unix domain datagram socket so no root rights are needed.

The purpose of this item is to track the development of a test suite to validate the following conditions are met on the qemu to swtpm connection:

- Read/write can work correctly.
- ioctls could be mapped to out-of-band messages.
- If the unix domain socket pair is created by qemu and passed to swtpm as stdin/out, then it is guaranteed that swtpm stops when qemu gets killed.
Comment 1 Jair Gonzalez 2017-04-17 21:28:13 UTC
After an agreement with the Refkit team, the progress on the minimal required sanity tests to release a feature will be tracked on the same bug issue used to track the feature's development. Analogous QA bugs like this one may be created if required, and will be used to track the development of more extensive test cases.

According to this, the dependence will be inverted in relation to the feature bug.
Comment 2 Humberto Ibarra 2017-05-23 22:04:18 UTC
No more tests for this are considered at the moment aside of the core ones which already being described as part of a different bug. Closing for now.