Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Scott Garman <scott.a.garman@intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: RFC: Who wants/cares about SLiRP networking for QEMU?
Date: Tue, 08 May 2012 18:19:52 -0700	[thread overview]
Message-ID: <4FA9C638.2000502@intel.com> (raw)

This is an inquiry to see if there's much interest in adding an 
alternate networking capability for our QEMU setups. Currently, we use 
tun/tap devices, which need root privileges to be created. Hence, our 
runqemu script requires sudo access.

I'm curious to know who would like to see us use an alternate mechanism 
(most likely SLiRP) to get around the need for sudo access. Is this much 
of a problem for anyone, or would the team's resources be better spent 
on other bugfixes?

Secondly, does anyone have any war stories about using SLiRP for this 
purpose? Is there a better way we should consider doing this?

Thanks,

Scott

-- 
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center



             reply	other threads:[~2012-05-09  1:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-09  1:19 Scott Garman [this message]
2012-05-09  1:28 ` RFC: Who wants/cares about SLiRP networking for QEMU? Jason Wessel
2012-05-10  3:15   ` Scott Garman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FA9C638.2000502@intel.com \
    --to=scott.a.garman@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox