public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: William Boughton <bill@boughton.de>
To: kvm@vger.kernel.org
Subject: Re: Since we're sharing, here's my kvmctl script
Date: Thu, 12 Jun 2008 10:38:56 +0200	[thread overview]
Message-ID: <20080612083856.GA7126@yuri.org.uk> (raw)
In-Reply-To: <200806112108.05288.javier@guerrag.com>

On Wed, Jun 11, 2008 at 09:07:49PM -0500, Javier Guerra Giraldez wrote:
> On Wednesday 11 June 2008, Freddie Cash wrote:
> > The script can be run as a normal user, as it will use sudo where
> > needed.  However, this causes all the VMs to be run as root (this is
> > developed on Debian where they've added that annoying "feature" of not
> > being able to create/use tun/tap devices as non-root users).  If
> > anyone knows how to unbreak Debian to allow non-root users to create
> > tun/tap devices, I'm all ears.
> 
> change the group, owner, and/or privileges of /dev/net/tun, usually maneged by 
> udev

This won't help with recent kernels as you need CAP_NET_ADMIN to create
a device.  I use tunctl which is part of uml-utilities in Debian to create 
the network device and then pass it to qemu with ifname.

e.g

USER=kvm
NAME=test
IFACE=tap${NAME}
IFACE=$(sudo $TUNCTL -b -u $USER -t ${IFACE})
qemu-system-x86_64 ... -net tap,script=/etc/qemu-ifup,ifname=${IFACE}


bill
-- 
Bill Boughton

      reply	other threads:[~2008-06-12  9:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-11 22:52 Since we're sharing, here's my kvmctl script Freddie Cash
2008-06-11 23:04 ` Freddie Cash
2008-06-12 15:15   ` Freddie Cash
2008-06-12  0:42 ` qemu-send.c (was Re: Since we're sharing, here's my kvmctl script) Chris Webb
2008-06-12  2:10   ` Javier Guerra Giraldez
2008-06-12  8:35     ` Chris Webb
2008-06-12  2:07 ` Since we're sharing, here's my kvmctl script Javier Guerra Giraldez
2008-06-12  8:38   ` William Boughton [this message]

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=20080612083856.GA7126@yuri.org.uk \
    --to=bill@boughton.de \
    --cc=kvm@vger.kernel.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