public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Sridhar Samudrala <sri@us.ibm.com>
Cc: avi@redhat.com, kvm@vger.kernel.org,
	virtualization@lists.linux-foundation.org,
	gregory.haskins@gmail.com, David Stevens <dlstevens@us.ibm.com>,
	Shirley Ma <xma@us.ibm.com>
Subject: Re: [PATCHv4 6/6] qemu-kvm: vhost-net implementation
Date: Thu, 5 Nov 2009 10:23:41 +0200	[thread overview]
Message-ID: <20091105082341.GC5774@redhat.com> (raw)
In-Reply-To: <1257380527.30511.677.camel@w-sridhar.beaverton.ibm.com>

On Wed, Nov 04, 2009 at 04:22:07PM -0800, Sridhar Samudrala wrote:
> On Tue, 2009-11-03 at 00:24 +0200, Michael S. Tsirkin wrote:
> > This adds support for vhost-net virtio kernel backend.
> > 
> > This patch is not intended to being merged yet.
> > I'm posting it for the benefit of people testing
> > the backend.
> > 
> > Usage instructions:
> > vhost currently requires MSI-X support in guest virtio.
> > This means guests kernel version should be >= 2.6.31.
> > 
> > To enable vhost, simply add ",vhost" flag to nic options.
> > Example with tap backend:
> > qemu-system-x86_64 -m 1G disk-c.qcow2 \
> > -net tap,ifname=msttap0,script=/home/mst/ifup,downscript=no \
> >  -net nic,model=virtio,vhost
> > 
> > Example with raw socket backend:
> > ifconfig eth3 promisc
> > qemu-system-x86_64 -m 1G disk-c.qcow2 \
> > -net raw,ifname=eth3 \
> >  -net nic,model=virtio,vhost
> 
> As the vhost is a backend feature, i think the 'vhost' flag should
> be added to the -net tap or -net raw option rather than the -net nic
> which specifies the guest options.
> 
> Thanks
> Sridhar

Yes.

-- 
MST

      reply	other threads:[~2009-11-05  8:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1257200517.git.mst@redhat.com>
2009-11-02 22:23 ` [PATCHv4 1/6] qemu/virtio: move features to an inline function Michael S. Tsirkin
2009-11-02 22:33   ` Anthony Liguori
2009-11-03  5:08     ` Avi Kivity
2009-11-03 10:40     ` Michael S. Tsirkin
2009-11-02 22:23 ` [PATCHv4 2/6] qemu/net: routines to get tap fd Michael S. Tsirkin
2009-11-02 22:23 ` [PATCHv4 3/6] qemu/net: add raw backend Or Gerlitz
2009-11-02 22:24 ` [PATCHv4 4/6] qemu/net: move typedef to qemu-common.h Michael S. Tsirkin
2009-11-02 22:24 ` [PATCHv4 5/6] qemu/raw: add API to get raw socket Michael S. Tsirkin
2009-11-02 22:24 ` [PATCHv4 6/6] qemu-kvm: vhost-net implementation Michael S. Tsirkin
2009-11-05  0:22   ` Sridhar Samudrala
2009-11-05  8:23     ` Michael S. Tsirkin [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=20091105082341.GC5774@redhat.com \
    --to=mst@redhat.com \
    --cc=avi@redhat.com \
    --cc=dlstevens@us.ibm.com \
    --cc=gregory.haskins@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=sri@us.ibm.com \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=xma@us.ibm.com \
    /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