I get these messages continually whenever my Windows 10 VM is running, any way to suppress them as my log is pretty useless as its just full of them and trying to find useful data is impossible ?

 

eg.

Oct 14 13:59:08 Tower kernel: kvm [7321]: vcpu0 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop

Oct 14 13:59:08 Tower kernel: kvm [7321]: vcpu0 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop

Oct 14 13:59:08 Tower kernel: kvm [7321]: vcpu0 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop

Oct 14 13:59:08 Tower kernel: kvm [7321]: vcpu0 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop

Oct 14 13:59:08 Tower kernel: kvm [7321]: vcpu0 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop

Oct 14 13:59:08 Tower kernel: kvm [7321]: vcpu0 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop

Oct 14 13:59:08 Tower kernel: kvm [7321]: vcpu0 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop

Oct 14 13:59:13 Tower kernel: kvm_set_msr_common: 514 callbacks suppressed

Oct 14 13:59:13 Tower kernel: kvm [7321]: vcpu0 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop

Oct 14 13:59:13 Tower kernel: kvm [7321]: vcpu0 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop

Oct 14 13:59:13 Tower kernel: kvm [7321]: vcpu0 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop

Oct 14 13:59:13 Tower kernel: kvm [7321]: vcpu0 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop

Oct 14 13:59:13 Tower kernel: kvm [7321]: vcpu0 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop

Oct 14 13:59:13 Tower kernel: kvm [7321]: vcpu0 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop

Oct 14 13:59:13 Tower kernel: kvm [7321]: vcpu0 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop

Oct 14 13:59:13 Tower kernel: kvm [7321]: vcpu0 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop

Oct 14 13:59:13 Tower kernel: kvm [7321]: vcpu0 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop

Oct 14 13:59:13 Tower kernel: kvm [7321]: vcpu0 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop

Oct 14 13:59:18 Tower kernel: kvm_set_msr_common: 514 callbacks suppressed

Oct 14 13:59:18 Tower kernel: kvm [7321]: vcpu0 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop

 

etc etc.

I can't help with a fix for that, but if you want a cleaner version of your syslog for examination, try "uniq -s 15 /var/log/syslog /boot/syslog.txt".  It will put a copy of the syslog on the flash drive, minus all or most of the duplicated lines.

 

To clean the current syslog, you could try something like: (untested)

cd /var/log
uniq -s 15 syslog sysnew
mv -f sysnew syslog

i think that error  vcpu0 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop  error happens when the virtual machine tries to access an MSR that isnt supported by the virtual CPU.

i think that error  vcpu0 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop  error happens when the virtual machine tries to access an MSR that isnt supported by the virtual CPU.

 

What's that in English and how do I fix it?

Which virtual CPU are you emulating? If you are using host passthrough, it should not occur.

Hi,

 

This is the relevant xml:

 

<vcpu placement='static'>4</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='0'/>
    <vcpupin vcpu='1' cpuset='1'/>
    <vcpupin vcpu='2' cpuset='2'/>
    <vcpupin vcpu='3' cpuset='3'/>
  </cputune>
  <resource>
    <partition>/machine</partition>
  </resource>
  <os>
    <type arch='x86_64' machine='pc-i440fx-2.3'>hvm</type>
  </os>
  <features>
    <acpi/>
    <apic/>
    <hyperv>
      <relaxed state='on'/>
      <vapic state='on'/>
      <spinlocks state='on' retries='8191'/>
      <vendor id='none'/>
    </hyperv>
  </features>
  <cpu mode='host-passthrough'>
    <topology sockets='1' cores='4' threads='1'/>
  </cpu>
  <clock offset='localtime'>
    <timer name='hypervclock' present='yes'/>
    <timer name='hpet' present='no'/>
  </clock>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>

I find it strange that either your processor or your kernel don't support the debug register MSR. Are you sure you haven't turned something off in your BIOS?

 

Adding ignore_msrs=1 was a workaround that worked for some people, but that's already in the stock /etc/modprobe.d/kvm.conf.

I'll check my BIOS settings then, any idea what sort of settings in there I need to confirm ?

There may be something about Model Specific Registers or MSR or debugging, since the MSR listed in this topic is usually employed for hardware level debugging, possibly something is trying to employ some sort of non-VT-x virtual machine, like some sort of software protection scheme.

Eventually found out that these messages are caused by an automation program I run called HouseBot.

 

Once I start it then errors begin, once I shut it down they stop.