From: William Dauchy <william@gandi.net>
To: Jason Wang <jasowang@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] vhost-net issue with multiples interfaces using MQ
Date: Tue, 19 Aug 2014 15:02:57 +0200 [thread overview]
Message-ID: <20140819130257.GA9040@gandi.net> (raw)
In-Reply-To: <53F2C72A.4080900@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 433 bytes --]
On Aug19 11:40, Jason Wang wrote:
> What's the qemu command line for your testing? I try simple command line
> with 3 mq cards in qemu 2.1. Everything works fine.
I'm using readconfig option to read the three vif interfaces.
thanks for testing I will re-triple test to see what's wrong
> Is this a regression? If yes, you can probably bisect to find the first
> bad commit.
nope first time I'm using it
--
William
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2014-08-19 13:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 11:42 [Qemu-devel] vhost-net issue with multiples interfaces using MQ William Dauchy
2014-08-19 3:40 ` Jason Wang
2014-08-19 13:02 ` William Dauchy [this message]
2014-08-20 11:27 ` William Dauchy
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=20140819130257.GA9040@gandi.net \
--to=william@gandi.net \
--cc=jasowang@redhat.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).