virtualbox.org

---

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

---

Hi,

A Win 10 1909 VM runs perfectly well until I attempt to install Windows Updates. The following single update is pending:

• 2019-11 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4524570)

When this is installed the machine restarts and then hangs at the Windows boot screen.
If I power off the machine and power back on, it hangs at the same point.
After 2-3 goes it automatically rolls back the patch and boots correctly.

Any ideas? It hangs around line 1434 in the attached log.

Thanks,
Simon.

Brand new Win10 VM (same version), fails in the same way with the same update.

For the moment, avoid that update. Thank you for the detective work, trying it on a new installation!

FWIW, I have no problems with Windows 10 1909 as host and/or guest OS in various combinations, using VirtualBox 5.2.34.

Also don't see any problems when using Windows 10 (or MacOS Host) and Windows 10 1903 to 1909, but I don't rely on Windows Update to perform either the version or monthly (Patch Tuesday) updates.

Personally I would recommend downloading and applying these updates directly (having made a secure backup of the VM Folder first, given Microsoft's reputation for releasing 'Patch Tuesday' and version Updates with significant problems.).

e.g. https://www.tenforums.com/windows-10-ne ... 476-a.html or https://support.microsoft.com/en-us/help/4524570

Hello,

I'm using an HP ZBOOK 17 ( an old one ) And this update is not causing problem.
With a brand you Lenovo Thinkpad p52 this update is causing the boot failure.

May be this information can help.

Hello,
first, sorry for my terrible English

Yesterday, I update my DELL BIOS (Dell Precision 7540 Version 1.5.1)

I use Windows 10 Version 1903 64bit as Host.

Then I start Portable VirtualBox with VirtualBox Version 6.0.14 r133895.
Starting an Guest with Windows Server 2018 or Windows Server 2012 works well.

Starting any Windows 10 Guest (Version 1903 32bit and 64 bit) stop working after the blue Window Logo was shown.

[ModEdit; Partial logs removed]

Thank's a lot for Help.

Your English sounds quite fine to me.

Unfortunately we don't support Portable Virtualbox here. You'd have to ask them if you want to use their version.

However, if you want to run fully-installed Virtualbox from http://www.virtualbox.org, without Portable or any other 3rd-party add-on, then we can help.

Once you have official Virtualbox installed, and if a guest does not start, pick one non-starting guest, and zip & post the whole log file using the forum's Upload Attachment tab.

Hi!

I have a new laptop (Lenovo X1 with a Core I9 cpu) and I can't run VM's on it. I copied some vm's from my old desktop and none of them work. I also created a new Win10 vm and that one installed fine. But after the first reboot is shows the same issues as the copied vm's; they all hang on the windows logo during boot; no rotating wait indicator is shown.

I checked the Virtualisation settings in the bios and made sure hyper-v isn't installed on my host. On my desktop pc it was no problem for me to run VMs.

can someone help me? The main reason I bought this core i9-64GB-2TB laptop is to run VM's on it

Hello scottgus1,
Thank's alot lot for your reply.
Tomorrow I install VirtualBox and create the complete Log-File.
Best regards

Dear scottgus1,

I install Version 6.1.0 and get the same Problem, attached the two Log-Files.

Thank's for your Support.

00:00:02.337142 VUSB: Attached 'HidMouse' to port 1 on RootHub#1 (FullSpeed)
00:00:02.337301 VUSB: Attached 'HidMouse' to port 2 on RootHub#1 (FullSpeed)

Not sure how you managed to do that, can't say I've seen two mice attached before. I want to see the recipe of the VM, the ".vbox" file. Right-click on the VM in the VirtualBox Manager, select "Show in Explorer". ZIP the selected ".vbox" file and attach it to your response.

Your VBox.log ends prematurely. Always close the VM, even if it doesn't start, before grabbing the log. Can you please try again, because we can't see the whole picture?


PS. I deleted your cross-post from another thread. You already have a dedicated thread on your own, if it turns out that it's a common theme, a moderator will merge the threads appropriately.

Hi socratis, thanks for your reply.

I'v added the 2 requested files.

as for the 2 mice: it's a thinkpad with a trackpoint and a touchpad. and sometimes a wired or a bluetooth mouse

No hardening issues:

2440.208c: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x0

The log doesn't seem to me to show any starting problems.

However:

00:00:01.695211 Executable: d:\VirtualBox\VirtualBoxVM.exe
.......
'D:\VirtualBox_HDD\VirtualBoxPortable\data\.VirtualBox\Machines\_WIN 10 x64\WIN10-x64.vdi'

Unusual installation location and still possibly corrupted by Portable...

Try a fresh guest run from the main Virtualbox window.

A couple of things that I noticed too...

00:00:01.789655 [/Devices/e1000/0/Config/] (level 4)
00:00:01.789656   AdapterType    <integer> = 0x0000000000000002 (2)
...
00:00:02.267322 E1000#0: Chip=82545EM LinkUpDelay=3000ms EthernetCRC=on GSO=enabled Itr=disabled ItrRx=enabled TID=disabled R0=enabled RC=disabled

Any particular reason why you decided to ignore the template suggested default values for an "Intel PRO/1000 MT Desktop (82540EM)" NIC and went with "Intel PRO/1000 MT Server (82545EM)"?

00:00:01.610613 VirtualBox VM 6.1.0 r135406 win.amd64 (Dec 10 2019 14:34:16) release log
...
00:00:01.319874 [/Devices/vga/0/Config/] (level 4)
00:00:01.319875   3DEnabled        <integer> = 0x0000000000000001 (1)
00:00:01.319876   CustomVideoModes <integer> = 0x0000000000000000 (0)
00:00:01.319876   FadeIn           <integer> = 0x0000000000000001 (1)
00:00:01.319877   FadeOut          <integer> = 0x0000000000000001 (1)
00:00:01.319878   HeightReduction  <integer> = 0x0000000000000000 (0)
00:00:01.319878   LogoFile         <string>  = "" (cb=1)
00:00:01.319879   LogoTime         <integer> = 0x0000000000000000 (0)
00:00:01.319880   MonitorCount     <integer> = 0x0000000000000001 (1)
00:00:01.319880   ShowBootMenu     <integer> = 0x0000000000000002 (2)
00:00:01.319881   VRamSize         <integer> = 0x0000000010000000 (268 435 456, 256 MB)

This is a not a valid setup. You're starting a VM with VBoxVGA+3D enabled. Aren't you getting a warning at start about this? Did you go to the VM Settings and there was no "warning triangle" at the bottom of the dialog? Please go to the VM Settings » Display, and either disable the 3D acceleration, or change the vGPU to "VBoxSVGA". Then the warning will go away as well...

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...