How do I fix these errors while trying start Virtual Box? - terminal

I commanded 'vagrant up' on my terminal, to login my virtual CentoOS7 server then,I got these errors.
Just before I tried to up vagrant, I was customizing my vim editor on CentOS7 server on my vagrant. and then, I sat some important document.
maybe it caused this error...
and I found similar question on the web but I couldn't fix it.
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["startvm", "6f113832-832d-4fd6-ba87-af003b3dddce", "--type", "headless"]
Stderr: VBoxManage: error: Could not open the medium '/Users/yamadaasuma/VirtualBox VMs/MyCentOS_default_1551371079969_97354/centos-6.8-x86_64-disk001.vmdk'.
VBoxManage: error: VD: error VERR_FILE_NOT_FOUND opening image file '/Users/yamadaasuma/VirtualBox VMs/MyCentOS_default_1551371079969_97354/centos-6.8-x86_64-disk001.vmdk' (VERR_FILE_NOT_FOUND)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MediumWrap, interface IMedium
And these are the logs from my Virtual Box.
Please help me anyone.
00:00:00.040456 VirtualBox VM 6.0.12 r133076 darwin.amd64 (Sep 3 2019 12:00:40) release log
00:00:00.040456 Log opened 2019-09-20T13:35:04.466754000Z
00:00:00.040456 Build Type: release
00:00:00.040456 OS Product: Darwin
00:00:00.040456 OS Release: 18.6.0
00:00:00.040456 OS Version: Darwin Kernel Version 18.6.0: Thu Apr 25 23:16:27 PDT 2019; root:xnu-4903.261.4~2/RELEASE_X86_64
00:00:00.040456 DMI Product Name: MacBookAir7,2
00:00:00.040456 DMI Product Version: 1.0
00:00:00.040456 Host RAM: 8192MB (8.0GB) total, 3483MB (3.4GB) available
00:00:00.040456 Executable: /Applications/VirtualBox.app/Contents/MacOS/VBoxHeadless
00:00:00.040456 Process ID: 64193
00:00:00.040456 Package type: DARWIN_64BITS_GENERIC
00:00:00.043166 Installed Extension Packs:
00:00:00.043208 None installed!
00:00:00.045230 Console: Machine state changed to 'Starting'
00:00:00.050801 Console: Machine state changed to 'PoweredOff'
00:00:00.061957 Power up failed (vrc=VINF_SUCCESS, rc=NS_ERROR_FAILURE (0X80004005))

The error is showing because vagrant cannot find the virtual box file which is associated with the project's virtual machine. Maybe it was deleted by accident.
In order to solve the issue open the Virtual Box GUI and then right click on the virtual box which is associated with the issue and click on remove.
This will delete the association from Virtual Box.
Now you can run vagrant up --provision and it will remake the box for you.

Try running
vagrant reload --provision
then
vagrant up
This cheatsheet can you help you more. https://gist.github.com/wpscholar/a49594e2e2b918f4d0c4

It should solve the problem
VBoxManage startvm "6f113832-832d-4fd6-ba87-af003b3dddce" --type headless

I would try to run the following command in CMD as administrator:
sc start vboxdrv
According to this forum post: https://github.com/hashicorp/vagrant/issues/9318
A complete reinstall of VirtualBox fixed the issue for some users.

Related

Big Sur MacOS Vagrant issue

I just updated MacOS to New version (Big Sur). When I tried vagrant up to start the vagrant, it shows error as the following below:
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["hostonlyif", "create"]
Stderr: 0%...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Failed to create the host-only adapter
VBoxManage: error: VBoxNetAdpCtl: Error while adding new interface: failed to open /dev/vboxnetctl: No such file or directory
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
VBoxManage: error: Context: "RTEXITCODE handleCreate(HandlerArg *)" at line 94 of file VBoxManageHostonly.cpp
Anyone know how to solve this issue? I've tried install vagrant again already.
I have solved this problem by below steps:
Update your virtualbox
Update your vagrant
Go to System Preference then privacy& security and Allow the permission in general tap.
I had this issue too & upgrading my virtualbox to 6.1 solve the issue. Check the thread here.
But when I tried using virtual v6.0 the error still persist.
I had been updated the VirtualBox even reinstall but the issue did not resolve . After I uninstall and reinstall the Virtualbox, allow permission, and restart my pc then the issue fix. I had followed the bellow steps:
Uninstall VirtualBox via their official uninstaller script
Do a clean install of VirtualBox using VirtualBox.pkg
Adjust the privacy settings of Big Sur: System Preferences > Security and Privacy > click the unlock button
Restart pc

`Vagrant up ` issue

I am using Vagrant Up command to run but I always get this error
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["startvm", "0cda9586-5016-446e-880e-fae72f66dae4", "--type",
"headless"]
Stderr: VBoxManage: error: The virtual machine
'website_default_1539955305061_15994' has terminated unexpectedly
during startup with exit code 1 (0x1)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005),
component MachineWrap, interface IMachine
I am using Mac high sierra. I downloaded image from here https://www.vagrantup.com/downloads.html
Does anyone knows how to solve
I guess you need to download the latest version of VirtualBox since the older version is not supported by the latest MacOs version(10.14)
https://www.virtualbox.org/wiki/Downloads
Also, the vagrant need to update for supporting the latest VirtualBox
Latest Version: 2.2.1
To upgrade to the latest version, visit the downloads page and
download and install the latest version of Vagrant from the URL
below:
https://www.vagrantup.com/downloads.html
oh, one more thing, you may also want to update the vagrant plugin:
vagrant plugin update

VM won't bring up using homestead up

I have no issue running vm's using homestead up but last week I just updated to the latest Windows 10 update and now when I run the command it gives me
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["startvm", "c8da3222-7052-452a-b590-ff7144b50c9e", "--type", "headless"]
Stderr: VBoxManage.exe: error: The virtual machine 'homestead-7' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\magal\VirtualBox VMs\homestead-7\Logs\VBoxHardening.log'
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine
Been searching the web for a solution but got no luck.
Box Version : 2.1.0
Without more info the only advice is to run vagrant destroy && vagrant up If you still have issues after that, consider opening a new issue on https://github.com/laravel/homestead/issues/new
Issue was fixed after upgrading my Virtualbox to 5.2.
On Windows 10, I installed everything as ADMINISTRATOR and only the following configuration worked for me:
Vagrant 1.9.2 : Download Vagrant 1.9.2
Oracle VM VirtualBox 5.1.30 : Download Oracle VM VirtualBox 5.1.30
For older versions of VirtualBox, the virtual machine has terminated unexpectedly.
For newer versions of VirtualBox, the host-only adapter cannot be created.
When you upgrade or downgrade, make sure that you permanently delete (Shift + Delete) the following folders from C:\Users\your-user : .vagrant, .VirtualBox and Virtual VM Machines. When using vagrant up, these folders will be created again.
After each program install and uninstall, make sure to restart your computer. Old files from VirtualMachine and Vagrant are persistent until the OS boots up again.

VirtualBox/Vagrant stopped working after Windows 10 Creators Update

I was happily using Vagrant with VirtualBox for my laravel projects (Homestead) but after the Creators Update for Windows 10, VirtualBox stopped working - vagrant up was not throwing any errors and I was even able to vagrant ssh successfully but my web projects were unreachable from the browser.
Initially I was using VirtualBox v.5.1.14 but decided to update to the latest (which is v.5.1.22) - no luck whatsoever, so after reading the answers from this thread I've downgraded to v.5.0.38
Now when I try to vagrant up this error is shown:
vagrant up
Bringing machine 'homestead-7' up with 'virtualbox' provider...
==> homestead-7: Checking if box 'laravel/homestead' is up to date...
==> homestead-7: Resuming suspended VM...
==> homestead-7: 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", "e5ac5ef8-07fa-412f-b59c-bfd745db047e", "--type", "headless"]
Stderr: VBoxManage.exe: error: Failed to load unit 'cpum' (VERR_INVALID_FLAGS)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole
p.s. I've already set Host-Only Network Adapter through preferences in VirtualBox
What I did to resolve the issue was to "plug off" my virtual machine's state using discard, hoping not to lose any information... Now I'm on VirtualBox v.5.1.14 and will stick with it until all things work.
I had to update to Virtualbox Version 5.2 to get my boxes running again.
and also need to reinstall git for windows 2.15.1.2-64 bit and select the option "use windows default console" (cmd.exe) instead of "MinTTY"
With MinTTY the command :
vagrant ssh
will not show the bash command line.
using windows default Console worked.
see more possibe workarounds to this piont also in this git issue
My Working env:
- Windows 10 - 1709 - Build 16299.125
- vagrant 2.0.1
- virtualbox 5.2.0
- git for windows 2.15.1.2. 64 bit
Turning off Hyper-V solved my problem.
Solution:
Control Panel -> Turn Windows Feature on or Off -> Uncheck Hyper-V
I had the same problem. My vagrant up stopped working after the Windows Fall Creators Update (1709). It worked after I turned off Hyper-V.
Current Working Environment:
- Windows 10 (1709)
- Vagrant 1.9.7
- VirtualBox 5.1.32

Homestead in a Ubuntu 14 VBox - Setup Errors

I am having some issues setting up my dev environment.
My setup:
Windows 10 Host
Running Ubuntu 14 in a VirtualBox instance
Install Homestead
vagrant up
This error
There was an error while executing VboxManage, a CLI used by Vagrant for controlling Virtualbox. The command and stderr is shown below.
Command: [hostonlyif", "create"]
Stderr: 0%...
Progress State: NS_ERROR_FAILURE VBoxManage: error: Failed to create the host-only adapter VboxManage: error: VboxNetAdpCtl: Error while adding new interface: VBoxNetAdpCtl: ioctl failed for > devboxnetctl: Inappropriate ioctl for devic
VboxManage error: Details: code NS_ERROR_FAILURE (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
VBoxManage: error: Context: "RTEXCODE handleCreate(HandlerArg*)" at line 71 of file VBoxManageHostonly.cpp
I would greatly appreciate any insight into this issue, as my google-fu has failed me on this one (and some errors with dependencies concerning the right version of virtual box -- 5.1 doesn't work here, had to uninstall and downgrade to 5-- have depleted my energies).
Is it possible that this is an "inception" kind of issue regarding the fact that I'm setting up a virtual machine inside a virtual machine?
The (first) VBox Storage settings: 50GB partitioned, 14 current size
Granted the machine 1 cpu
The network settings is here
Thankyou in advance
I have had a similar problem updating from Windows 7 to Windows 10.
You can see the solution in my blog (in Spanish) and automatically translated with Google translator. It is not spam ;)
Try to downgrade linux kernel version. Its most probably about your hardware and linux kernel mismatch problem. Also Its not normal situation why are you using virtual machine inside virtual machine?.

Resources