public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: "K. Y. Srinivasan" <kys@microsoft.com>,
	Haiyang Zhang <haiyangz@microsoft.com>,
	Stephen Hemminger <sthemmin@microsoft.com>,
	Wei Liu <wei.liu@kernel.org>
Cc: linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] tools/hv: async name resolution in kvp_daemon
Date: Fri, 19 Mar 2021 15:46:07 +0100	[thread overview]
Message-ID: <20210319154607.550198ad.olaf@aepfle.de> (raw)
In-Reply-To: <20210319144145.4064-1-olaf@aepfle.de>

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

Am Fri, 19 Mar 2021 15:41:44 +0100
schrieb Olaf Hering <olaf@aepfle.de>:

> FullyQualifiedDomainName

I think in the past I did asked MSFT what the host side really expects. Maybe this time there will be an answer.

Why would the host expect a FQDN from a VM? Why would it care about DNS layout of the network within the VM?

Basically my copy of hv_kvp_daemon just sends `uname -n` to the host. This is more correct. This does not waste any network resources. This, up to now, led to no complains.

So, what is the purpose of this API?


Olaf

[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-03-19 14:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-19 14:41 [PATCH v2] tools/hv: async name resolution in kvp_daemon Olaf Hering
2021-03-19 14:46 ` Olaf Hering [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-11-13 15:54 Olaf Hering
2019-11-13 16:00 ` Olaf Hering
2020-01-03 13:31 ` Olaf Hering

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=20210319154607.550198ad.olaf@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=haiyangz@microsoft.com \
    --cc=kys@microsoft.com \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sthemmin@microsoft.com \
    --cc=wei.liu@kernel.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