Bug 11952

Summary: runqemu - ERROR - Acquiring lockfile /tmp/qemu-tap-locks/tap0.lock failed: [Errno 11] Resource temporarily unavailable
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Juro Bystricky <juro.bystricky>
Component: Scripts and ToolsAssignee: Richard Purdie <richard.purdie>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Medium+ CC: joshuagloe, ross.burton
Version: 2.4   
Target Milestone: 2.4 M4   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Juro Bystricky 2017-08-18 16:51:25 UTC 
As seen in Autobuilder:
https://autobuilder.yocto.io/builders/nightly-ppc-lsb/builds/421/steps/Running%20Sanity%20Tests/logs/stdio

ERROR: core-image-lsb-1.0-r0 do_testimage: Didn't receive a console connection from qemu. Here is the qemu command line used:
tmp/work/x86_64-linux/qemu-helper-native/1.0-r1/recipe-sysroot-native/usr/bin//qemu-system-ppc-devicevirtio-net-pci,netdev=net0,mac=52:54:00:12:34:04-netdevtap,id=net0,ifname=tap1,script=no,downscript=no-drivefile=/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-ppc-lsb/build/build/tmp/deploy/images/qemuppc/core-image-lsb-qemuppc.ext4,if=virtio,format=raw-show-cursor-usb-usbdevicetablet-devicevirtio-rng-pci-serialtcp:127.0.0.1:46580-machinemac99-cpuG4-m256-serialtcp:127.0.0.1:47257-snapshot-kerneltmp/deploy/images/qemuppc/vmlinux--4.1.42+git0+9f9c9a66ef_1e29490acc-r0.2-qemuppc-20170817003236.bin-appendroot=/dev/vda rw highres=off  mem=256M ip=192.168.7.4::192.168.7.3:255.255.255.0 console=tty console=ttyS0 console=tty1 console=ttyS0,115200n8 printk.time=1
and output from runqemu:
runqemu - INFO - Continuing with the following parameters:

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



I believe "[Errno 11] Resource temporarily unavailable" should be handled by re-trying, instead of erroring out immediately
Comment 1 Richard Purdie 2017-08-29 15:05:50 UTC 
FWIW it does retry for a later tap device and that this wasn't really an error. The real error seems to be the qemu console didn't appear in 60s
Comment 2 Richard Purdie 2017-09-07 14:19:34 UTC 
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=06280ec2e329bbc7413dc162177d1da642608c05 fixes the "error" messages and makes them warnings. Bug 12001 tracks the process not appearing in 60s issue.