I have a problem with Vagrant, trying to initialize a virtualbox with laravel/homestead box.
I have installed latest version of Vagrant (1.7.4) on my Windows 8 OS.
I have installed Oracle VirtualBox 5.5.0.
Then I did this in windows Command Prompt:
vagrant add box laravel/homestead to add the laravel homestead box
vagrant init laravel/homestead
and
vagrant up
After vagrant up somewhere in the process the system fails with BSoD (KMODE_EXCEPTION_NOT_HANDLED)
Any ideas of what i could have done wrong, or have anybody experienced this problem?
Thank you!
Make sure you don't have Hyper-V windows resource active.
If you had installed Docker before check this, coz Docker needs Hyper-V.
In my case this works for me
Search for "Windows resource" on your windows start menu, and click on Enable or Disable windows resources, find Hyper-V, uncheck all checkboxes and OK. Restart your machine after this.
Ty
I had almost same issue(BSOD gave error SYSTEM_SERVICE_EXCEPTION).
Yesterday I installed Docker on Windows 10 and today I tried to "vagrant up"(using VirtualBox Provisioner) and got the BSOD. Hyper-V was conflicting and I turned it off from "Windows Features" and the issue got resolved.
Related
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]
I have virtual box Versión 5.1.30 r118389 (Qt5.6.2); vagrant 2.0.1 and laravel/homestead 5.01, when i do vagrant up show message error:
Do you have hardware virtualization (VT-x) enabled in your BIOS? You need to ensure you do NOT have Hyper-V enabled.
Outside of that you'd have to investigate that stop code to see what Windows was doing when the crash happened.
The VM I was trying to run was running perfectly on a Windows 7 machine.
I had upgraded to Windows 10 and tried out the same machine (with all the same configs and vagrant boxes), uninstalled and reinstalled virtualbox several times, but it still doesn't work.
Tried making a brand new VM - that didn't work too.
Here's the error
Some people who had similar 'hostonly' errors have suggested to restart the VirtualBox service from terminal, but I don't know the Windows equivalent of that command.
Anybody had this error before? How do I solve this?
A test build is available at https://www.virtualbox.org/download/testcase/VirtualBox-5.0.1-101902-Win.exe . This should fix the host-only interface creation problem by introducing a 5-second timeout when querying the registry key. We would appreciate feedback (i.e. does it fix the host-only interface creation errors or not, is the timeout long enough).
https://www.virtualbox.org/download/testcase/VirtualBox-5.0.1-101902-Win.exe
See https://www.virtualbox.org/ticket/14040#trac-change-55
Uninstalling the current VirtualBox and installing the testbuild worked for me
I have the same error and it seems to be a problem with changed network security in Windows and still no updated for it in Virtualbox.
Not pretty but a working solution (tested under Win10 build10130). This is what I did to get homestead up and working
Uninstall Vagrant and VirtualBox (restart if necessary)
Install notepad+ or other notepad replacement that handles linux line-endings
Download Vagrant v1.7.2, VirtualBox 5.0RC1, VirtualBox v4.3.6
Enable built-in administrator account.
net user administrator /active:yes
switch to Administrator account
Install Vagrant v1.7.2 (restart if necessary, log back into Administrator)
Install VirtualBox v5.0RC1
Install VirtualBox v4.3.6
Update VBox Host-Only adaptor driver (device manager,Search Automatically)
Edit VagrantFile file (where ever you vagrant up from) and change all ~/ to C:/Users/username/
Edit Homestead.yaml (Where ever you had it, likely C:\Users\username\.homestead) and change all ~/ to C:/Users/username/
Open VirtualBox
Run vagrant up
switch back to your usual user (do not sign out of Adminstrator)
hey presto, you have a working homestead
Each time after to manage vagrant (start, halt, whatever) switch to Administrator, manage, and switch back to your usual user. Do not sign out of the Administrator account when switching if you have a box up
VirtualBox won't boot the VM no matter what...I tryied with Vagrant and Docker.
Vagrant gave me timed out messages and Docker gave me exit code (1). I read tons of suggestions related to this problem but still found no solution. Any suggestion is welcomed.
VirtualBox version: 4.3.26
Vagrant version: 1.7.2
Docker Version: 1.6.0
and I'm running on windows 8.1
Which OS do you want to use in VirtualBox VM? For me it worked when I downloaded the latest version from https://www.virtualbox.org/wiki/Downloads. I have had troubles with some OS images but as I understand the question you don't even get that far.
Tried the solution in docker on windows not working ? It's Windows 7 but might solve your issue.
I managed to fix it by just shutting down the Virtual Box VM network.It set itself up again on NAT when I rebooted the VM, so that was the solution... It's probably a virtualbox bug.
I've installed the genymotion+virtualbox package on Windows 7 64-bit and everything goes fine... But when I start Genymotion it presents me an error message Unable to load virtualbox.
VirtualBox is installed and I'm able to start it manually. I've tried to install the packages separately, updated virtualbox to 4.2.16 but nothing worked.
I've already read genymotion FAQ but it did not help.
I have spend all day to solve this error since none of the answers worked for me.
I found out that oracle virtual box doesn't install the network adapter correctly in windows 8.1
Solution:
Delete all previous virtual box adapters
Go to device manager and click "Action" > "Add legacy hardware"
Install the oracle virtual box adapters manually (my path was C:\Program Files\Oracle\VirtualBox\drivers\network\netadp\VBoxNetAdp.inf)
Now that virtual box adapters is installed correctly, it needs to be setup correctly. (the following solution is like many other solution in here)
Start Oracle VM VirtualBox and go to "File" > "Preferences" > "Network" > "Host-only Network"
Click edit
Set IPv4 192.168.56.1 mask 255.255.255.0
Click DHCP Server tab and set server adr: 192.168.56.100 server Mask: 255.255.255.0 low address bound: 192.168.56.101 upper adress bound 192.168.56.254
Now click OK and start genymotion
Had the same problem, Uninstall Genymotion, install VirtualBox stand alone from https://www.virtualbox.org/wiki/Downloads then install the Genymotion package without VirtualBox.
Try closing Android Studio/Eclipse if it's open. It worked for me.
In Linux at least, I had to restart VirtualBox, running this command on terminal:
/lib/virtualbox/VirtualBox restart
Seems to be the same on Mac OS X.
What worked for me in Windows 7 is to remove the Host-only Network (in Oracle virtual box Preferences menu [CTRL+G] -> Network -> Host-only Networks). Genymotion will recreate it automatically at the next virtual device start. For the record; I'm using a Nexus S 2.3.7 virtual device.
Open Genymotion in Windows as an administrator. My Genymotion works only in this mode
FIXED SOLUTION
Run below command in terminal, It denotes where is your virtualbox install on MAC/Linux.
$ which vboxmanage
/usr/local/bin/VBoxManage
Genymotion search the virtualBox in /usr/bin/VBoxManage while it is located to /usr/local/bin/VBoxManage , you need to create the symlink to that location , Run in terminal to fix it.
sudo ln -s /usr/local/bin/VBoxManage /usr/bin/VBoxManage
I am using Intellij IDEA and same error happened to me, I found that the path to genymotion folder was not configured properly. Either open settings using File > Settings or press Ctrl + Alt + S then in IDE Settings check if the path to the genymotion folder is correct or not.
Since Android Studio are almost similar to Intellij IDEA so you can apply the same steps above to Android Studio as well.
Actually it seems like Genymotion has an issue with the newer versions of Virtual box, I had the same issue on my Mac but when I downgraded to 4.3.30 it worked like a charm.
Verify that GenyMotion is in your PATH environment variable. I noticed mine was not auto populated, so once I entered it, it was fine.
For Windows there are 2 installers. Did you use the bundle containing VirtualBox installer?
It is call Windows 32/64 bits (with VirtualBox).
Don't ask what this has to do with that , but by right clicking the genymotion application file and changing to compatibility to Vista solved the problem!
I also experienced this when I upgraded operating system from Windows 8 to Windows 8.1. Un-installing Virtualbox and re-installing worked for me.
Close Android Studio (if Android Studio is running)
Run Genymotion as administrator
that's all! simple.
try launching it via android-studio/eclipse plugin. Thats how I had similar issue when launching it from ubuntu.