Bug 1474 - QEMU won't run on a system that does not support tunctl
Summary: QEMU won't run on a system that does not support tunctl
Status: RESOLVED FIXED
Alias: None
Product: Meta-yocto
Classification: Build System, Metadata & Runtime
Component: meta-yocto (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Low enhancement
Target Milestone: 1.5
Assignee: Andrei Dinu
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2011-09-13 14:16 UTC by Mark Hatle
Modified: 2013-06-05 08:02 UTC (History)
4 users (show)

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

Attachments
Slirp Patch - may need rebasing (12.33 KB, message/rfc822)
2013-04-26 21:30 UTC, Saul Wold 		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 Mark Hatle 2011-09-13 14:16:39 UTC 
I am on a shared machine, where I do not normally have sudo access.  Without it, the runqemu scripts fails.

I was granted sudo access, and everything still fails as the system does not support enabling the "tap" devices.

I was able to hack the qemu run script to disable the setup of the network and requirements for sudo.  This should be a run-time option to avoid networking and items that require sudo.
Comment 1 Mark Hatle 2012-05-08 15:51:10 UTC 
The best workaround for this (no access to root) is SLiRP support in QEMU.
Comment 2 Scott Garman 2012-05-11 02:45:43 UTC 
Whoever implements this should get in touch with Jason Wessel: jason.wessel@windriver.com. Jason writes:

"We have QEMU + UserMode NFS + SLiRP for years in Wind River Linux products.   In that period I have sent upstream most of the patches dealing with problems.  There remain a few patches to the User Mode NFS service which are not currently in the Yocto project.  I also have a patch that is not in the QEMU mainline that deals with syn packets where QEMU violates the RFC that was never merged upstream for some reason.  I imagine that you will probably want all those patches if that is going to be your mode of operation."

"You will also want to create a mechanism to easily add port redirections.  Typically we have always used what we call an simulator "instance" number so we know the ports are at generally fixed locations and for each instance number all the port redirections are incremented by 100."
Comment 3 Saul Wold 2013-04-26 21:30:24 UTC 
Created attachment 1202 [details]
Slirp Patch - may need rebasing