Deploying via (VirtualBox/VMWare/AWS/Azure/ESXi): VirtualBox
Vagrant Version (if applicable): Vagrant 2.2.19
Description of the issue:
Posting this in case somebody else runs into similar issues building on Windows and as a potential FR for the prepare.ps1 script.
Vagrant provisioning on VirtualBox fails due to VMs becoming unresponsive shortly after boot. I have spent a good amount of time looking at this and have localized the issue it to Hyper-V being implicitly enabled by Windows Subsystem for Linux (WSL) for which prepare.ps does not check. There are additional potential culprits listed on VBox forums over here for which it may make sense to include additional checks in the 'prepare.ps1' script.
Description of the issue:
Posting this in case somebody else runs into similar issues building on Windows and as a potential FR for the
prepare.ps1script.Vagrant provisioning on VirtualBox fails due to VMs becoming unresponsive shortly after boot. I have spent a good amount of time looking at this and have localized the issue it to Hyper-V being implicitly enabled by Windows Subsystem for Linux (WSL) for which
prepare.psdoes not check. There are additional potential culprits listed on VBox forums over here for which it may make sense to include additional checks in the 'prepare.ps1' script.Link to Gist Containing Build Logs:
N/A