public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Dragos Tatulea <dragos.tatulea@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
	kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: TODO item: guest programmable mac/vlan filtering with macvtap
Date: Mon, 1 Nov 2010 13:29:43 +0200	[thread overview]
Message-ID: <20101101112943.GA28908@redhat.com> (raw)
In-Reply-To: <AANLkTi=amTpbmC_9doArzOOoHF0UMaKaTmyvwToHFj3U@mail.gmail.com>

On Mon, Nov 01, 2010 at 11:48:23AM +0100, Dragos Tatulea wrote:
> > 1. add a secondary mac (or third, etc) address to the guest virtio-net
> > interface.
> Maybe I misunderstood this. Is it just setting another mac on the
> guest virtio-net interface?

Well, yes, that's also not possible at the moment.  Or e.g. set more
than one mac per virtio-net device using macvlan.

> >
> > 4. the above stuff must be controllable by host admin
> >  - Well, for this there are a few options:
> >    > admin switch that allows the guest user to add macs
> >    > preconfig allowed MAC's in mactap (or qemu config) for the guest user
> >    > allow/disallow command for user in qemu (although this doesn't
> > seem to be supported)
> >
> Well, on a second thought, qemu capabilities should be just fine, right?
> 
> -- Dragos

At some level, although I think we also want a way to disable
access that qemu can't override unless it has net admin capability.

-- 
MST

  reply	other threads:[~2010-11-01 11:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-14 21:40 TODO item: guest programmable mac/vlan filtering with macvtap Dragos Tatulea
2010-10-15  6:56 ` Michael S. Tsirkin
2010-10-18 10:31   ` Arnd Bergmann
2010-10-30 14:50 ` Dragos Tatulea
2010-11-01 10:48   ` Dragos Tatulea
2010-11-01 11:29     ` Michael S. Tsirkin [this message]
2010-11-01 17:12     ` Dragos Tatulea
2011-06-24  0:07       ` Roopa Prabhu

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=20101101112943.GA28908@redhat.com \
    --to=mst@redhat.com \
    --cc=arnd@arndb.de \
    --cc=dragos.tatulea@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.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