https://bugs.winehq.org/show_bug.cgi?id=40240
--- Comment #3 from François Gouget fgouget@codeweavers.com --- It turns out that the ntdll:exception Windows crash on wtbw1064 produces the following kernel error messages on the host:
Dec 16 13:43:48 vm3 kernel: [ 191.624802] kvm [2064]: vcpu0, guest rIP: 0xfffff803cb3c0bf3 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 16 13:43:48 vm3 kernel: [ 191.624835] kvm [2064]: vcpu0, guest rIP: 0xfffff803cb3c0c5c unhandled rdmsr: 0x1c9
This happens even with QEMU 1:2.7+dfsg-3~bpo8+2 and linux-image 4.7.8-1~bpo8+1. Fortunately looking up these messages turns up the following workaround which lets ntdll:exception succeed.
echo 1 >/sys/module/kvm/parameters/ignore_msrs
https://www.reddit.com/r/VFIO/comments/42dj7n/some_games_crash_to_biosboot_o...
Todo: 1) Make sure the echo will be performed on boot, on all VM hosts so the Windows 10 VM can be moved around at will. 2) Report this QEMU issue if it has not been reported yet. 3) This implies checking whether this issue is specific to Intel hosts or if it also happens on AMD ones (vm2). 4) Check whether it also happens on my TestBot rig. 5) I seem to remember the crash did not happen on the Windows 7 and 8.1 VMs that were upgraded to Windows 10. Double-check, on a host know to have the above issue (e.g. vm3). 6) Record the relevant QEMU bug(s) here so we can keep track of them.