New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vagrant up takes long time after installing guest additions manually in centos box #6812
Comments
same error here, any clue? I have been throughout this since last 3 days :/ |
Hi @akaSStalkALEX Can you please share your complete Vagrantfile and the output of the command in debug mode as a github gist? |
My up log https://gist.github.com/akaSStalkALEX/6315b40683fc7c9d64cc. I replaced some personal info in directory pathes mainly and also I recreated box again, timeout error has gone, but it still executes quite long and ssh connecting problems present as I understand from log. |
@sethvargo @akaSStalkALEX Same issue here on my personal laptop. On my professional computer which is really faster, I dont get the error. The project is the same, and all versions tools are the same, execpt I run Windows 10 on this one vs windows 7 on my personal laptop. I think that the answer for this is in the question. I randomly get the same issue as you, or sometimes this one
Upgrading Vagrant config to use 4 CPUs and 2048 Gb RAM (like what I use on my professional computer) doesn't solve the problem, and the process still looks really slow... Windows 7 Home x64 Just ask if you want some more logs. |
Wow, so strange ... As a windows user, I'm using Pageant as ssh-agent with my key loaded into it. I've try to close it, then I re-opened a new terminal and I loaded my key manually using
And it worked, Vagrant Up successfull .... Wuuuuut ? oO Additional note : I use Git for windows linked to plink.exe during installation. @akaSStalkALEX By chance, are you running Vagrant on Windows ? |
@tlartaud I'm using Vagrant on Win 10 and ssh agent from Git's latest version. PC configuration has nothing to do with current problem. Error came out after updating Vagrant from 1.7.4 to 1.8.0 on the same PC. I was a bit wrong at the beginning doing my assumptions. Here's some lines from my up log.
As I understand Vagrant using ssh-agent makes one connection at the beginning and then for all (or maybe not and I'm mistaken?) commands uses the same connection: |
yeah, I had the same output and I cannot figure out if this happens randomly or in some specific cases. But apparently, this is not related to pageant ^^ I think it just randomly fail. |
@akaSStalkALEX
Hey, you are giving me an idea ! In your Vagrantfile, try to turn off natdnshostresolver1 ?
|
I fixed my problem uninstalling the whole vagrant, including it (users/system) files. Here what I did https://laracasts.com/discuss/channels/laravel/homestead-up-problemas?page=0#reply-130684 hope it can help a little bit |
Same here. I didn't have this problem on the 1.7.x version of Vagrant, and this issue is happening since I update Vagrant with the latest version 1.8.1. Hope it can help, and we'll find a solution soon. |
Same problem here using vccw. But some times it works '-'. I'm on OS X 10.11.3 (El Capitan) using Vagrant 1.8.1 and VirtualBox 5.0.14. debug mode log: https://gist.github.com/victorbaraonunes/3f34ada42f1cd4823a92 |
same here |
I installed vbguest plugin and it seems to have fixed the issue. |
@joshuaadickerson "...also I have vbguest plugin..." |
Are there any updates on this? I have the same issue OS: OS X 10.11.3 |
Setting |
I have to revise that. It only temporarily fixes this issue, but when I turn |
After hours and hours of not be able to fix this issue, I reinstalled OSX and it is working again |
Hi all, Thank you for opening an issue. I spent a lot of time with redhat and centos guests and I was unable to reproduce this issue on Vagrant 1.8.3. Is this still occurring? |
I'm seeing this issue:
|
@sethvargo This is still happening as of today. This is my vagrant file:
|
Still an issue |
Hi there, Thanks for reporting this bug. I'm sure this was a real issue when originally reported (our fault for not looking sooner!) but there have been multiple Vagrant releases since the original report. I'm going to close this issue now and request you reopen the issue if you're still experiencing this problem. I'm sorry this wasn't looked at earlier Cheers! |
Still having the issue on Windows 10 and fresh install from today with latest versions of Vagrant 1.9.2 and |
After all updates I had all the same problems as on the moment I reported this issue. So I just recreated vm, now it works as it should be. I think it somehow connected with yum updates inside vm, I regularly updated my vm and after one of the updates it started working with bugs. But I'm not sure. |
Same issue after upgrading from 1.8.5 to 1.9.3;
did not work. I have destroyed the machine and tried recreating it several times. On Ubuntu Trusty (14.04). vagrant up --debug output:
Out of ideas for today. It looks like a connection is established but that the error happens during/after negotiating protocol? Any ideas on what that could be? |
So, do you think updating the vm and vagrant version is a good solution ? |
Same here with a fresh VCCW install. UPDATE: uninstalling and installing Vagrant seemed to work. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Not sure how to describe issue correctly whether this is bug or not. So I initialized centos/7 box, also I have vbguest plugin and it tried to install guest additions as usual during vagrant up command executing. Installation of one of the modules failed. I installed guest additions manually but before it yum update command was executed to fix building failed module. After these actions plugin showed GuestAdditions 5.0.12 running --- OK. But I get problem: vagrant up command executing time instead of seconds becomes almost 5-10 minutes. Sometimes it doesn't execute at all. It started to hangs on booting machine, checking guest additions, mounting folders. I tried debug option and as I understand vagrant was not able to define version of virtual machine. There was long time loop before each command during "up" trying to sort out different versions of Linux(ubuntu, debian, arch, funtoo etc.) and also I saw error "failed connecting to ssh agent" something like that. Not sure if it is bug of vagrant or this plugin.
The text was updated successfully, but these errors were encountered: