From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id CA88BC433EF for ; Tue, 18 Jan 2022 14:22:28 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S245176AbiAROW1 (ORCPT ); Tue, 18 Jan 2022 09:22:27 -0500 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:43527 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S245071AbiAROW0 (ORCPT ); Tue, 18 Jan 2022 09:22:26 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1642515746; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=y4YzeEHCT5Qsp1fTF2Ff1Fo1X3wdgn1gp47dQ5F5Huc=; b=Gcj7TMGEHboZaCr6rlwiPf7SSMLa3Pw/RL/BnC5t06ONDehofRcZ+waOV/7V6FQh+9EA7e P1O3T/XRj23f+m7ZmnYpWrJvHhNUODi1ivHFO0pNkIr/DBQnFE5Tf1MSkAL9u2q5950zva l2bUiynzSFsOvizov5mzylY/DtNyYNM= Received: from mail-ed1-f72.google.com (mail-ed1-f72.google.com [209.85.208.72]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-652-KlFFfJILOuGbA2J0z9tbog-1; Tue, 18 Jan 2022 09:22:25 -0500 X-MC-Unique: KlFFfJILOuGbA2J0z9tbog-1 Received: by mail-ed1-f72.google.com with SMTP id t5-20020aa7db05000000b00402670daeb9so6195537eds.5 for ; Tue, 18 Jan 2022 06:22:24 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:mime-version; bh=y4YzeEHCT5Qsp1fTF2Ff1Fo1X3wdgn1gp47dQ5F5Huc=; b=X3GT5o/C25hBNGj/QFdIVjVDQsJsLYyElyo/ovPtpgREn/GLkAT97PdlOoRSOVxz35 0XQrxkd7LWTAi3wJRD+uRELxEgCgauKuveBnAYfUOO/4MkwRwYoXU84AFBj+NeXpT1/K 6F1Cy38jiA7Bw7PtUb5Tk0cU3oxntyqm+Sj8PCjUUBQdF9rOESX5Rum1GwhHhmINIXAe DQ/sQR1NOKhqkhjyvGcwTci84tfnk1K7ASsNdRdkB4b4L6BNwz4cCgXnBPbgyLwdt3cM +mH4wWguJnnyv4YMdHk9S+ZeAdfHaZNKkeLkNecldTrrqFUCcM6aKO92yPuLF3iPXHWc mRuA== X-Gm-Message-State: AOAM531dlCrlIcKZRh3L88j3GNky7sZSckJje9xRKKA5tDpn1sr4mfO9 gKdY5U/SVVz5MXlPoD+DY+bj+yV/FYEv/qSBED5oqAcLemDueqzJ29vfDtrCgjggnOdhzHjQASI veBS4MHsIAlrrZjH5cKHQHPEh X-Received: by 2002:a17:907:a088:: with SMTP id hu8mr8326068ejc.371.1642515743988; Tue, 18 Jan 2022 06:22:23 -0800 (PST) X-Google-Smtp-Source: ABdhPJwzJQAqutfAisYqiCh+L8bg9o17eCN/WQ/E0+eI30kykTX1fCzEW1NnfAmieqKaAxTUw7qCtA== X-Received: by 2002:a17:907:a088:: with SMTP id hu8mr8326054ejc.371.1642515743776; Tue, 18 Jan 2022 06:22:23 -0800 (PST) Received: from fedora (nat-2.ign.cz. [91.219.240.2]) by smtp.gmail.com with ESMTPSA id l25sm4381770edc.20.2022.01.18.06.22.22 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 18 Jan 2022 06:22:23 -0800 (PST) From: Vitaly Kuznetsov To: Paolo Bonzini Cc: Sean Christopherson , Wanpeng Li , Jim Mattson , Maxim Levitsky , linux-kernel@vger.kernel.org, kvm@vger.kernel.org Subject: Re: [PATCH v3 0/5] KVM: nVMX: Fix Windows 11 + WSL2 + Enlightened VMCS In-Reply-To: <20220112170134.1904308-1-vkuznets@redhat.com> References: <20220112170134.1904308-1-vkuznets@redhat.com> Date: Tue, 18 Jan 2022 15:22:22 +0100 Message-ID: <87k0exktsx.fsf@redhat.com> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Vitaly Kuznetsov writes: > Changes since v2 [Sean]: > - Tweak a comment in PATCH5. > - Add Reviewed-by: tags to PATCHes 3 and 5. > > Original description: > > Windows 11 with enabled Hyper-V role doesn't boot on KVM when Enlightened > VMCS interface is provided to it. The observed behavior doesn't conform to > Hyper-V TLFS. In particular, I'm observing 'VMREAD' instructions trying to > access field 0x4404 ("VM-exit interruption information"). TLFS, however, is > very clear this should not be happening: > > "Any VMREAD or VMWRITE instructions while an enlightened VMCS is active is > unsupported and can result in unexpected behavior." > > Microsoft confirms this is a bug in Hyper-V which is supposed to get fixed > eventually. For the time being, implement a workaround in KVM allowing > VMREAD instructions to read from the currently loaded Enlightened VMCS. > > Patches 1-2 are unrelated fixes to VMX feature MSR filtering when eVMCS is > enabled. Patches 3 and 4 are preparatory changes, patch 5 implements the > workaround. > Paolo, would it be possible to pick this up for 5.17? Technically, this is a "fix", even if the bug itself is not in KVM) -- Vitaly