mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Jinpu Wang <jinpu.wang@ionos.com>
Cc: fanwenyi0529@gmail.com, kvm@vger.kernel.org,
	 Paolo Bonzini <pbonzini@redhat.com>,
	Xiaoyao Li <xiaoyao.li@intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Hang on reboot in multi-core FreeBSD guest on Linux KVM host with Intel Sierra Forest CPU
Date: Wed, 8 Oct 2025 08:55:24 -0700	[thread overview]
Message-ID: <aOaJbHPBXHwxlC1S@google.com> (raw)
In-Reply-To: <CAMGffE=P5HJkJxh2mj3c_oh6busFKYb0TGuhAc36toc5_uD72w@mail.gmail.com>

Trimmed Cc: to drop people from the original thread.  In the future, just start
a new bug report.  Piggybacking a 10 year old bug just because the symptoms are
similar does more harm than good.  Whatever the old thread was chasing was already
fixed, _10 years_ ago; they were just trying to identy exactly what commit fixed
the problem.  I.e. whatever they were chasing _can't_ be the same root cause,
because even if it's literally the same code bug, it would require a code change
and thus a regression between v4.0 and v6.1.

On Wed, Oct 08, 2025, Jinpu Wang wrote:
> On Wed, Oct 8, 2025 at 2:44 PM Jack Wang <jinpu.wang@ionos.com> wrote:
> > Sorry for bump this old thread, we hit same issue on Intel Sierra Forest
> > machines with LTS kernel 6.1/6.12, maybe KVM comunity could help fix it.

Are there any host kernels that _do_ work?  E.g. have you tried a bleeding edge
host kernel?

> > ### **[BUG] Hang on FreeBSD Guest Reboot under KVM on Intel SierraForest (Xeon 6710E)**
> >
> > **Summary:**
> > Multi-cores FreeBSD guests hang during reboot under KVM on systems with
> > Intel(R) Xeon(R) 6710E (SierraForest). The issue is fully reproducible with
> > APICv enabled and disappears when disabling APICv (`enable_apicv=N`). The
> > same configuration works correctly on Ice Lake (Xeon Gold 6338).

Does Sierra Forest have IPI virtualization?  If so, you could try running with
APICv enabled, but enable_ipiv=false to specifically disable IPI virtualization.

       reply	other threads:[~2025-10-08 15:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <539FC243.2070906@redhat.com>
     [not found] ` <20140617060500.GA20764@minantech.com>
     [not found]   ` <FFEF5F78-D9E6-4333-BC1A-78076C132CBF@jnielsen.net>
     [not found]     ` <6850B127-F16B-465F-BDDB-BA3F99B9E446@jnielsen.net>
     [not found]       ` <jpgioafjtxb.fsf@redhat.com>
     [not found]         ` <74412BDB-EF6F-4C20-84C8-C6EF3A25885C@jnielsen.net>
     [not found]           ` <558AD1B0.5060200@redhat.com>
     [not found]             ` <FAFB2BA9-E924-4E70-A84A-E5F2D97BC2F0@jnielsen.net>
     [not found]               ` <CACzj_yVTyescyWBRuA3MMCC0Ymg7TKF-+sCW1N+Xwfffvw_Wsg@mail.gmail.com>
     [not found]                 ` <CAMGffE=P5HJkJxh2mj3c_oh6busFKYb0TGuhAc36toc5_uD72w@mail.gmail.com>
2025-10-08 15:55                   ` Sean Christopherson [this message]
2025-10-09  3:44                     ` Jinpu Wang
2025-10-09 11:21                       ` Jinpu Wang
2025-10-09 12:36                         ` Jinpu Wang
2025-10-09 12:52                           ` Vitaly Kuznetsov
2025-10-10  5:04                             ` Jinpu Wang

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=aOaJbHPBXHwxlC1S@google.com \
    --to=seanjc@google.com \
    --cc=fanwenyi0529@gmail.com \
    --cc=jinpu.wang@ionos.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=xiaoyao.li@intel.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

Powered by JetHome