Bug 371 - "runqemu qemux86-64" failed due to tap setting
Summary: "runqemu qemux86-64" failed due to tap setting
Status: VERIFIED FIXED
Alias: None
Product: Meta-yocto
Classification: Build System, Metadata & Runtime
Component: meta-yocto (show other bugs)
Version: 0.9
Hardware: x86 x86_64
: Medium normal
Target Milestone: 0.9 M4
Assignee: Scott Garman
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2010-09-30 04:30 UTC by Dexuan Cui
Modified: 2010-12-21 06:07 UTC (History)
7 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified: Program Management
Documentation change: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dexuan Cui 2010-09-30 04:30:28 UTC
Based on today's poky.git's  master (commit 7f7c185c) plus Kevin's fix to gcc
(commit 843d9daf), I met with the failure:

$ runqemu qemux86-64
lockfile: Try praying, giving up on "/tmp/qemu-tap-locks/tap0"
lockfile: Try praying, giving up on "/tmp/qemu-tap-locks/tap1"
lockfile: Try praying, giving up on "/tmp/qemu-tap-locks/tap2"
lockfile: Try praying, giving up on "/tmp/qemu-tap-locks/tap3"
lockfile: Try praying, giving up on "/tmp/qemu-tap-locks/tap4"
lockfile: Try praying, giving up on "/tmp/qemu-tap-locks/tap5"
lockfile: Try praying, giving up on "/tmp/qemu-tap-locks/tap6"
lockfile: Try praying, giving up on "/tmp/qemu-tap-locks/tap7"
lockfile: Try praying, giving up on "/tmp/qemu-tap-locks/tap8"
lockfile: Try praying, giving up on "/tmp/qemu-tap-locks/tap9"
lockfile: Try praying, giving up on "/tmp/qemu-tap-locks/tap10"
lockfile: Try praying, giving up on "/tmp/qemu-tap-locks/tap11"
lockfile: Try praying, giving up on "/tmp/qemu-tap-locks/tap12"
lockfile: Try praying, giving up on "/tmp/qemu-tap-locks/tap13"
lockfile: Try praying, giving up on "/tmp/qemu-tap-locks/tap14"
Setting up tap interface under sudo
lockfile: Try praying, giving up on "/tmp/qemu-tap-locks/tap15"
/opt/dcui/p/scripts/..//scripts/poky-qemu-internal: line 98: ( * 2) + 1 : syntax error: operand expected (error token is "* 2) + 1 ")
/opt/dcui/p/scripts/..//scripts/poky-qemu-internal: line 99: ( * 2) + 2 : syntax error: operand expected (error token is "* 2) + 2 ")
cat: /proc/sys/vm/mmap_min_addr: Operation not permitted
/opt/dcui/p/scripts/..//scripts/poky-qemu-internal: line 154: [: !=: unary operator expected
Warning: distccd not present, no distcc support loaded.
Running qemu-system-x86_64...
/opt/dcui/p/build/tmp/sysroots/x86_64-linux/usr/bin/qemu-system-x86_64 -kernel /opt/dcui/p/build/tmp/deploy/images/bzImage-qemux86-64.bin -net nic,vlan=0 -net tap,vlan=0,ifname=,script=no,downscript=no -hda /opt/dcui/p/build/tmp/deploy/images/poky-image-sdk-qemux86-64.ext3 -show-cursor -usb -usbdevice wacom-tablet -vga vmware -enable-gl --append "vga=0 root=/dev/hda mem=128M ip=192.168.7.::192.168.7.:255.255.255.0"
Enabling opengl
warning: could not configure /dev/net/tun: no virtual network emulation
Releasing lockfile of preconfigured tap device ''


Not sure the "Try praying, giving up" is normal.

Here looks $TAP is emtpy -- will look into this.

BTW: commit 0be92981b32a introduced a bug:
 if [ "$TAP" = "" ]; then
+    if lockfile $LOCKFILE; then
+   TAP=$tap
+   break;    ==========> it's incorrect to use "break" in "if" statement...
+    fi
 else
     echo "Using preconfigured tap device '$TAP'"
 fi
Comment 1 Scott Garman 2010-10-07 14:20:17 UTC
This has been fixed in the refactoring leading up to commit 	0f973ed66551cdd1112ee9df42df5603835b8384. poky-qemu has replaced runqemu as the Poky QEMU control script.
Comment 2 Dexuan Cui 2010-10-20 01:01:08 UTC
Now poky-qemu works fine for me. Let me VERIFY the bug.