DPDK patches and discussions
 help / color / mirror / Atom feed
From: Pankaj Chauhan <pankaj.chauhan@nxp.com>
To: Vaibhav Sood <vaibhav_sood@persistent.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Running DPDK in a VM
Date: Wed, 10 Aug 2016 10:49:58 +0530	[thread overview]
Message-ID: <3c652f40-f6bb-e49e-ec4c-4c61e212112d@nxp.com> (raw)
In-Reply-To: <PN1PR01MB0415A16E4BB6CEAB3CB66D879B070@PN1PR01MB0415.INDPRD01.PROD.OUTLOOK.COM>

On 8/4/2016 3:51 PM, Vaibhav Sood wrote:
Hi,

> Hi!
>
> I am looking at running DPDK in a VM, I would like to know if there are any limitations when doing this in terms of any DPDK features that do not work in a VM
>

We do run DPDK in VM, and we have not come across any major limitations. 
There are multiple ways to run DPDK in virtual machine, if you are using 
virtio devices:

1. vhost-switch : please refer following link:

http://dpdk.readthedocs.io/en/v16.04/sample_app_ug/vhost.html

2. you can use OVS also as backend instead of vhost-switch.

we've used both methods on our platforms and they work fine.

> The only post I came across for running DPDK in a VM is this: http://dpdk.org/ml/archives/dev/2013-September/000441.html
>
> As an example, I tried to run the DPDK test suite (DTS, http://dpdk.org/doc/dts/gsg/ ) and see some tests fail saying virtio nics are not supported (Specifically, the ethertype_filter and five_tuple_filter tests give an error: FAILED ''virtio nic not support syn filter''). I would like to know if there are any limitations along these lines when running DPDK in VMs as compared to physical machines/NICS
>
> Thanks!
> Vaibhav
>

Thanks,
Pankaj

      reply	other threads:[~2016-08-10  5:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-04 10:21 Vaibhav Sood
2016-08-10  5:19 ` Pankaj Chauhan [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=3c652f40-f6bb-e49e-ec4c-4c61e212112d@nxp.com \
    --to=pankaj.chauhan@nxp.com \
    --cc=dev@dpdk.org \
    --cc=vaibhav_sood@persistent.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;
as well as URLs for NNTP newsgroup(s).