On 18.08.2021 13:49, Paul Menzel wrote:
In scripts, running
modprobe kvm_amd 2>/dev/null
modprobe kvm_intel 2>/dev/null
to ensure the modules are loaded causes Linux to log errors.
$ dmesg --level=err
[ 0.641747] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x3a (or later)
[ 40.196868] kvm: already loaded the other module
[ 40.219857] kvm: already loaded the other module
[ 55.501362] kvm [1177]: vcpu0, guest rIP: 0xffffffff96e5b644 disabled perfctr wrmsr: 0xc2 data 0xffff
[ 56.397974] kvm [1418]: vcpu0, guest rIP: 0xffffffff81046158 disabled perfctr wrmsr: 0xc1 data 0xabcd
[1007981.827781] kvm: already loaded the other module
[1008000.394089] kvm: already loaded the other module
[1008030.706999] kvm: already loaded the other module
[1020396.054470] kvm: already loaded the other module
[1020405.614774] kvm: already loaded the other module
[1020410.140069] kvm: already loaded the other module
[1020704.049231] kvm: already loaded the other module
As one of the two KVM modules is already loaded, KVM is functioning, and
their is no error condition. Therefore, demote the log message level to
informational.
Shouldn't this return ENODEV when loading one of these modules instead
as there is no hardware that supports both VMX and SVM?
Thanks,
Maciej
