qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Luke Gorrie <luke@snabb.co>
To: Anshul Makkar <anshul.makkar@profitbricks.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
	Nikolay Nikolaev <n.nikolaev@virtualopensystems.com>
Subject: Re: [Qemu-devel] directly inject packet in vrings and not use NetClient APIs
Date: Wed, 19 Nov 2014 18:39:38 +0100	[thread overview]
Message-ID: <CAA2XHbdLQdStDqR0-COVD7sd3e-hphyjVJVx-mso3OdRDnLPrA@mail.gmail.com> (raw)
In-Reply-To: <CAM4NYE-WSdZBF==N=add42sXx8TMom+5wGo4g_Mwn3zSDT1cvw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 695 bytes --]

Hi Anshul,

On Wednesday, November 19, 2014, Anshul Makkar <
anshul.makkar@profitbricks.com> wrote:
>
>
> I have implemented a usermode app that is using vhost-user backend and
> gets direct access to the guest vrings. I am able to receive packets but
> when I post directly to vring and issue kick, packets fails to reach the
> guest. (ifconfig eth0 RX counter is unchanged. tcpdump also doesn't detect
> any packets.) .
>

Sounds to me like something that should work.

I'd suggest debug-compiling the virtio-net driver in the guest to see why
it doesn't take the packet. Gets the kick? Processes the used ring? MAC
address is accepted? Etc. That has been the most productive approach for me.

[-- Attachment #2: Type: text/html, Size: 1028 bytes --]

  reply	other threads:[~2014-11-19 17:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-19 15:53 [Qemu-devel] directly inject packet in vrings and not use NetClient APIs Anshul Makkar
2014-11-19 17:39 ` Luke Gorrie [this message]
2014-11-19 21:42   ` Anshul Makkar

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=CAA2XHbdLQdStDqR0-COVD7sd3e-hphyjVJVx-mso3OdRDnLPrA@mail.gmail.com \
    --to=luke@snabb.co \
    --cc=anshul.makkar@profitbricks.com \
    --cc=n.nikolaev@virtualopensystems.com \
    --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;
as well as URLs for NNTP newsgroup(s).