environment
Windows 10 Pro
Vagrant 2.2.4
VirtualBox 6.0.4 r128413 (Qt5.6.2)
box: laravel / homestead (virtualbox, 7.1.0)
Vagrant plug-ins: vagrant-hostmanager (1.8.9global)
Hyper-V Installed
VirtualBox has been able to coexist with Hyper-V since version 6, so VirtualBox and Vagrant versions have been upgraded to the latest version and Hyper-V has been installed, and the SSH part has timed out.When I tried to close it, I couldn't see the screen when I saw it or started it in VirtualBox.
I looked it up and found out that the SSH key is correct?I understand that, but I would like to know how to write homestead in a different way from the normal Vagrant file, so please let me know.
The logs are as follows:
Bringing machine 'homestead-7' up with 'virtualbox' provider...
==>homestead-7: Importing base box 'larvel/homestead'...
== > homestead-7: Matching MAC address for NAT networking...
==>homestead-7: Checking if box 'larvel/homestead' version '7.1.0' is up to date...
==>homestead-7: Setting the name of the VM:homestead-7
== > homestead-7: Clearing any previously set network interfaces...
==>homestead-7:Preparing network interfaces based on configuration...
homestead-7:Adapter 1:nat
hostead-7:Adapter 2:hostonly
== > homestead-7: Forwarding ports...
homestead-7:80(guest)=>8000(host)(adapter1)
homestead-7:443(guest)=>44300(host)(adapter1)
homestead-7:3306(guest)=>33060(host)(adapter1)
homestead-7:4040(guest)=>4040(host)(adapter1)
homestead-7:5432(guest)=>54320(host)(adapter1)
homestead-7:8025(guest)=>8025(host)(adapter1)
homestead-7:27017(guest)=>27017(host)(adapter1)
homestead-7:22(guest)=>2222(host)(adapter1)
==>homestead-7: Running 'pre-boot' VM customizations...
==>homestead-7: Booting VM...
==>homestead-7: Waiting for machine to boot. This may take a new minutes...
homestead-7:SSH address:127.0.0.1:2222
homestead-7:SSH username:vagrant
homestead-7:SSH auth method:private key
Timed out while waiting for the machine to boot. This means that
Vagrant was unavailable to communicate with the guest machine with in
The configured("config.vm.boot_timeout" value) time period.
If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine.These errors
Are usally good hits as to what may be wrong.
If you're using a custom box, make sure that networking is proper
working and you're able to connect to the machine.It is a common
problem that networking isn't setup proper in these boxes.
Verify that authentication configurations are also setup proper,
as well.
If the boxappears to be booting professionally, you may want to increase
The timeout("config.vm.boot_timeout") value.
In conclusion, it seems that Type-V was involved.
When I uninstalled and restarted Hyper-V, it did not time out and started without any problems.
I didn't even know which log to look at so I didn't know what the error was.
I felt like I saw something that could coexist with Hyper-V, but it may not be complete yet.
© 2024 OneMinuteCode. All rights reserved.