VirtualBox

Opened 5 years ago

Last modified 4 years ago

#18629 new defect

Failed to open a session for the virtual machine vm1.

Reported by: rolevsky Owned by:
Component: other Version: VirtualBox 6.0.6
Keywords: Cc:
Guest type: other Host type: Windows

Description

win 10 - pro version 1903 - fast ring updates

Failed to open a session for the virtual machine vm1.

Call to WHvSetupPartition failed: ERROR_SUCCESS (Last=0xc000000d/87) (VERR_NEM_VM_CREATE_FAILED).

Result Code: E_FAIL (0x80004005) Component: ConsoleWrap Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

Attachments (2)

VBox.log (34.7 KB ) - added by RockyM 4 years ago.
VBox log created when trying to start
VBoxHardening.log (377.4 KB ) - added by RockyM 4 years ago.
VBoxHardening log when trying to start

Download all attachments as: .zip

Change History (5)

comment:1 by Socratis, 5 years ago

  1. It's usually better and faster, if issues get first addressed in the VirtualBox forums, a lot more eyes there. More than 95% of the issues are resolved in the forums, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is most probably not a bug and someone from the developers has to deal with it and close it as "Invalid".

Plus a discussion and analysis on the bug tracker is going to help me, you, and potentially a future drive-by user or two. Not so in the forums, many more tend to benefit...

  1. You were supposed to follow these steps when you filed the bug, and provide a VBox.log:

    Attach a (full) log file ("Machine" menu/"Show Log" in the main VirtualBox Manager window) straight away to save time for you and for us. The log file contains a lot of useful information about both the host and the guest systems as well as information about what happened during a particular machine run. Please do not cut and paste it.

by RockyM, 4 years ago

Attachment: VBox.log added

VBox log created when trying to start

by RockyM, 4 years ago

Attachment: VBoxHardening.log added

VBoxHardening log when trying to start

comment:2 by RockyM, 4 years ago

I try to install Linux - I've tried Fedora and Linux with the same result. I have uninstalled and re-installed Virtualbox. I set it up with 8GB of RAM, 80GB of stroage. 4 CPU's - assign the .iso to the DVD on storage, everything else is default.

My machine has 32 GB of RAM, 8 core, 16 thread Ryzen.

I get these errors but I do have the logs, hopefully this helps.

comment:3 by Frank Batschulat (Oracle), 4 years ago

Host type: otherWindows

The newly attached log:
https://www.virtualbox.org/attachment/ticket/18629/VBox.log[[BR]] shows this error with VirtualBox VM 6.0.18 r136238

638	00:00:01.811156 VMSetError: F:\tinderbox\win-6.0\src\VBox\VMM\VMMR3\NEMR3Native-win.cpp(1463) int __cdecl nemR3NativeInitAfterCPUM(struct VM *); rc=VERR_NEM_VM_CREATE_FAILED 
639	00:00:01.811190 VMSetError: Call to WHvSetupPartition failed: ERROR_SUCCESS (Last=0xc000000d/87) 
640	00:00:01.811234 NEM: Destroying partition 00000000019124e0 with its 0 VCpus... 
641	00:00:01.990865 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Call to WHvSetupPartition failed: ERROR_SUCCESS (Last=0xc000000d/87) (VERR_NEM_VM_CREATE_FAILED)}, preserve=false aResultDetail=-6805 
642	00:00:01.991045 Console: Machine state changed to 'PoweredOff' 
643	00:00:01.993433 Power up failed (vrc=VERR_NEM_VM_CREATE_FAILED, rc=E_FAIL (0X80004005)) 
644	00:00:02.494686 GUI: UIMachineViewNormal::resendSizeHint: Restoring guest size-hint for screen 0 to 800x600 
645	00:00:02.494728 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={ab4164db-c13e-4dab-842d-61ee3f0c1e87} aComponent={DisplayWrap} aText={The console is not powered up}, preserve=false aResultDetail=0 
646	00:00:02.494901 GUI: Aborting startup due to power up progress issue detected...
Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use