Currently, I am using VirtualBox 6.1.2. I tried to install Windows 10 64bit guest on my Windows 10 64bit host.
I follow the direction of this topic--I have a 64bit host, but can't install 64bit guests.
The screen stucks at the windows logo and will not process further.
In the log file, it stops after HyperV messages:
00:00:02.534096 ERROR [COM]: aRC=VBOX_E_VM_ERROR (0x80bb0003) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=-37
00:00:02.583596 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0 flags=0x0 origin=0,0
00:00:02.583777 VMMDev: Guest Log: CPUID EDX: 0x178bfbff
00:00:02.584468 VMMDev: Guest Log: BIOS: No PCI IDE controller, not probing IDE
00:00:02.584688 AHCI#0: Reset the HBA
00:00:02.584693 VD#0: Cancelling all active requests
00:00:02.584722 AHCI#0: Port 0 reset
00:00:02.584774 VD#0: Cancelling all active requests
00:00:02.585187 VMMDev: Guest Log: BIOS: AHCI 0-P#0: PCHS=16383/16/63 LCHS=1024/255/63 0x000000000a000000 sectors
00:00:02.585225 AHCI#0: Port 1 reset
00:00:02.585794 PIT: mode=2 count=0x48d3 (18643) - 64.00 Hz (ch=0)
00:00:02.639206 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=000000000cbc0000 w=640 h=480 bpp=32 cbLine=0xA00 flags=0x0 origin=0,0
00:00:03.023733 GUI: UIMachineViewNormal::resendSizeHint: Restoring guest size-hint for screen 0 to 800x600
00:00:03.032683 GUI: 2D video acceleration is disabled
00:00:03.032817 GUI: HID LEDs sync is enabled
00:00:03.048964 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=5
00:00:05.081230 PIT: mode=2 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:00:05.081557 VMMDev: Guest Log: BIOS: Boot : bseqnr=1, bootseq=0023
00:00:05.086644 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0 flags=0x0 origin=0,0
00:00:05.086911 VMMDev: Guest Log: BIOS: Booting from CD-ROM...
00:00:05.300439 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=000000000cbc0000 w=1024 h=768 bpp=24 cbLine=0xC00 flags=0x0 origin=0,0
00:00:07.981110 GIM: HyperV: Guest OS reported ID 0x1040a0000271b
00:00:07.981129 GIM: HyperV: Open-source=false Vendor=0x1 OS=0x4 (Windows NT or derivative) Major=10 Minor=0 ServicePack=0 Build=10011
00:00:07.981149 GIM: HyperV: Enabled hypercall page at 0x0000000000281000
Also got this error--VBOX_E_VM_ERROR before the HyperV messages.
I tried disable the Hyper-V for the current session using the following command:
bcdedit /set hypervisorlaunchtype off
The current bcdedit:
Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.efi
description Disable Hyper-V
locale en-US
inherit {bootloadersettings}
recoverysequence {994be326-ed7a-11e9-90ad-98fa9bbc3667}
displaymessageoverride Recovery
recoveryenabled Yes
badmemoryaccess Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \Windows
resumeobject {94fd661d-ed7f-11e9-a39f-98fa9bbc3667}
nx OptIn
bootmenupolicy Standard
hypervisorlaunchtype Off
Please advice what else do I need to do before trying to install the Windows 10 64bit guest.
Thanks much in advance,
Cho
Cannot install Windows 10 64bit Guest on Windows 10 64Bit Host
Re: Cannot install Windows 10 64bit Guest on Windows 10 64Bit Host
Thanks, mpack.
I read the "I have a 64bit host, but can't install 64bit guests" you have mentioned.
I followed all the instructions on that topic.
After carefully researched on the log messages, I, however, found this bug corresponding with this ticket #19169.
CVE-2019-11135 causes Win10 Guests with Q2'19 Intel CPUs to get stuck with "IEM: wrmsr(0x122,0x0`00000003
My machine CPU is Intel Core i5-8365U.
What else can I do? Is it already fixed? Why am I still getting this error?
I am currently using VirtualBox 6.1.2.
Thanks,
Cho
- Attachments
-
- VBoxLogs.zip
- (134.46 KiB) Downloaded 64 times
Re: Cannot install Windows 10 64bit Guest on Windows 10 64Bit Host
According to this topic--Virtualbox 6.1 - Windows 10 Pro 1909 Hangs at startup after applying MS KB4524570--changing the CPU profile workaround does it.
"C:\Program Files\Oracle\VirtualBox\VBoxManage" modifyvm VMname --cpu-profile "Intel Core i7-6700K"
Thanks mpack, socratis, and pt58.
"C:\Program Files\Oracle\VirtualBox\VBoxManage" modifyvm VMname --cpu-profile "Intel Core i7-6700K"
Thanks mpack, socratis, and pt58.
-
- Oracle Corporation
- Posts: 793
- Joined: 7. Jan 2008, 16:17
Re: Cannot install Windows 10 64bit Guest on Windows 10 64Bit Host
This looks like Windows 10 is writing to IA32_TSX_CTRL without properly verifying if the MSR is available.
Please provide feedback if the following test build works:
Windows host:
https://www.virtualbox.org/download/tes ... 50-Win.exe
Linux (64-bit) host:
https://www.virtualbox.org/download/tes ... _amd64.run
Links expire automatically in ~14 days.
Make sure to undo any CPU profile changing you may have applied previously before testing it.
Please provide feedback if the following test build works:
Windows host:
https://www.virtualbox.org/download/tes ... 50-Win.exe
Linux (64-bit) host:
https://www.virtualbox.org/download/tes ... _amd64.run
Links expire automatically in ~14 days.
Make sure to undo any CPU profile changing you may have applied previously before testing it.
Oracle Corp.
Re: Cannot install Windows 10 64bit Guest on Windows 10 64Bit Host
Is a patch coming for VMBox 6.1? I am seeing the same problem running 6.1.2.
Also, what is the recommended best way to undu any CPU profile changes?
Also, what is the recommended best way to undu any CPU profile changes?
Re: Cannot install Windows 10 64bit Guest on Windows 10 64Bit Host
We have at least one thread in parallel talking about the same issue which is mentioned in the bug report in first place:
viewtopic.php?f=2&t=95783
I think it would make sense to stop here and continue with the discussion in the main thread if all information is also available there.
viewtopic.php?f=2&t=95783
I think it would make sense to stop here and continue with the discussion in the main thread if all information is also available there.