public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: bugzilla-daemon@kernel.org
Cc: kvm@vger.kernel.org
Subject: Re: [Bug 221249] New: kvm_amd prints "CPU 1 isn't AMD or Hygon" on Intel Core Ultra (Arch Linux)
Date: Fri, 3 Apr 2026 07:13:18 -0700	[thread overview]
Message-ID: <ac_K_v2p5AJJ2up4@google.com> (raw)
In-Reply-To: <bug-221249-28872@https.bugzilla.kernel.org/>

On Mon, Mar 16, 2026, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=221249
> 
>             Bug ID: 221249
>            Summary: kvm_amd prints "CPU 1 isn't AMD or Hygon" on Intel
>                     Core Ultra (Arch Linux)
>            Product: Virtualization
>            Version: unspecified
>           Hardware: Intel
>                 OS: Linux
>             Status: NEW
>           Severity: normal
>           Priority: P3
>          Component: kvm
>           Assignee: virtualization_kvm@kernel-bugs.osdl.org
>           Reporter: thisisamirv@gmail.com
>         Regression: No
> 
> Created attachment 309692
>   --> https://bugzilla.kernel.org/attachment.cgi?id=309692&action=edit
> log
> 
> I am observing the following kernel message on a Lenovo ThinkPad X9-14 Gen 1
> running Arch Linux on an Intel CPU:
> 
> kvm_amd: CPU 1 isn't AMD or Hygon
> 
> # System information
> 
> Kernel: 6.19.6-arch1-1
> Distribution: Arch Linux

...

>   kvm_amd: CPU 1 isn't AMD or Hygon
> 
> * The system does not have an AMD CPU.
> * It appears the kvm_amd module may be probed or initialized briefly
>   even on Intel systems.

This is highly unlikely to be an upstream kernel bug.  The unwanted probing is
most likely coming from elsewhere.  Given that the out-of-tree VirtualBox driver
loads shortly after the failed kvm_amd.ko load, my guess is that vboxdrv is the
culprit. 

[    3.087169] kvm_amd: CPU 1 isn't AMD or Hygon
[    3.118021] vboxdrv: module uses symbol (cr4_read_shadow) from namespace module:kvm,kvm-amd,kvm-intel, but does not import it.
[    3.118032] vboxdrv: module uses symbol (__flush_tlb_all) from namespace module:kvm,kvm-amd,kvm-intel, but does not import it.
[    3.118063] vboxdrv: module uses symbol (cr4_update_irqsoff) from namespace module:kvm,kvm-amd,kvm-intel, but does not import it.
[    3.124334] vboxdrv: Found 8 processor cores/threads
[    3.152502] rtR0InitNative: g_pLnxInitMm=000000000ba3e8e7
[    3.181635] vboxdrv: Found KVM hardware-virtualization symbols
[    3.181638] vboxdrv: TSC mode is Invariant, tentative frequency 3302385743 Hz
[    3.181641] vboxdrv: Successfully loaded version 7.2.6 r172322 (interface 0x00340002)

FWIW, attempting to load kvm_{amd,intel}.ko on the "wrong" CPU is benign other
than the error message.

  reply	other threads:[~2026-04-03 14:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-16 23:22 [Bug 221249] New: kvm_amd prints "CPU 1 isn't AMD or Hygon" on Intel Core Ultra (Arch Linux) bugzilla-daemon
2026-04-03 14:13 ` Sean Christopherson [this message]
2026-04-03 14:13 ` [Bug 221249] " bugzilla-daemon

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=ac_K_v2p5AJJ2up4@google.com \
    --to=seanjc@google.com \
    --cc=bugzilla-daemon@kernel.org \
    --cc=kvm@vger.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