Bug 9437 - after dropping HOB from build appliance, "runqemu" doesn't work: TUN unavailable
Summary: after dropping HOB from build appliance, "runqemu" doesn't work: TUN unavai...
Status: VERIFIED FIXED
Alias: None
Product: Runtime
Classification: Build System, Metadata & Runtime
Component: build-appliance (show other bugs)
Version: 2.1
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 2.1 M4
Assignee: Juro Bystricky
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-04-12 07:46 UTC by Ke Zou
Modified: 2016-04-25 05:52 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
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 Ke Zou 2016-04-12 07:46:19 UTC 
BA image URL:
http://autobuilder.yoctoproject.org/pub/releases/yocto-2.1.rc1/build-appliance/

how to reproduce:
unzip build-appliance image
use vmplayer to run 
in BA shell: build image(core-image-minimal)
try to runqemu with newly-built image
"runqemu qemuxxx nographic"

the printout:
sh-4.3$ runqemmu qemuarm nographic
TUN control device /dev/net/tun is unavailable: you may need to enable TUN (e.g. sudo modprobe tun)
Comment 1 Juro Bystricky 2016-04-13 18:26:54 UTC 
To remedy this with the existing BA:
1. Switch to root terminal "Terminal" from the default "Terminal <2>"
2. Run 
   # sudo modprobe tun
3. 
   # cd /sbin
   # ls -s /usr/sbin/iptables iptables

4. Switch to "Terminal <2>"

   $ runqemu qemux86


I'll try to modify the BA recipe so that the above steps are not needed.
Comment 2 Juro Bystricky 2016-04-15 16:27:29 UTC 
Patch sent to the mailing list:
http://lists.openembedded.org/pipermail/openembedded-core/2016-April/120284.html
Comment 4 Ke Zou 2016-04-25 05:52:27 UTC 
verified with yocto 2.1 rc2 build