VBoxManage.exe: error: The virtual machine 'mongod-m103' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005)

Not sure why this is happening, I’ve tried google.stackoverflow but with no luck. Any ideas?

More command prompt:

C:\Users\021454\Desktop\Nebuchadnezzar\m103\m103-vagrant-env>vagrant up --provision
Bringing machine ‘mongod-m103’ up with ‘virtualbox’ provider…
==> mongod-m103: Clearing any previously set forwarded ports…
==> mongod-m103: Clearing any previously set network interfaces…
==> mongod-m103: Preparing network interfaces based on configuration…
mongod-m103: Adapter 1: nat
mongod-m103: Adapter 2: hostonly
==> mongod-m103: Forwarding ports…
mongod-m103: 22 (guest) => 2222 (host) (adapter 1)
==> mongod-m103: Running ‘pre-boot’ VM customizations…
==> mongod-m103: Booting VM…
There was an error while executing VBoxManage, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: [“startvm”, “d9f0e09d-d128-4d50-9b89-ca69af8f0118”, “–type”, “headless”]

Stderr: VBoxManage.exe: error: The virtual machine ‘mongod-m103’ has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in ‘C:\Users\021454\VirtualBox VMs\mongod-m103\Logs\VBoxHardening.log’
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine

C:\Users\021454\Desktop\Nebuchadnezzar\m103\m103-vagrant-env>vagrant ssh
VM must be running to open SSH connection. Run vagrant up
to start the virtual machine.

Thank you

Maybe one of these suggestions:

https://stackoverflow.com/questions/32686280/there-was-an-error-while-executing-vboxmanage-a-cli-used-by-vagrant-for-contr

1 Like

And a lot of the time the same problem has been experienced by other students and at some point solved. So remember to search the discussion board.

In addition, this scenario was covered in Chapter 0 - Troubleshooting the Vagrant Environment

1 Like

Hi @Nicholas_90117,

Please take a look at the following thread for reference and see if it can be of any help to you.

Thanks,
Muskan
Curriculum Support Engineer

1 Like

Hello @Jennifer_45288

Thank you for your response. I attempted to both change my environment variables and stopping the VM in the GUI. But this didn’t solve the issue.

Hello @007_jb

Thank you for your response.

I did go through those troubleshooting suggestions, with no luck.

Hello @Muskan_47318

Thank you for your response.

I also found this suggestion, “deselecting Hyper-V in Windows Features” and double checked now to confirm it’s deselected.

Still having the same issue.

Hi @Nicholas_90117, just to confirm, you’ve also turned on Virtualization in the BIOS settings?

And have you looked in the log file?
C:\Users\021454\VirtualBox VMs\mongod-m103\Logs\VBoxHardening.log

If you haven’t already, please mention your OS and version.

Here’s more detail from the logs that Virtual Box creates:

3214.1a58: \SystemRoot\System32\kernel32.dll:
3214.1a58: CreationTime: 2019-09-06T07:25:37.367667900Z
3214.1a58: LastWriteTime: 2019-04-19T10:54:56.743034000Z
3214.1a58: ChangeTime: 2019-10-21T22:08:52.436688600Z
3214.1a58: FileAttributes: 0x20
3214.1a58: Size: 0xafd48
3214.1a58: NT Headers: 0xe8
3214.1a58: Timestamp: 0xda2d7146
3214.1a58: Machine: 0x8664 - amd64
3214.1a58: Timestamp: 0xda2d7146
3214.1a58: Image Version: 10.0
3214.1a58: SizeOfImage: 0xb1000 (724992)
3214.1a58: Resource Dir: 0xaf000 LB 0x520
3214.1a58: [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
3214.1a58: [Raw version resource data: 0xaf0b0 LB 0x3a4, codepage 0x0 (reserved 0x0)]
3214.1a58: ProductName: Microsoft® Windows® Operating System
3214.1a58: ProductVersion: 10.0.17134.753
3214.1a58: FileVersion: 10.0.17134.753 (WinBuild.160101.0800)
3214.1a58: FileDescription: Windows NT BASE API Client DLL

Hi @007_jb

I did confirm that Intel Virtualization Technology is enabled in my BIOS. and I looked in the log file. (see above comment)

I’m using Windows 10 Enterprise Version 1803 OS build 17134.1069

I was on my mobile phone earlier so couldn’t respond sooner.

Do you have admin privileges on this machine? If you do try and run the Windows Shell as Administrator.
And if it’s a work machine, I wonder if your Sys Admins have set a policy to disallow installations of VMs.

Please try the above, and if you don’t have much luck, run this (as Admin) to see the log for vagrant:

vagrant destroy
vagrant up --provision --debug

I do have admin privileges on my machine, I’m sure my sys admins have put loads of restrictions in place.

I ran the two line you requested, and the length of the debug is massive, not sure what will be useful to you, but I got the same error at the bottom:

Command: [“startvm”, “6a7fa567-18ef-457c-9bf9-1d5b25feb5c1”, “–type”, “headless”]

Stderr: VBoxManage.exe: error: The virtual machine ‘mongod-m103’ has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in ‘C:\Users\021454\VirtualBox VMs\mongod-m103\Logs\VBoxHardening.log’
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine

There was an error while executing VBoxManage, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: [“startvm”, “6a7fa567-18ef-457c-9bf9-1d5b25feb5c1”, “–type”, “headless”]

Stderr: VBoxManage.exe: error: The virtual machine ‘mongod-m103’ has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in ‘C:\Users\021454\VirtualBox VMs\mongod-m103\Logs\VBoxHardening.log’
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine
INFO interface: Machine: error-exit [“Vagrant::Errors::VBoxManageError”, “There was an error while executing VBoxManage, a CLI used by Vagrant\nfor controlling VirtualBox. The command and stderr is shown below.\n\nCommand: [“startvm”, “6a7fa567-18ef-457c-9bf9-1d5b25feb5c1”, “–type”, “headless”]\n\nStderr: VBoxManage.exe: error: The virtual machine ‘mongod-m103’ has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in ‘C:\Users\021454\VirtualBox VMs\mongod-m103\Logs\VBoxHardening.log’\r\nVBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine\r\n”]

Yes it looks the same. Do you see anything useful just before these lines?

This goes on for a few hundred lines(just before the above):
ERROR vagrant: C:/HashiCorp/Vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/plugins/providers/virtualbox/driver/version_5_0.rb:726:in block in start' C:/HashiCorp/Vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/util/retryable.rb:17:in retryable’
C:/HashiCorp/Vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/plugins/providers/virtualbox/driver/version_5_0.rb:716:in start' C:/HashiCorp/Vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/plugins/providers/virtualbox/action/boot.rb:16:in call’
C:/HashiCorp/Vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/warden.rb:50:in call' C:/HashiCorp/Vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/builtin/before_trigger.rb:23:in call’
C:/HashiCorp/Vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/warden.rb:50:in `call’

Pipe it into a file and share it via a file share link. That way the Curriculum Engineers will have the full log too.

It’s a big one: https://pastebin.com/CrV9LQ0Q

I waited to long to complete the Labs, so I’ll fail the course. Guess I’ll come back later. Thanks for your help and effort @007_jb

It was a pretty lengthy file indeed! Nothing jumps out at me. The headless mode of VBox allows a VM to run from inside a terminal via SSH so I believe something is blocking this from happening because that’s where it’s failing. Your machine either needs a Windows patch or your Sys Admins have blocked this somehow. I suggest that you get in touch with your IT Support Desk to have your system updated (if necessary) and for them to install it (if they agree).

Another thing you could try is uninstalling and installing the latest version of VBox. Remember to reboot each time.

No problem! Hopefully you’ll be up and running before the next session.

Hi @Nicholas_90117,

Sorry to hear that you weren’t able to resolve this issue and had to drop the course.

But the good thing is that we have our next session starting on 11/11/2019 and you may give it a try again and complete your course successfully.

Please feel free to reach out to us with any queries you have in future.

Thanks,
Muskan
Curriculum Support Engineer

Hi @Muskan_47318

I’m trying to take 310 and 130 again, but I’m running into the same error. My error is with VirtualBox, I’m getting:

E_FAIL (0x80004005)

The virtual machine ‘m310_database_1573658814927_90121’ has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in ‘C:\Users\021454\VirtualBox VMs\m310_database_1573658814927_90121\Logs\VBoxHardening.log’.

I’ve scoured the internet for solutions, but still unable to fix. Not sure how to resolve this and complete the courses.