Hi all,
yesterday I closed the VM correctly but today it prompted the error reported here:doh...
failed to open a session for the virtual machine win 7
VT-X is not available. (VERR_VMX_NO_VMX).
result code: e_fail (0x80004005)
component: console
interface: iconsole "
I disabled the hyperv as suggested and did all followed all the oder advices...enebled the vtx virtualization...but now, when I start the VM, it goes in a loop: windows loading files...
I don't know what happened and I don't know how to solve.
can please someone help me or suggest me the right way to resolve?
thank you
Newbie here...sorry I have a problem :(
Re: Newbie here...sorry I have a problem :(
resolved
i created a new vm and attached the old disk...doh
i created a new vm and attached the old disk...doh
Re: Newbie here...sorry I have a problem :(
Could you please details the steps that helped fix your issue? I got the below error.
Failed to open a session for the virtual machine .
VT-x is not available (VERR_VMX_NO_VMX).
Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
Failed to open a session for the virtual machine .
VT-x is not available (VERR_VMX_NO_VMX).
Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Mostly XP
Re: Newbie here...sorry I have a problem :(
Please read the following FAQ, it deals with a closely related issue. FAQ: I have a 64bit host, but can't install 64bit guests.
I don't recommend that you try the OPs solution, which has no relevance that I can think of. I suspect that his actual "fix" was something else he did along the way, e.g. rebooting the host.
I don't recommend that you try the OPs solution, which has no relevance that I can think of. I suspect that his actual "fix" was something else he did along the way, e.g. rebooting the host.