I'm currently running vargant version 2.1.5 on my mac high sierra 10.13.6
So after completing the vagrant init and vagrant up command I'm suppose to have a fully running virtual machine in virtualbox. But after running vagrant up I get this instead.
There was an error while executing VBoxManage, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["startvm", "3574f45d-aade-4053-af8b-0c88330e855f", "--type", "headless"]
Stderr: VBoxManage: error: The virtual machine 'saltstates_default_1539870640620_6152' has terminated unexpectedly during startup with exit code 1 (0x1)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine
Any idea what this is about?
So if you have mac high sierra or higher, mac security and system preferences allow applications to make system changes with in a 30 mins of installation of the application. So I had to uninstall virtual box then reinstall it. Then I went to system preferences and allow kernel driver changes.
It's not necessary to reinstall VirtualBox in order to resolve this problem. As described in the VirtualBox forum for macOS hosts, you can do the following instead:
Restart your machine and enter Recovery Mode (Press and hold ⌘-R on reboot.)
Open the Terminal.
Type the following: spctl kext-consent add VB5E2TV963
Press Enter.
Restart your machine.
When you install application, on Mac OS, you have to accept permission.
Follow the step.
After:
I've Windows 10 Pro system, and use Hyper-V on that system. Due to the needs of device redirection doesn't works well with Hyper-V, I've installed VMWare Workstation 14.
I have to disable Hyper-V to make VMWare Workstation work, at beginning. It worked until last weekend , seems because of the QFE update. I just verified, it was not QFE but Feature update to Windows 10, version 1803 that triggered the problem with VMWare Workstation again.
After Windows update completed (after reboot), I tried to start a VM in VMWare. I get the error dialog complaining about Device/Credential Guard.
Following the instruction in this link: https://kb.vmware.com/s/article/2146361, and after the reboot, I get another complaint about incompatibility with Hyper-V.
After reset the Hyper-V selection in Windows Feature or confirm that HyperV is not already removed, and reboot, the first error came back.
It gets in a loop of error complaining about Device Guard and complaining about Hyper-V for VMWare.
Ok, thanks to the answer from communities of VMWare: https://communities.vmware.com/thread/588526
The issue is now gone, by applying the following change:
Disable credential guard by using readiness tool from Microsoft: https://www.microsoft.com/en-us/download/details.aspx?id=53337, with this command: DG_Readiness_Tool_v3.2.ps1 -disable
Disable Hyper-V by using PowerShell command: Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V
Reboot and accept to boot without CG/DG.
Although I don't like that VMWare cannot work together with device guard from system, I get my VM working for the moment.
1- run cmd as admin
2- run : bcdedit /set hypervisorlaunchtype off
3- reboot
let me knew if it works please
good luck
here are the few steps for you to solve this issue:
Disable the HvHost service (and any other services with prefix Hyper-V if needed) from windows TaskManager(Ctrl+Alt+Del)
use the tool from the official website
Uncompress the downloaded zip file to your own directory, take C:\DG_Readiness_Tool_v3.5 here for instance.
Run Windows PowerShell as admin, type the following two commands:
cd C:\DG_Readiness_Tool_v3.5
.\DG_Readiness_Tool_v3.5.ps1 -Disable
Reboot
Adrian at https://answers.microsoft.com/en-us/windows/forum/windows_10-security/cannot-disable-memory-integrity-core-isolation-in/29ac5ce4-30d2-47d1-ab17-734980fd287b
says "I think it's a bug that this cannot be disabled via UI but fortunately it's possible through the registry by setting the following key to 0:"
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity\Enabled
This worked for me as well [Windows 10 Pro Version 1803(OS Build 17134.112, VMWare Workstation 14 Pro Version 14.1.2]
Hi I am new to kubernetes. I have read online tutorials to understand kubernetes and its benefits. To get hands on I have done a set up in my windows machine. It worked well half-way and received error while configuring kubernets VM.
I have downloaded Minikube installers and issued following command in windows 10 power shell
.\minikube.exe start --kubernetes-version="v1.6.0"
--vm-driver="virtualbox" --show-libmachine-logs --alsologtostderr
Retrying.
E1104 23:10:01.364507 16152 start.go:122] Error starting host: Error creating host: Error creating machine: Error in driver during machine creation: Unable to start the VM: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe startvm minikube --type headless failed:
VBoxManage.exe: error: The virtual machine 'minikube' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\Kube\ .minikube\machines\minikube\minikube\Logs\VBoxHardening.log'
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine
I have oracle virtual box already installed in my machine.Not sure whether it causes this issue.
upon reading few other forums, i have deleted .minikube directory and reissued the same commands in windows power shell but it didnt help.
can anyone please guide me to install kubernetes in windows 10 machine.
I have no hyper-v in my machine(Windows home edition).
Looks like my oracle virtual box has network access issues. Hence it could not set up kubernetes vm. I found this issue when i start my "Docker quick start terminal", it shows same error as i posted above. Hence i uninstalled and then installed latest version of oracle virtual box. It resolved the issue. kubernetes cluster has been created in my windows 10 machine.
I uninstalled the virtual box and installed docker toobox for windows from here
https://docs.docker.com/toolbox/toolbox_install_windows/#step-2-install-docker-toolbox
This will install Oracle VM virtual box too.
Open “Docker Quickstart Terminal”
This opens a Unix Bash.
Use this terminal for building docker images and running minikube.
I am getting the following issue trying to start a VM using vagrant & VirtualBox on my MacBook Air (13-inch, Early 2015) running OS X 10.11.6. I have tried VirtualBox version 5.0.26, 5.1.0 and 5.1.2. I have searched around and tried all the suggestions I could find. what do I need to do to fix this issue?
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["startvm", "23e70124-39c9-46ea-a45d-cf34c0e8a251", "--type", "headless"]
Stderr: VBoxManage: error: The VM session was aborted
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component SessionMachine, interface ISession
This seems to be a problem with setting the networking to NAT mode (which is done by vagrant). To bring up the vm, go into virtualbox, edit the vm network settings to something like bridged and start the vm and it should work.
However, the downside is that the vagrant up command does not work (down works once the vm has been started manually).
At this point, I am also struggling to find a solution (may be something to do with El Capitan)
Had the same problem, though I am on os x 10.10.5 Yosemite.
Downgrading to VirtualBox 4.3.40 worked for me.
https://www.virtualbox.org/wiki/Download_Old_Builds_4_3
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Locked. This question and its answers are locked because the question is off-topic but has historical significance. It is not currently accepting new answers or interactions.
Machine: Window10 (64bit).
I downloaded the latest VirtualBox, Vagrant and initialized CentOS 6.7 64bit image/url.
The following worked successfully in Git-Bash session.
1. vagrant box add "centos67x64" "https://github.com/CommanderK5/packer-centos-template/releases/download/0.6.7/vagrant-centos-6.7.box"
2. vagrant init
3. Updated Vagrantfile (and turned vb.gui option i.e. uncommented that config section in the file).
config.vm.provider "virtualbox" do |vb|
# Display the VirtualBox GUI when booting the machine
vb.gui = true
# Customize the amount of memory on the VM:
vb.memory = "2048"
end
After that, I tried the following command but I'm getting this error message.
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'centos67x64'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: vv_default_1466548735200_80300
==> 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: 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", "ae74ebaa-8f01-48cf-bdad-956c59ef1208", "--type", "gui"]
Stderr: VBoxManage.exe: error: VT-x is not available (VERR_VMX_NO_VMX)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole
If I turn/comment off the whole Vagrantfile respective section, I'm still getting the following error.
$ vagrant 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: Forwarding ports...
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", "ae74ebaa-8f01-48cf-bdad-956c59ef1208", "--type", "headless"]
Stderr: VBoxManage.exe: error: VT-x is not available (VERR_VMX_NO_VMX)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole
Any ideas! I looked into other posts but couldn't find how to resolve in my case.
As I got some hints, I tried one of the solution.
TURN off the Hyper-V which is turned of by default I guess in Windows10.
To do this, I Went to Control panel in Windows10 and looked here and found this.
Then, I turned Hyper-V off by unchecking (the tick mark, or black box).
Windows10 told me to RESTART, I said "No" (later).
Tried running "vagrant up" again (without or without any changes or the above mentioned config.vm... changes to the Vagrantfile). It didn't work and gave me the same --headless error message.
OK, time to restart. Restarted Windows10. After the restart, I saw bunch of Virtual Box error messages popups (few of them are shown below).
Once I clicked on OK button on all of those Virtual Box popup windows, I tried to run Virtual Box on my machine, it came up fine(successfully).
Now, I opened Git-BASH and again went to the directory where Vagrantfile was present. Tried tweaking the settings on / off or commenting/uncommenting the Vagrantfile respective section (as I described above).
STILL getting the the same error messages for running "vagrant up" (even after turning the Hyper-V off as well).
Stop hyper-v service running by default in Windows 8/10, since it blocks all other calls to VT hardware.
Additional explanation here:
https://social.technet.microsoft.com/Forums/windows/en-US/118561b9-7155-46e3-a874-6a38b35c67fd/hyperv-disables-vtx-for-other-hypervisors?forum=w8itprogeneral
Also as you have mentioned, if not already enabled, turn on Intel VT virtualization in BIOS settings and restart the machine.
To turn Hypervisor off, run this from Command Prompt (Admin) (Windows+X):
bcdedit /set hypervisorlaunchtype off
and reboot your computer. To turn it back on again, run:
bcdedit /set hypervisorlaunchtype on
If you receive "The integer data is not valid as specified", try:
bcdedit /set hypervisorlaunchtype auto
-- credit Tj Kellie
I just solved this problem by disabling(uncheck) Hyper-V. Seems Hyper-V was enabled when I installed Docker
Control Panel -> Program And Features -> Turn Windows Features on or off.
You may need to reboot afterwords.
Warning: Vagrant with VirtualBox cannot work with Docker at the same time.
Although this is an old question, but I've still encounter it recently.
This is what worked for me on my i7-3770 3.40GHz, Z77 extreme motherboard running Windows 10.
In Windows, disable Hyper-V:
Open up a PowerShell or CMD session as Administrator.
Type the following command:
dism.exe /Online /Disable-Feature:Microsoft-Hyper-V-All
Windows will ask you to restart.
In the bios:
Disable >>> Intel Virtualization Technology, vt-d
Save the bios settings and allow it to restart and boot into Windows.
Shutdown the computer (I've tried just restarting and it didn't work)
Power up the computer, go into the bios and re-enable the above disabled settings.
Save, restart.
Download the Intel Utility to check.
You should now see it been supported:
If it still doesn't work, try re-enabling Hyper-V first then following the steps above.
Docker can be the culprit. I had same issue after installing docker. Docker uses Windows hyper-v driver to create containers. Hence Docker and Virtual Box may not work together!
Along with Hyper-V option, I had to uncheck "Containers" Windows feature to have my Vagrant work.
If you are getting the above error on Windows 10 Pro then you can disable the Hyper-V. Hyper-V is default enable in the Windows 10. You can either use Hyper-V or Virtual Box. So, to use the Virtual box you have to disable hyper-v in windows, you can follow following steps to do -
Search Control Panel
Click on Uninstall a program
Turn Windows features on or off
Unselect the Hyper-V option.
Click on OK
Restart the system to apply the changes.
Search for Windows Features. Turn off Hyper V.Most likely, Virtual Box is clashing with Hyper V on Windows. Also check for Hyper V running in your Services. Stop and disable that as well.
Besides turning on virtualization features of the processor and turning off Hyper-V, here's another thing, related to Windows' Virtualization-Based Security features:
https://learn.microsoft.com/en-us/windows-hardware/design/device-experiences/oem-vbs
VBS (and the associated security features) must be disabled to avoid conflicting hypervisors. Here is a solution from VMware, which also seems valid for the VirtualBox issue":
https://kb.vmware.com/s/article/2146361
If the Docker is installed and up and running at the same time, if you are trying to run Virtual Box it will not work. The underlying kernel on host machine which is present on your laptop will not allow to work both things at the same time.
Hence Docker and Virtual box can't run at the same time. for that,
To use Docker you have to enable the hyper-v which is present on this location
Control Panel -> Program And Features -> Turn Windows Features on or off.
To run Virtual box you have to disable the hyper-v from above location.
Turn Off the Hyper-V option from the windows feature list. You can find this on control panel.
The only thing that worked for me was running the installers and doing a repair for VM VirtualBox and Vagrant.
Tried all above steps but nothing was working till I enabled Virtualization Technology in BIOS. Even though Intel CPU Utility was showing Virtualization as Ticked, it really wasn't.
Had boot-up system, entered BIOS, Enabled Virtualization, Restarted and Voila! It worked after more than 4 hours of efforts.
This is what helped me:
Remove Hyper-V and install Hypervisor platform.
In the elevated Powershell prompt do:
Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All
Enable-WindowsOptionalFeature -Online -FeatureName HypervisorPlatform
Restart
Disable Windows Defender Credential Guard
"Local Group Policy Editor" → "Computer Configuration" → "Administrative Templates" → "System" → "Device Guard" → "Turn on Virtualization Based Security" → Set to "Disabled"
Delete the following registry settings:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\LSA\LsaCfgFlags
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\DeviceGuard\LsaCfgFlags
Restart
Delete the Windows Defender Credential Guard EFI variables
In the elevated command prompt do:
mountvol X: /s
copy %WINDIR%\System32\SecConfig.efi X:\EFI\Microsoft\Boot\SecConfig.efi /Y
bcdedit /create {0cb3b571-2f2e-4343-a879-d86a476d7215} /d "DebugTool" /application osloader
bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} path "\EFI\Microsoft\Boot\SecConfig.efi"
bcdedit /set {bootmgr} bootsequence {0cb3b571-2f2e-4343-a879-d86a476d7215}
bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} loadoptions DISABLE-LSA-ISO
bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} device partition=X:
mountvol X: /d
Restart
Disable virtualization-based security
Delete all registry keys under HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\DeviceGuard\* (but keep DeviceGuard itself).
Restart
See also: Disable Windows Defender Credential Guard