All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Alex Kirillov <lekiravi@yandex-team.ru>
Cc: jasowang@redhat.com, qemu-devel@nongnu.org,
	yc-core@yandex-team.ru, armbru@redhat.com
Subject: Re: QMP netdev_add multiple dnssearch values
Date: Fri, 25 Oct 2019 07:20:46 +0200	[thread overview]
Message-ID: <87d0elmmdt.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <713881571320392@iva8-147456c4bd40.qloud-c.yandex.net> (Alex Kirillov's message of "Thu, 17 Oct 2019 16:53:22 +0300")

Alex Kirillov <lekiravi@yandex-team.ru> writes:

> Hi,
>
> I'm trying to create a user (slirp) interface with several `dnssearch` values using QMP.
> But every variant I pass can't do that.

What exactly goes wrong?  Does the QMP command fail?  Does it succeed
but the network backend incorrectly?

> According to the QAPI schema it should be like:
>
> {
>     "execute": "netdev_add",
>     "arguments": {
>         "id": "netdev0",
>         "type": "user",
>         "dnssearch": [
>             {
>                 "str": "8.8.8.8"
>             },
>             {
>                 "str": "8.8.4.4"
>             }
>         ]
>     }
> }
>
> I looked through code and find out that `dnssearch` is passing to the `slirp_dnssearch` (net/slirp.c),
> but the only way to execute this function correctly is to pass simply string (like "example.org") to `dnssearch` OR to use command line options.
>
>
> What is the correct form of QMP command that I should use?
>
>
> P.S. Looks like fields `hostfwd` and `guestfwd` has the same issue.
>
> -- 
> Alex Kirillov
> Yandex.Cloud



  reply	other threads:[~2019-10-25  5:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-17 13:53 QMP netdev_add multiple dnssearch values Alex Kirillov
2019-10-25  5:20 ` Markus Armbruster [this message]
2019-10-29 10:20   ` Alex Kirillov
2019-11-27 13:30     ` Markus Armbruster
2019-11-27 15:49       ` Eric Blake
2020-03-12 21:26         ` Eric Blake
2020-03-13 15:09           ` Markus Armbruster

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=87d0elmmdt.fsf@dusky.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=lekiravi@yandex-team.ru \
    --cc=qemu-devel@nongnu.org \
    --cc=yc-core@yandex-team.ru \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.