Hey Dennis, sorry for the late reply. My laptop's hardrive drop dead on me ... So I upgraded to a SSD and just finished reinstalling all my stuff. The good news is vagrant and virtualbox both work now. I suspect you where right on your last message. It was probably a mess in my network with all the different environments I had running. Starting over on a fresh windows did the trick. I wish we could of got to the bottom this but at least it works now. Thanks a lot for your support ;-)
Le samedi 25 mai 2019 13:53:01 UTC-4, Dennis Chang a écrit : > > Hi Patrick, > > So I'm watching your video (thanks for that) and the black screen through > the console is disconcerting. > I've seen that before, in my case, it was some effect from a boot script > (/etc/rc.local) that > we had in our environment. I didn't really fix it except for removing the > entire boot script > from the process. > > In your case, my first suspicion are the custom boot configuration option > that you have > in your Vagrantfile. If you will, can you post it? This is the Vagrantfile > for (ytake/gardening). > > So I'm download this vagrant box myself (2.7 GB) and I'll poke around to > see what is in > there that may affect the boot console screen. > > But in the meantime, I'd like you to try and get output from the boot > screen. Recall, > there was a screen to select a Linux version. You mentioned you selected > recovery > option? Well instead of selecting that second option, hit ESC instead. > This should > output the options (I'd like to see it). Notice in the output of the > options, there is a "quiet" > someplace. I'd like you to edit that line, by pressing 'E' and remove > "quiet". Finally, > when you hit Enter, the boot process should show Linux boot text. We want > to see where > it dies. > > What I believe is happening is, for the black screen, something is > affecting the console. > However, given all the problems you're experiencing with Vagrant and > VirtualBox (has it > *ever* worked for you on this machine?) I suspect that there is something > wrong with > VirtualBox and the network (meaning your physical interfaces). Because all > VMs will use > the network, I'm guessing there may be an issue with VirtualBox and the > network interfaces > on your computer. So for instance, when you have "private_network" in your > Vagrantfile, > you *should* see a virtual interface (under Windows Network Connections). > That's what > happens on my laptop (but I use a Mac, but it's the same principle). > > Perhaps you can display your network connections? > > The idea is that since, a VM needs to establish the network interface > inside Vagrant/VirtualBox, > this is where it is failing. A VM OS will at times stall, indefinitely > while trying to obtain an IP > address, for instance, from a DHCP server. So in other words, if your > laptop/desktop has network > issues then it's possible it will affect VirtualBox. > > So let's start there. If you can show us Vagrantfile, your network > connections, and finally > if you can play with the boot options so that it displays a Linux boot > sequence then we can > track down your issue. > > Dennis > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/4739f2ec-1eb8-42d9-94dd-71ee7886a5aa%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
