David used "5.6.0-1042.46-oem", the closest I had was "5.6.0-1052-oem" so I tried that one.
With that my win10 install immediately crashed into the reported issue.
So to summarize:
1. I can reproduce it
2. Chances are high that it is fixed by kernel commit 841c2be0 "kvm: x86: replace kvm_spec_ctrl_test_value with runtime test on the host"
3. there are some qemu changes which might be related, but we need Babu to reply about if/how those are related
I need to get myself updated on Ubuntu oem kernels.
If there is a 5.6 series that is supposed to work on that, then this patch needs to be backported.
But if OTOH it is a valid upgrade path that you'll get the 5.10.0-1020-oem that I had or later as part of your 20.04 OEM then that "is the fix" for you @David.
David used "5.6.0- 1042.46- oem", the closest I had was "5.6.0-1052-oem" so I tried that one.
With that my win10 install immediately crashed into the reported issue.
So to summarize: ctrl_test_ value with runtime test on the host"
1. I can reproduce it
2. Chances are high that it is fixed by kernel commit 841c2be0 "kvm: x86: replace kvm_spec_
3. there are some qemu changes which might be related, but we need Babu to reply about if/how those are related
I need to get myself updated on Ubuntu oem kernels.
If there is a 5.6 series that is supposed to work on that, then this patch needs to be backported.
But if OTOH it is a valid upgrade path that you'll get the 5.10.0-1020-oem that I had or later as part of your 20.04 OEM then that "is the fix" for you @David.