Bug 11913 - musl image launch with runqemu did not reach the login banner
Summary: musl image launch with runqemu did not reach the login banner
Status: RESOLVED FIXED
Alias: None
Product: Runtime Testing
Classification: QA/Testing
Component: general (show other bugs)
Version: 2.4
Hardware: x86 Multiple
: High normal
Target Milestone: 2.4 M3
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2017-08-08 21:31 UTC by Leonardo Sandoval Gonzalez
Modified: 2017-08-14 22:56 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
log comming from [1] (101.54 KB, application/octet-stream)
2017-08-08 21:31 UTC, Leonardo Sandoval Gonzalez 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Leonardo Sandoval Gonzalez 2017-08-08 21:31:41 UTC 
Created attachment 3926 [details]
log comming from [1]

AB build [1] indicates that once the musl image was build and launched through runqemu, but the login banner was not reached. Apparently the issue is the following, leading to a timeout on the host following a sigterm to the runqemu process.

    runqemu - ERROR - Acquiring lockfile /tmp/qemu-tap-locks/tap0.lock failed: [Errno 11] Resource temporarily unavailable

[1] https://autobuilder.yocto.io/builders/nightly-musl/builds/391
Comment 1 Leonardo Sandoval Gonzalez 2017-08-08 22:03:09 UTC 
Just realized that this is ross/mut so it may be invalid. Leaving as it is, so decision on its status is done at triage
Comment 2 Leonardo Sandoval Gonzalez 2017-08-10 20:16:18 UTC 
Another musl build with similar symptoms

[1] https://autobuilder.yocto.io/builders/nightly-musl/builds/392/steps/Running%20Sanity%20Tests/logs/stdio