-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting error when trying to execute 'vagrant up' #10563
Comments
Hi there @satapathyS - Please look at |
VBoxHardening.log2b34.304c: Log file opened: 5.1.0r108711 g_hStartupLog=0000000000000070 g_uNtVerCombined=0xa03fab00 |
This looks to be a duplicate of this: #9318 (comment) Thanks! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Vagrant 2.2.2
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'centos/7' could not be found. Attempting to find and install.. .
default: Box Provider: virtualbox
default: Box Version: >= 0
==> default: Loading metadata for box 'centos/7'
default: URL: https://vagrantcloud.com/centos/7
==> default: Adding box 'centos/7' (v1811.02) for provider: virtualbox
default: Downloading: https://vagrantcloud.com/centos/boxes/7/versions/1811. 02/providers/virtualbox.box
default: Download redirected to host: cloud.centos.org
default:
==> default: Successfully added box 'centos/7' (v1811.02) for 'virtualbox'!
==> default: Importing base box 'centos/7'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'centos/7' is up to date...
==> default: Setting the name of the VM: Openstack_default_1546627876924_70435
==> default: Vagrant has detected a configuration issue which exposes a
==> default: vulnerability with the installed version of VirtualBox. The
==> default: current guest is configured to use an E1000 NIC type for a
==> default: network adapter which is vulnerable in this version of VirtualBox.
==> default: Ensure the guest is trusted to use this configuration or update
==> default: the NIC type using one of the methods below:
==> default:
==> default: https://www.vagrantup.com/docs/virtualbox/configuration.html#default-nic-type
==> default: https://www.vagrantup.com/docs/virtualbox/networking.html#virtualbox-nic-type
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Booting VM...
There was an error while executing
VBoxManage
, a CLI used by Vagrantfor controlling VirtualBox. The command and stderr is shown below.
Command: ["startvm", "95ba6753-22bd-4020-afdf-a9c3b8cd69ec", "--type", "headless"]
Stderr: VBoxManage.EXE: error: The virtual machine 'Openstack_default_1546627876924_70435' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\satapathys\VirtualBox VMs\Openstack_default_1546627876924_70435\Logs\VBoxHardening.log'
VBoxManage.EXE: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine
Host OS Microsoft Windows 10
The text was updated successfully, but these errors were encountered: