virtualbox.org

Hello,
first time on this forum...I have a recently installed Virtual Box / Ubuntu VM on a Windows 7 64 bit laptop(Sony), which was working fine when I shut down yesterday. I am seeing the following error code when I attempt to start the VM today:

Result Code:
E_FAIL (0x80004005)
Component:
Console
Interface:
IConsole {db7ab4ca-2a3f-4183-9243-c1208da92392}

It seems to be saying there is some locked resource that is needed to continue...can anyone point me in the direction of fixing this issue? One possible clue: I had another VM running in VMware at the same time last time everything was working, as I am in the process of transitioning that VM to Virtual Box. Both VM's have access to the same shared C:/Shared directory, but this problem does not look like a file system issue...but then what do I know, if I actually knew something, i wouldn't have to be asking here!

Thanks in advance for any and all ideas to try.
Bill Martin

Please post the VM log file as a zipped attachment. The log must be of a completed failed session (i.e. taken after the VM is shut down). The VM log file is called "VBox.log", and can be found in the "Logs" subfolder of your VM folder.

Hello "mpack",

Here's the log file, thanks for your assistance.

Bill

VBox.log wrote: 00:00:04.986620 Power up failed (vrc=VERR_VMX_MSR_LOCKED_OR_DISABLED, rc=E_FAIL (0X80004005))

MSR_LOCKED_OR_DISABLED means that you have VT-x enabled in this VM, but VT-x is not available. This could be because you have not enabled it in your BIOS, or it could be because another VT-x client is already running on your host PC (only one is allowed). The latter could be another VM platform or a debugger.

Thank you, it seems to have happened when I tried to use more than one cpu core. as soon as that was set back to "1", with VT-x still checked, it booted successfully. I'll have a look at bios settings next time I start up from really off condition.

Bill

I had what appears to be exactly the same error message:

Result Code: E_FAIL (0x80004005)
Component:
Console Interface:
Console {db7ab4ca-2a3f-4183-9243-c1208da92392}

I was attempting to start an XP Pro VM.

My solution was to open virtualbox, right-click the virtual machine and choose 'Discard saved state..."; restarted perfectly.

I am having trouble starting Virtual box. Ran it 2 weeks ago and all was fine. Tried to open it this morning and received a 0x80004005 error

103 path not found.

no changes were made to the path.

The SSD is in the G port and it seems that it is looking for the files in the E port. I change the path to look at G and it doesn't seem to make any difference. running 4.2.8, Wind 7 system.


any ideas?? thanks.

@Ellen. Please do not hijack someone else's discussion. Start your own topic to discuss your problem, and also read Minimum information needed for assistance.

Greetings, I am getting the same error: Failed to open a session for the virtual machine /machine-name/. VT-x is disabled in the BIOS. (VERR_VMX_MSR_VMXON_DISABLED).

Details:

Result Code: E_FAIL (0x80004005)
Component: Console
Interface: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}

I read that to fix this problem I need to change the VT-x settings in BIOS. How do I do that, can you provide detailed instructions?

No, we can't provide detailed instructions. That needs to come from your PC user manual or vendor

Hi, i have the same issue in each case after start of my VMs (one win xp and 3 Oracle Linux) all of them crashed with the same error. Please help, as i don`t want to reinstall them)
version of VB release: 4.3.16 r95972
it happend after reinstall of main os (from one windows 7 to another win7 from the same distributive). I thought may be the reason in version of Virtual Box. I have tried to reinstall it on the previous version but it did not help me. Also i tried to perform the solution mentioned from this topic and to change 2 cpu on 1. But it also had no succes.

• error code:
  E_FAIL (0x80004005)
  component:
  Machine
  Interface:
  IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

The pictured error is not close to being the same as the one discussed above. Above is a "VT-x disabled" problem, whereas you have one of the standard "hardening" issues - see "security issues" discussion at the top of his forum. Fix it by downgrading to 4.3.12, or try the 4.3.19 test build.

Incidentally, the log you posted shows a different problem yet again: apparantly you downgraded to 4.3.12 and then discovered that saved states are not backwards compatible. Not a problem - right click VM and discard the saved state.

mpack wrote:The pictured error is not close to being the same as the one discussed above. Above is a "VT-x disabled" problem, whereas you have one of the standard "hardening" issues - see "security issues" discussion at the top of his forum. Fix it by downgrading to 4.3.12, or try the 4.3.19 test build.

Incidentally, the log you posted shows a different problem yet again: apparantly you downgraded to 4.3.12 and then discovered that saved states are not backwards compatible. Not a problem - right click VM and discard the saved state.

Thanks, dude. Downgrade to 4.3.12 version helped to solve this issue. You are awesome.