Bug 11913

Summary: musl image launch with runqemu did not reach the login banner
Product: [QA/Testing] Runtime Testing Reporter: Leonardo Sandoval Gonzalez <leonardo.sandoval.gonzalez>
Component: generalAssignee: Richard Purdie <richard.purdie>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: High CC: randy.macleod
Version: 2.4   
Target Milestone: 2.4 M3   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
log comming from [1] none

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