[Bug]: vboxdrv triggers kvm_amd probe on Intel systems

[thisisamirv]

Version

7.2.6

Host OS Type

Linux

Host OS name + version

Arch linux 6.19.6-arch1-1

Host Architecture

x86

Guest OS Type

Linux

Guest Architecture

x86

Guest OS name + version

No response

Component

Other

What happened?

On an Intel-based system, the kvm_amd kernel module is being probed during boot, resulting in the message:

kvm_amd: CPU 1 isn't AMD or Hygon

This occurs even though:

The system uses an Intel CPU
kvm_intel loads correctly
No AMD-related virtualization should be involved

The message appears immediately before vboxdrv initialization and VirtualBox reports finding KVM symbols:

kvm_amd: CPU 1 isn't AMD or Hygon
vboxdrv: module uses symbol (...) from namespace module:kvm,kvm-amd,kvm-intel
vboxdrv: Found KVM hardware-virtualization symbols

• This behavior was initially reported upstream to the Linux kernel, where it was suggested that the trigger likely comes from VirtualBox (vboxdrv) interacting with KVM symbols.
• The issue is harmless but creates confusing and unnecessary log noise.
• Blacklisting kvm_amd prevents the message, suggesting it is not required for VirtualBox operation on Intel systems.

How can we reproduce this?

1- Install VirtualBox on an Intel-based Linux system
2- Ensure KVM is available (kvm_intel loads normally)
3- Reboot the system
4- Observe dmesg output during early boot

Did you upload all of your necessary log files, screenshots, etc.?

• Yes, I've uploaded all pertinent files to this issue.

[cybersnow02]

I also seen this in my VBox.log when looking at something else. Maybe it is trying to distinguish if this is an AMD or Intel CPU about CPU capabilities. Then, it throws this error but it might actually not preventing VBox to work as usual. Maybe just avoid reporting this error in the code?

[Doaxan]

Same here
29.04.2026 17:13 kvm_amd CPU 8 isn't AMD or Hygon