qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: William Dauchy <william@gandi.net>
Cc: pbonzini@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] adding a parameter in qemu tap option
Date: Fri, 22 Aug 2014 14:22:53 +0100	[thread overview]
Message-ID: <20140822132253.GB14126@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <20140822082735.GA3129@gandi.net>

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

On Fri, Aug 22, 2014 at 10:27:35AM +0200, William Dauchy wrote:
> Hi,
> 
> I'm trying to understand how to add a parameter in tap option.
> 
> I currently have a working config for a vm; i.e several interfaces using
> multiqueues.
> I had a try with:
> 
> --- a/qapi-schema.json
> +++ b/qapi-schema.json
>  -2006,6 +2008,7 @@
>  ##
>  { 'type': 'NetdevTapOptions',
>    'data': {
> +    '*foo':        'str',
>      '*ifname':     'str',
>      '*fd':         'str',
>      '*fds':        'str',
> 
> i.e just adding a foo parameter; nothing change in my config file (I'm
> using -readconfig option and not cmdline)
> multiqueue is no longer working in some cases.
> 
> I don't get how is it possible. I don't even understand why I don't have
> the same behaviour using the cmdline.
> 
> Maybe I forgot something obvious.
> Does someone has some hints?

I don't see any obvious reason from the small diff you have posted.  Are
you sure this is the only change you've made and the environment is
unchanged?

Stefan

[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2014-08-22 13:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-22  8:27 [Qemu-devel] adding a parameter in qemu tap option William Dauchy
2014-08-22 13:22 ` Stefan Hajnoczi [this message]
2014-08-22 13:28   ` 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=20140822132253.GB14126@stefanha-thinkpad.redhat.com \
    --to=stefanha@redhat.com \
    --cc=pbonzini@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).