Got this error.

Logs are attached.

I've found this:

Aug 25 20:27:18 Tower kernel: ------------[ cut here ]------------
Aug 25 20:27:18 Tower kernel: WARNING: CPU: 0 PID: 10502 at arch/x86/kvm/vmx.c:4773 vmx_deliver_posted_interrupt+0xec/0x128 [kvm_intel]
Aug 25 20:27:18 Tower kernel: Modules linked in: vhost_net tun vhost macvtap macvlan kvm_intel kvm md_mod xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables iptable_filter ip_tables bonding e1000e ptp pps_core r8169 mii hid_logitech_hidpp mxm_wmi x86_pkg_temp_thermal coretemp i2c_i801 i2c_smbus ahci i2c_core hid_logitech_dj libahci wmi [last unloaded: md_mod]
Aug 25 20:27:18 Tower kernel: CPU: 0 PID: 10502 Comm: CPU 0/KVM Not tainted 4.9.30-unRAID #1
Aug 25 20:27:18 Tower kernel: Hardware name: ASUS All Series/X99-A II, BIOS 0601 05/18/2016
Aug 25 20:27:18 Tower kernel: ffffc9000d0b7b60 ffffffff813a4a1b 0000000000000000 ffffffffa00ab568
Aug 25 20:27:18 Tower kernel: ffffc9000d0b7ba0 ffffffff8104d0d9 000012a50d0b7a00 ffff8807fe620000
Aug 25 20:27:18 Tower kernel: 000000000000000a ffffc9000d0b7c80 ffff8802083d8000 ffff8807fe620000
Aug 25 20:27:18 Tower kernel: Call Trace:
Aug 25 20:27:18 Tower kernel: [<ffffffff813a4a1b>] dump_stack+0x61/0x7e
Aug 25 20:27:18 Tower kernel: [<ffffffff8104d0d9>] __warn+0xb8/0xd3
Aug 25 20:27:18 Tower kernel: [<ffffffff8104d1a1>] warn_slowpath_null+0x18/0x1a
Aug 25 20:27:18 Tower kernel: [<ffffffffa008e3ee>] vmx_deliver_posted_interrupt+0xec/0x128 [kvm_intel]
Aug 25 20:27:18 Tower kernel: [<ffffffffa0064e81>] __apic_accept_irq+0x173/0x19b [kvm]
Aug 25 20:27:18 Tower kernel: [<ffffffffa00660bc>] kvm_apic_set_irq+0x25/0x27 [kvm]
Aug 25 20:27:18 Tower kernel: [<ffffffffa0069506>] kvm_irq_delivery_to_apic+0x129/0x20f [kvm]
Aug 25 20:27:18 Tower kernel: [<ffffffffa0065bff>] kvm_lapic_reg_write+0x336/0x492 [kvm]
Aug 25 20:27:18 Tower kernel: [<ffffffffa0065d9e>] kvm_apic_write_nodecode+0x43/0x49 [kvm]
Aug 25 20:27:18 Tower kernel: [<ffffffffa008bf82>] handle_apic_write+0x19/0x20 [kvm_intel]
Aug 25 20:27:18 Tower kernel: [<ffffffffa0096055>] vmx_handle_exit+0xf9d/0x1035 [kvm_intel]
Aug 25 20:27:18 Tower kernel: [<ffffffffa00528a9>] kvm_arch_vcpu_ioctl_run+0x357/0x1165 [kvm]
Aug 25 20:27:18 Tower kernel: [<ffffffffa008df4c>] ? __vmx_load_host_state.part.27+0x120/0x127 [kvm_intel]
Aug 25 20:27:18 Tower kernel: [<ffffffffa004d088>] ? kvm_arch_vcpu_load+0xea/0x1a0 [kvm]
Aug 25 20:27:18 Tower kernel: [<ffffffffa0042d71>] kvm_vcpu_ioctl+0x178/0x499 [kvm]
Aug 25 20:27:18 Tower kernel: [<ffffffffa00452f5>] ? kvm_vm_ioctl+0x40a/0x6d2 [kvm]
Aug 25 20:27:18 Tower kernel: [<ffffffff810bd85b>] ? __perf_event_task_sched_in+0xd0/0x135
Aug 25 20:27:18 Tower kernel: [<ffffffff81130112>] vfs_ioctl+0x13/0x2f
Aug 25 20:27:18 Tower kernel: [<ffffffff81130642>] do_vfs_ioctl+0x49c/0x50a
Aug 25 20:27:18 Tower kernel: [<ffffffff8113921f>] ? __fget+0x72/0x7e
Aug 25 20:27:18 Tower kernel: [<ffffffff811306ee>] SyS_ioctl+0x3e/0x5c
Aug 25 20:27:18 Tower kernel: [<ffffffff8167f537>] entry_SYSCALL_64_fastpath+0x1a/0xa9
Aug 25 20:27:18 Tower kernel: ---[ end trace 4bddda485d1bdd7b ]---

 

Any ideas?

 

Thanks!

tower-diagnostics-20170901-0040.zip

anyone?

I looked at the trace yesterday, had no clue.  The key question though is are your VM's still working normally?

Everything works perfectly as far as I can tell.

Then you have 2 options:

 

1. Get a degree in CoSci, scour through the source code for KVM, disassemble the code for your BIOS and any add-in cards, and use that as a basis to try and put the error into perspective.  Or,
2. Don't worry about it.

 

I'll let you decide  

Edited September 4, 20178 yr by Squid

Hmmm, Option number 1 sound like a solid choice

 

Thanks anyways!