Hi, I tried to run my vm and it gave me error like virtualization, i enabled hyper v and now it gives this error
Failed to open a session for the virtual machine Windows 7 SP1 OVGorskiy.
The VM session was closed before any attempt to power it on.
Result Code: E_FAIL (0x80004005)
Component: SessionMachine
Interface: ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}
Please help
The VM session was closed before any attempt to power it on.
-
- Posts: 7
- Joined: 30. Oct 2022, 15:26
The VM session was closed before any attempt to power it on.
- Attachments
-
- VBox.log
- Logs
- (27.84 KiB) Downloaded 2 times
-
- Posts: 7
- Joined: 30. Oct 2022, 15:26
Re: The VM session was closed before any attempt to power it on.
P.S. Im not gonna install another versions of virtual box. I want to stay on 6th version
-
- Posts: 7
- Joined: 30. Oct 2022, 15:26
Re: The VM session was closed before any attempt to power it on.
UPD: I run virtualbox as administrator now it gives me windows hypervisor platform issues, i have russian windows 10 and i cant find windows hypervisor platofrm in optional features, heres screenshots
- Attachments
-
- изображение_2022-11-20_114212940.png (7.03 KiB) Viewed 733 times
-
- изображение_2022-11-20_114149076.png (4.95 KiB) Viewed 733 times
-
- изображение_2022-11-20_114124021.png (8.5 KiB) Viewed 733 times
-
- Posts: 7
- Joined: 30. Oct 2022, 15:26
Re: The VM session was closed before any attempt to power it on.
UPD: Its still issue with hypervisor, i turned off sandbox, hyper v, still nothing
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: The VM session was closed before any attempt to power it on.
To be clear: enabling Hyper-v will pretty much guarantee a conflict with VirtualBox. The best setting is off, not on.
The only log you have provided shows Hyper-v off, and VT-x not available. So either you enabled Hyper-v but didn't boot the PC, or VT-x is being used by something else - e.g. non Microsoft AV, or VT-x is not enabled in the PC BIOS.
The only log you have provided shows Hyper-v off, and VT-x not available. So either you enabled Hyper-v but didn't boot the PC, or VT-x is being used by something else - e.g. non Microsoft AV, or VT-x is not enabled in the PC BIOS.
See also FAQ: I have a 64bit host, but can't install 64bit guests.00:00:08.549557 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:00:08.765621 NEM: info: Found optional import WinHvPlatform.dll!WHvQueryGpaRangeDirtyBitmap.
00:00:08.784029 VMSetError: F:\tinderbox\win-6.1\src\VBox\VMM\VMMR3\NEMR3Native-win.cpp(1460) int __cdecl nemR3NativeInit(struct VM *,bool,bool); rc=VERR_NEM_NOT_AVAILABLE
00:00:08.784410 VMSetError: WHvCapabilityCodeHypervisorPresent is FALSE! Make sure you have enabled the 'Windows Hypervisor Platform' feature.
00:00:08.784496 NEM: NEMR3Init: Native init failed: VERR_NEM_NOT_AVAILABLE. {i.e. Hyper-v not available}.
00:00:08.784514 VMSetError: F:\tinderbox\win-6.1\src\VBox\VMM\VMMR3\HM.cpp(630) int __cdecl HMR3Init(struct VM *); rc=VERR_VMX_NO_VMX
00:00:08.784593 VMSetError: VT-x is not available
00:00:08.785817 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={WHvCapabilityCodeHypervisorPresent is FALSE! Make sure you have enabled the 'Windows Hypervisor Platform' feature. (VERR_NEM_NOT_AVAILABLE).
00:00:08.785894 VT-x is not available (VERR_VMX_NO_VMX)}, preserve=false aResultDetail=-4009