Huu Phan | Blog Linux operating system | Linux operating system -Blog Huu Phan | www.huuphan.com
huuphan.com. Powered by Blogger.

Vagrant up error while executing `VBoxManage`

This day, I running vagrant up in my laptop then isuse. I can not start VM in vagrant. My laptop use windows 10. Error code as below:

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

Command: ["showvminfo", "600a47e1-9637-4054-89c2-df3e5bf8f691"]

Stderr: VBoxManage.exe: error: Code ERROR_MOD_NOT_FOUND 0x8007007E (0x8007007E) - ERROR_MOD_NOT_FOUND 0x8007007E (extended info not available)
VBoxManage.exe: error: Context: "GetGuestOSType(osTypeId.raw(), osType.asOutParam())" at line 575 of file VBoxManageInfo.cpp

Solve problem There was an error while executing `VBoxManage`, a CLI used by Vagrant for controlling VirtualBox.


Step 1: Right click on VirtualBox.exe and select Properties.

Step 2: Click the Compatability tab. Click the button that says 'Change settings for all users'.
Vagrant up error while executing `VBoxManage`

Step 3: In the new window that pops up check 'Run this program as administrator'. --> Click the Ok button.
Vagrant up error while executing `VBoxManage`

Step 4: Click Apply
Now, You can running vagrant up in windows 10.
Vagrant up error while executing `VBoxManage`

post new :

Huu Phan | Blog Linux operating system | Huu Phan ~ Zimbra Mail Server,linux,bash script,centos,linux command | www.huuphan.com

1 comments :

I am still getting same error

$ vagrant.exe up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
default: Adapter 2: bridged
==> default: You are trying to forward to privileged ports (ports <= 1024). Most
==> default: operating systems restrict this to only privileged process (typically
==> default: processes running as an administrative user). This is a warning in case
==> default: the port forwarding doesn't work. If any problems occur, please try a
==> default: port higher than 1024.
==> default: Forwarding ports...
default: 80 (guest) => 80 (host) (adapter 1)
default: 8080 (guest) => 8080 (host) (adapter 1)
default: 9090 (guest) => 9090 (host) (adapter 1)
default: 5000 (guest) => 5000 (host) (adapter 1)
default: 3000 (guest) => 3000 (host) (adapter 1)
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: 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", "04050abe-70e9-4a49-aec6-1d7581d7f16e", "--type", "headless"]

Stderr: VBoxManage.exe: error: The virtual machine 'vagrant_default_1571689157293_26137' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\Administrator\VirtualBox VMs\vagrant_default_1571689157293_26137\Logs\VBoxHardening.log'
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine

Relay