![]() Note: I have enabled WSL 2 in my machine. With this solution already vagrant works perfectly for this is not an answer he specifically said I will test if it works fine disabing this feature. I have Docker Desktop installed on my Windows 10, too. In my case I have two different Vagrant with Homestead/Laravel boxes and only the second had this problem. I had the same issue and trying your solution works fine. With this solution already vagrant works perfectly for me. PS: On saying that you already activate virtualization on the board (bios) Once the aforementioned features were deactivated and the computer was restarted, I share the new state of the processor where it is evident that virtualization is already working: I show you the capture of the initial state: įix it by disabling the following windows features: The WindowsFeature VirtualMachinePlatform is necessary for WSL 2Īfter a couple of days of trying to solve the problem with "SSH auth method: private key", it was found that windows 10 has a conflict with vagrant.Īs a tool to validate the status of virtualization, the program was used: ". In this case, you can use a loop to create multiple VMs with derived private IPs. Let’s say you want to create 3 Vms of the same type. You can individually manage the VMs with its name. Note: I have enabled WSL 2 in my machine. To ssh into the VMs, you need to use the names web and db. Vagrant freezes on 'SSH auth method: private key' when using Ubuntu box #11890.Vagrant up times out on SSH and vagrant ssh connection reset #11931.If not enable it by running the following command on PowerShell as Administrator: dism.exe /online /Enable-Feature /FeatureName:VirtualMachinePlatform /all /NoRestart. WindowsFeature VirtualMachinePlatform should be enabled.The timeout ("config.vm.boot_timeout") value. If the box appears to be booting properly, you may want to increase Verify that authentication configurations are also setup properly, Problem that networking isn't setup properly in these boxes. Working and you're able to connect to the machine. If you're using a custom box, make sure that networking is properly These errorsĪre usually good hints as to what may be wrong. Vagrant had when attempting to connect to the machine. If you look above, you should be able to see the error(s) that The configured ("config.vm.boot_timeout" value) time period. Vagrant was unable to communicate with the guest machine within Timed out while waiting for the machine to boot. => default: Preparing network interfaces based on configuration.ĭefault: 22 (guest) => 2222 (host) (adapter 1) => default: Clearing any previously set network interfaces. => default: Setting the name of the VM: laravel-test-minimum_default_1603343961170_29543 => default: Checking if box 'laravel/homestead' version '9.6.1' is up to date. => default: Matching MAC address for NAT networking. => default: Importing base box 'laravel/homestead'. Bringing machine 'default' up with 'virtualbox' provider.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |