#19169 (CVE-2019-11135 causes Win10 Guests with Q2'19 Intel CPUs to get stuck with "IEM: wrmsr(0x122,0x0`00000003) -> #GP(0)") – Oracle VirtualBox
comment:1 by Socratis, 5 years ago
| Version: | VirtualBox 6.0.10 → VirtualBox 6.0.8 |
|---|
Actually it's VirtualBox>6.0.6, not >6.0.8. Sorry about that.
"Version" corrected.
comment:2 by MGA, 5 years ago
You can add this cpu to the list : Intel(R) Core(TM) i7-9850H CPU @ 2.60GHz
follow-up: 8 comment:6 by Klaus Espenlaub, 5 years ago
The fix is also in 6.1.4. Silently, because no one confirmed whether it really does what it should.
comment:7 by sgadsby, 5 years ago
Yes appears to be working for me in 6.1.4. I have successfully installed latest Windows Update and shutdown/start a couple of times.
C:\Program Files\Oracle\VirtualBox>VBoxManage.exe showvminfo "W10.C" |find "CPUProfile" CPUProfile: host
I have not tested 6.0.17.
in reply to: 8 comment:9 by fth0, 5 years ago
Replying to jbnixdorf:
Replying to klaus:
The fix is also in 6.1.4. Silently, because no one confirmed whether it really does what it should.
I answered in the forum that 6.0.17 is not working for me, none of my VMs are starting any more: https://forums.virtualbox.org/viewtopic.php?f=2&t=95783&start=45#p470440
Your tests with test build 6.0.17 show a totally different error (vboxdrv being stuck, reported in the VBoxHardening.log).
Do you still have the problem indicated by the bug title ('wrmsr(0x122, ...', reported in VBox.log)?
comment:10 by jbnixdorf, 5 years ago
I now updated to the latest version 6.1.10 and for me the issue is fixed.