From: Eugene Coetzee <eugene-ms3nWvnsWYxl57MIdRCFDg@public.gmane.org>
To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Running KVM without root privileges
Date: Sun, 19 Aug 2007 15:59:13 +0200 [thread overview]
Message-ID: <46C84CB1.5070202@reedflute.com> (raw)
In-Reply-To: <68676e00708190602p6b0ca91csc3a4550de162443a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Luca wrote:
>On 8/19/07, Eugene Coetzee <eugene-ms3nWvnsWYxl57MIdRCFDg@public.gmane.org> wrote:
>
>
>>Hi .
>>
>>I'm trying to run KVM on Feisty, 64 bit Intel with the "-net nic -net
>>tap" switches so I can use it in bridged network mode.
>>
>>It refuses and I have to run it sudo which for security concerns I don't
>>want to do.
>>
>>
>You need CAP_NET_ADMIN to fiddle with TUN/TAP.
>
>
Thanks for the reply. I'm a little confused about the interaction
between KVM and qemu. Which binary requires CAP_NET_ADMIN capability -
KVM or qemu ?
(see http://www.friedhoff.org/fscaps.html#Qemu )
regards,
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-08-19 13:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-19 12:38 Running KVM without root privileges Eugene Coetzee
[not found] ` <1187527111.10912.1.camel-w9fvoj/KL/s9qinSMKopcw@public.gmane.org>
2007-08-19 13:02 ` Luca
[not found] ` <68676e00708190602p6b0ca91csc3a4550de162443a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-08-19 13:59 ` Eugene Coetzee [this message]
[not found] ` <46C84CB1.5070202-ms3nWvnsWYxl57MIdRCFDg@public.gmane.org>
2007-08-19 15:00 ` Luca
[not found] ` <68676e00708190800u66b8039p2be2cdd344e87805-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-08-21 15:49 ` Eugene Coetzee
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=46C84CB1.5070202@reedflute.com \
--to=eugene-ms3nwvnswyxl57midrcfdg@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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