-
-
Notifications
You must be signed in to change notification settings - Fork 646
[vagrant-hostsupdater] error with drupalvm #2067
Comments
Just searching for your error message I found a couple issues - are they helpful? |
I managed to resolve this by downgrading the version og virtualbox from 6.1.10 to 6.1.4 |
I am setting up a new dev laptop today (Win10 Pro 2004 update), so using very latest Vagrant (2.2.9), Drupal VM and VirtualBox (6.1.12 r139181) and just did a test Vagrant Up - I have exactly the same error message at the same point. I tried running VirtualBox and having it 'show' but that did not work for me. There is a mismatch on the GuestAdditions, so maybe that is why the downgrade that was tried by amine-betari worked. I'll downgrade and see if that works. |
I was facing a very similar error when using vagrant-vbguest plugin to automatically match the guest additions version on the box. Took me 2 days to find this post. Downgrading now to test. @chumkui Same here. I upgraded to Windows 10 Pro 2004 over the weekend. Updated Vagrant to 2.2.9 and VirtualBox to 6.1.12.r139181 - and my dev environment completely stopped working. I've wasted 2 days trying to destroy and re-create boxes. Only to have something or the other fail - either ubuntu apt updates would fail OR npm fails. My first today move is going to be to revert back to the previous version of VirtualBox v6.1.4 r136177 (this used to work perfectly fine for me along with Vagrant 2.2.7). I'll update this post incase someone else ends up facing this same error and sees this. I would not wish what I went through the last 48+hours on ANYONE. |
Downgraded to VirtualBox v6.1.4 r136177, and Vagrant v2.2.7 - still facing the same issue. has anyone else had better luck with this? |
I've managed to get my development environment working again - Check here for other solutions that worked for some other people. The solution in my case was to use "virtualbox" as the type for synced_folders -
And also, inside the config specific to provider -
Note that /vagrant is the path I use inside my virtual machine - therefore that's the path added at the end of SharedFoldersEnableSymlinksCreate. These 2 changes fixed all my problems. Back to productive work!! |
I ran into this problem as well.
Now if the hostsupdater does not work, can we get around 2. manually? It appears: yes, we can. What I did: Since I normally shut down my machine into hibernation instead of restarting it, I will not have to do a vagrant up each time. This is not a permanent solution and sure hacky and not pretty - but when vagrant runs, everything inside the VM works as expected and I can do productive work again. --- Edit --- |
Hi,
I'm trying to execute a vagrant up to mount my drupal VM in order to setup a BLT project.
I get this error :
My configuration:
Windows 10
wsl 1
vagrant 2.2.9
virtualbox 6.1
blt 10
I have already installed vagrant-hostaupdater, vagrant-vbguest . launched the powershell as admin. checked the hosts file permission. none of this worked ?
any help please ?
thanks
The text was updated successfully, but these errors were encountered: