Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Mon, 25 Apr 2022 15:31:57 +0000
From:   Wei Liu <wei.liu@kernel.org>
To:     Michael Kelley <mikelley@microsoft.com>
Cc:     kys@microsoft.com, haiyangz@microsoft.com, sthemmin@microsoft.com,
        wei.liu@kernel.org, linux-kernel@vger.kernel.org,
        linux-hyperv@vger.kernel.org, vkuznets@redhat.com,
        decui@microsoft.com
Subject: Re: [PATCH 1/1] Drivers: hv: vmbus: Add VMbus IMC device to
 unsupported list
Message-ID: <20220425153157.q23v3ij6bjcke35f@liuwe-devbox-debian-v2>
References: <1649818140-100953-1-git-send-email-mikelley@microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1649818140-100953-1-git-send-email-mikelley@microsoft.com>
Precedence: bulk

On Tue, Apr 12, 2022 at 07:49:00PM -0700, Michael Kelley wrote:
> Hyper-V may offer an Initial Machine Configuration (IMC) synthetic
> device to guest VMs. The device may be used by Windows guests to get
> specialization information, such as the hostname.  But the device
> is not used in Linux and there is no Linux driver, so it is
> unsupported.
> 
> Currently, the IMC device GUID is not recognized by the VMbus driver,
> which results in an "Unknown GUID" error message during boot. Add
> the GUID to the list of known but unsupported devices so that the
> error message is not generated. Other than avoiding the error message,
> there is no change in guest behavior.
> 
> Signed-off-by: Michael Kelley <mikelley@microsoft.com>

Applied to hyperv-next. Thanks.