From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Sean Christopherson <seanjc@google.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
Sean Christopherson <sean.j.christopherson@intel.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [FYI PATCH] Revert "KVM: x86/mmu: Zap only TDP MMU leafs in kvm_zap_gfn_range()"
Date: Fri, 25 Mar 2022 11:38:21 +0100 [thread overview]
Message-ID: <87tubmnwpu.fsf@redhat.com> (raw)
In-Reply-To: <Yj0FYSC2sT4k/ELl@google.com>
Sean Christopherson <seanjc@google.com> writes:
> On Mon, Mar 21, 2022, Paolo Bonzini wrote:
>> On 3/18/22 17:48, Paolo Bonzini wrote:
>> > This reverts commit cf3e26427c08ad9015956293ab389004ac6a338e.
>> >
>> > Multi-vCPU Hyper-V guests started crashing randomly on boot with the
>> > latest kvm/queue and the problem can be bisected the problem to this
>> > particular patch.
...
>
> Vitaly, can you provide repro instructions? A nearly-complete QEMU command line
> would be wonderful :-)
The issue was observed with genuine Hyper-V guests, with or without any
Hyper-V enlightenments (not with Linux using Hyper-V enlightenments)
The QEMU command line is nothing special, e.g.
~/qemu/build/qemu-system-x86_64 -machine
q35,accel=kvm,kernel-irqchip=split -name guest=win2019 -cpu host -smp 16
-m 16384 -drive
file=/home/VMs/ws2019_gen1.qcow2,format=qcow2,if=none,id=drive-ide0-0-0
-device
ide-hd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1
-vnc :0 -rtc base=localtime,driftfix=slew --no-hpet -monitor stdio
--no-reboot
I'm also pretty sure I saw this on both AMD and Intel hosts, I can try
reproducing if needed.
--
Vitaly
next prev parent reply other threads:[~2022-03-25 10:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 16:48 [FYI PATCH] Revert "KVM: x86/mmu: Zap only TDP MMU leafs in kvm_zap_gfn_range()" Paolo Bonzini
2022-03-21 9:13 ` Paolo Bonzini
2022-03-24 23:57 ` Sean Christopherson
2022-03-25 10:38 ` Vitaly Kuznetsov [this message]
2022-03-25 11:21 ` Paolo Bonzini
2022-03-25 20:22 ` Sean Christopherson
2022-03-25 15:03 ` Vitaly Kuznetsov
2022-03-25 20:18 ` Sean Christopherson
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=87tubmnwpu.fsf@redhat.com \
--to=vkuznets@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=sean.j.christopherson@intel.com \
--cc=seanjc@google.com \
/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