Again: Turning off hyper-v is no option for most of us.
jruhe
jruhe wrote:Again: Turning off hyper-v is no option for most of us.
Call to WHvSetupPartition failed: ERROR_SUCCESS (Last=0xc000000d/87) (VERR_NEM_VM_CREATE_FAILED).
Код ошибки: E_FAIL (0x80004005)
Компонент: ConsoleWrap
Интерфейс: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
if (g_pfnVidMessageSlotMap(hPartitionDevice, &MappedMsgSlot, iCpu))
mov rcx, 200000000h
test [rdi+10h], rcx
short loc_FFFFF80441B83F27
WINDBG>dq @rdi
ffffc804`e99d2000 00000000`6e747250 00000000`00000000
ffffc804`e99d2010 00000002`00200244 00000000`00000000
test [rdi+10h], rcx
ffffd881`69a0bdc0 fffff804`3ec86ff4 0xfffff804`3e920003
ffffd881`69a0bdc8 fffff804`3ec8701a nt!HvcallpExtendedFastHypercall+0x54
ffffd881`69a0bdd8 fffff804`3ee007e7 nt!HvcallpExtendedFastHypercallWithOutput+0x1a
ffffd881`69a0bdf0 fffff804`41bd9cfa nt!HvcallFastExtended+0x27
ffffd881`69a0be30 fffff804`41bdb635 winhvr!WinHvpDispatchVp+0x92
ffffd881`69a0bec0 fffff804`41bdb0ec winhvr!WinHvpVpDispatchLoop+0x225
ffffd881`69a0bfa0 fffff804`41b56823 winhvr!WinHvRunVpDispatchLoop+0x4c
ffffd881`69a0bfe0 fffff804`41b564a7 Vid!VidXSchedulerpVpRun+0x73
ffffd881`69a0c010 fffff804`41b89036 Vid!VidXSchedulerVpRun+0x1f
ffffd881`69a0c050 fffff804`41b531e9 Vid!VidVpRun+0x11a
ffffd881`69a0c080 fffff804`41b53fa3 Vid!VidIoControlFastPartition+0x10f1
ffffd881`69a0c410 fffff804`41b52a94 Vid!VidExoFastIoControlPartition+0x21f
ffffd881`69a0c4f0 fffff804`418d2ba6 Vid!VidIoControlFast+0xb54
ffffd881`69a0c5a0 fffff804`43e3d7c9 VBoxDrv+0x12ba6
ffffd881`69a0c640 fffff804`43e3dcb2 VMMR0!REMFlushTBs+0x7749
ffffd881`69a0c6e0 fffff804`43d77ce3 VMMR0!REMFlushTBs+0x7c32
ffffd881`69a0c7a0 fffff804`418c1771 VMMR0!VMMR0EntryFast+0x193
ffffd881`69a0c830 fffff804`418d4ec3 VBoxDrv+0x1771
ffffd881`69a0c860 fffff804`3f0a4d0b VBoxDrv+0x14ec3
ffffd881`69a0c900 fffff804`3f0a45d6 nt!IopXxxControlFile+0x71b
ffffd881`69a0ca20 fffff804`3ec8eb18 nt!NtDeviceIoControlFile+0x56
ffffd881`69a0ca90 00007ffc`c9b5c1a4 nt!KiSystemServiceCopyEnd+0x28 (TrapFrame @ ffffd881`69a0cb00)
Jay-Cee wrote:Well then...I guess that's why no ones posting a success as it doesn't work without the "workaround" >:)
Let me do it: SUCCESS!
[...]
-> Hyper-V -> Hyper-V-Platform -> Hyper-V-Hypervisor "disabled"
#if defined(NEM_WIN_WITH_RING0_RUNLOOP) || defined(NEM_WIN_USE_OUR_OWN_RUN_API)
{
VID_MAPPED_MESSAGE_SLOT MappedMsgSlot = { NULL, UINT32_MAX, UINT32_MAX };
if (g_pfnVidMessageSlotMap(hPartitionDevice, &MappedMsgSlot, iCpu))
{
AssertLogRelMsg(MappedMsgSlot.iCpu == iCpu && MappedMsgSlot.uParentAdvisory == UINT32_MAX,
("%#x %#x (iCpu=%#x)\n", MappedMsgSlot.iCpu, MappedMsgSlot.uParentAdvisory, iCpu));
pVCpu->nem.s.pvMsgSlotMapping = MappedMsgSlot.pMsgBlock;
}
else
{
NTSTATUS const rcNtLast = RTNtLastStatusValue();
DWORD const dwErrLast = RTNtLastErrorValue();
return VMSetError(pVM, VERR_NEM_VM_CREATE_FAILED, RT_SRC_POS,
"Call to WHvSetupPartition failed: %Rhrc (Last=%#x/%u)", hrc, rcNtLast, dwErrLast);
}
}
#endif
#if defined(NEM_WIN_WITH_RING0_RUNLOOP) || defined(NEM_WIN_USE_OUR_OWN_RUN_API)
No, VirtualBox 6.0 running in a Windows 10 Hyper-V root partition can execute both 32-bit and 64-bit VMs, as long as you have a Windows 10 version which is compatible with VirtualBox's code supporting Hyper-V. Currently this is Windows 10 1803 and 1809.
Andrew Brehm wrote:That means waiting for a new version of VirtualBox, I suppose.
Return to VirtualBox on Windows Hosts
Users browsing this forum: Google [Bot] and 46 guests