virtualbox.org

Question:

Would it be a good test to downgrade the bios of my laptop to a certain version?

(Bios changelist is on the bottom of this page: https://pcsupport.lenovo.com/nl/en/prod ... s/ds540308 )

edit: nevermind,
I can only downgrade 1 version:
- If the UEFI BIOS has been updated to version 1.26 or higher,
it is no longer able to roll back to the version before 1.26.

socratis wrote:

00:00:07.800331 IEM: wrmsr(0x122,0x0`00000003) -> #GP(0)
00:01:01.816180 GUI: Request to close active machine-window.

Something MSR related again...

MSR 0x122 is IA32_TSX_CTRL. This is related to Intel Transactional System Extensions which VirtualBox doesn't support. Its possible that the guest is writing to that MSR without checking its capability bit in MSR_IA32_ARCH_CAPABILITIES (0x10a, bit 7). The guest is writing bits 0 and 1 which seem to be "disable" and "clear"....

Ramshankar wrote:Its possible that the guest is writing to that MSR without checking its capability bit in MSR_IA32_ARCH_CAPABILITIES (0x10a, bit 7).

That's what I also suspected (just like in the cases with xBSD guests and the SPEC_CTRL MSR). My assumptions so far:

• Intel CPUs with CPU family 6 and CPU model 0x9e/0x8e/0x55, running an up-to-date Windows/Linux host OS, have the 2019-11-12 Intel microcode update applied that adds the IA32_TSX_CTRL MSR.
• An up-to-date Windows 10 1903/1909 guest OS accesses the IA32_TSX_CTRL MSR without checking the IA32_ARCH_CAPABILITIES MSR first.

The problem at hand seems to occur only when using VirtualBox versions newer than 6.0.6. Which changes between VirtualBox 6.0.6 and 6.0.8 could influence the behavior? Have there been changes in the CPUID/MSR area?

Ramshankar wrote:The guest is writing bits 0 and 1 which seem to be "disable" and "clear"....

You can find a description of those bits following the first link in viewtopic.php?f=2&t=95783&start=15#p465495 (if you've not seen it already ).

taking the risk of looking a bit silly to you,
Do we have to wait for a new version or is it a configuration problem?
I don't see any traces of this problem in the bug thread.

mga wrote:Do we have to wait for a new version or is it a configuration problem?

It's a hardware issue (microcode update for the CPUs), that only applies to newer Intel CPUs. You'll have to wait for the developers to debug it and apply a fix. It's definitely not a configuration problem. You'd wish...

mga wrote:I don't see any traces of this problem in the bug thread.

Because nobody opened a ticket yet!

I'll open one and tie it to the thread...

Ticket #19169: CVE-2019-11135 causes Win10 Guests with Q2'19 Intel CPUs to get stuck with "IEM: wrmsr(0x122,0x0`00000003) -> #GP(0)".

This affects all VirtualBox > 6.0.8, hence the 6.0.10 version assigned.

Shouldn't that be => 6.0.8 or > 6.0.6 ?

mga wrote:6.0.8 : crash
6.0.6 : no crash, vm is booting normally.

Ticket [url=https://www.virtualbox.org/ticket/19169]#19169[/url] wrote:This affects all VirtualBox > 6.0.8, hence the 6.0.10 version assigned.

doezel wrote:Shouldn't that be => 6.0.8 or > 6.0.6 ?

D'oh!
I fixed the ticket as much as I could. I need either more coffee or more sleep. I think I'll go with the latter...

Thanks 'doezel' for catching this! And a big thanks to 'mga' for all the detective work and the bisection!

Thanks to you socratis.

I see Windows10 updates and upgrades as dangerous tasks because we can't predict what losses or problems will result from failure,there are some bugs in Windows 10 updates or upgrades.There's no denying it. At least I'm not going to try it myself. I don't have any experience with it.

I am sure glad I found this post as this issue has been causing me loos of sleep as I could not get Windows 10 guest or a Windows 7 guest running on my Windows 10 host to boot on a i9-9900K CPU host PC.

Downgraded to 6.0.6 and yes, I am back up and running fine with both Win 10 and Win 7 guest VM's.

I would like to reply and confirm that Windows 10 Guest with update KB4530684 hangs on boot. Just recently upgraded to Cascade Lake-X from Skylake-X.

as a temporary workaround I found that a technique mentioned in another thread worked here, but here is the command
Doing this allows me to continue to use the latest version of Virtualbox while still allowing me to use updated vms

TimFromFL wrote:as a temporary workaround I found that a technique mentioned in another thread worked here, but here is the command

Code: Select all

"C:\Program Files\Oracle\VirtualBox\VBoxManage" modifyvm VMname --cpu-profile "Intel Core i7-6700K"

Doing this allows me to continue to use the latest version of Virtualbox while still allowing me to use updated vms

Thanks for confirming that this does actually work.
It was a theory I put forward, but with no way of verifying because I couldn't test it on a recent Intel CPU host.

Hello,

Workaround with Changing Profile work for me too.

Virtualbox 6.0.14 with Intel Xeon E2286M

Thanks for the great Support!