qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: William Dauchy <william@gandi.net>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] vhost-net issue with multiples interfaces using MQ
Date: Tue, 19 Aug 2014 11:40:26 +0800	[thread overview]
Message-ID: <53F2C72A.4080900@redhat.com> (raw)
In-Reply-To: <20140818114223.GA13779@gandi.net>

On 08/18/2014 07:42 PM, William Dauchy wrote:
> Hello,
>
> Using qemu2.1.0, a linux v3.14.X x86_64 as host and a linux v3.12.X x86_64 as guest
> I'm starting a VM with these network interfaces:
>
> [netdev "vifA.0"]
>   type = "tap"
>   vhost = "on"
>   ifname = "vifA.0"
>   downscript = "no"
>   script = "no"
>   queues = "2"
>
> [device "vifA.0"]
>   driver = "virtio-net-pci"
>   netdev = "vifA.0"
>   mac = "00:16:3e:1a:4e:11"
>   mq = "on"
>   vectors = "5"
>
> (and same config for two other interfaces but with a different MAC address)
>
> In the error message I'm getting during startup:
> unable to start vhost net: 95: falling back on userspace virtio

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 saw that it's failing in `vhost_dev_start` where `vhost_dev_set_features` is returning an error.
> r = vhost_dev_set_features(hdev, hdev->log_enabled);
> I'm hitting the issue starting from three interfaces, i.e no problem with one or two.
> I also don't have the issue with disabling multi queue.
>
> Am I wrong on something? What can I do to help debug this situation?
>
> Regards,

Is this a regression? If yes, you can probably bisect to find the first
bad commit.

Thanks

  reply	other threads:[~2014-08-19  3:40 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 [this message]
2014-08-19 13:02   ` William Dauchy
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=53F2C72A.4080900@redhat.com \
    --to=jasowang@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=william@gandi.net \
    /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).