| Summary: | QA: Validate QEMU as a supported platform in Refkit | ||
|---|---|---|---|
| Product: | [QA/Testing] IoT Reference OS Kit Testing | Reporter: | Jair Gonzalez <jair.de.jesus.gonzalez.plascencia> |
| Component: | intel-iot-refkit-automated-build-testing | Assignee: | Humberto Ibarra <humberto.ibarra.lopez> |
| Status: | RESOLVED INVALID | QA Contact: | Jair Gonzalez <jair.de.jesus.gonzalez.plascencia> |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | dmitry.rojkov |
| Version: | 2.3 | ||
| Target Milestone: | 2.3 M4 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
| Bug Depends on: | 11068 | ||
| Bug Blocks: | |||
|
Description
Jair Gonzalez
2017-03-21 23:11:01 UTC
I see this bug blocks now the bug 11068. Jair, I guess that all prerequisites have already made their way to the master branch of Refkit. Basically the tests should do > bitbake refkit-image-common > bitbake ovmf > runqemu ovmf refkit-image-common wic slirp nographic serial Then in a separate shell run > ssh root@localhost -p 2222 Alternatively the "slirp" option could be omitted, then runqemu would use a TAP interface. But this approach requires root permissions and a properly configured DHCP-server listening on the temporary TAP interface. Added PR 114 to the refkit github 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. No more tests are planned for this at the moment aside from the ones already considered by the development team. Closing this for now. |