A bug with new version of Vagrant, Virtualbox and vagrant-vgguest

[inwoker]

Hi

When doing vagrant up with a newer than Virtualbox 7.0.14, it tries to update virtualbox guest additions and fails. As I understand it's related to newer version of ruby inside vagrant and no longer supported vagrant-vgguest plugin. Link of people discussing the issue:
hashicorp/vagrant#13404

There are two possible solutions that I found:

1. use a fork of vagrant-vbguest. But if I understand correctly it's beyond the scope of Homestead, but maybe not.
2. As a temporary solution I've added:

    if Vagrant.has_plugin?("vagrant-vbguest")
      config.vbguest.auto_update = false
    end

to Homestead Vagrantfile: Vagrant.configure block

I've also added stack.trace in attached file
stack.trace.txt

[skeeith]

@inwoker hm... awhile back I've encountered this issue, I have VB v7.1.4 currently now running fine.

Got different reports about installed GuestAdditions version:
Virtualbox on your host claims:   6.1.50
VBoxService inside the vm claims: 7.1.4
Going on, assuming VBoxService is correct...
[homestead] GuestAdditions 7.1.4 running --- OK.
Got different reports about installed GuestAdditions version:
Virtualbox on your host claims:   6.1.50
VBoxService inside the vm claims: 7.1.4
Going on, assuming VBoxService is correct...

@inwoker what have you tried to fix/mitigate this beside besides disabling auto_update? I'll try to recall what I did to fix this

@svpernova09 maybe we could run a command installing virtual box guest additions AFTER FIRST installing of homestead? what do you think or do you have a suggestion about this? Iet me know what you think I'll work on this. I have to recall what I did to install virtual box guest additions correctly.

I'm also planning to update the current node and npm default version to v24 LTS and MongoDB as well to v8, since I was the one who updated it last time too

[svpernova09]

@inwoker hm... awhile back I've encountered this issue, I have VB v7.1.4 currently now running fine.

Got different reports about installed GuestAdditions version:
Virtualbox on your host claims:   6.1.50
VBoxService inside the vm claims: 7.1.4
Going on, assuming VBoxService is correct...
[homestead] GuestAdditions 7.1.4 running --- OK.
Got different reports about installed GuestAdditions version:
Virtualbox on your host claims:   6.1.50
VBoxService inside the vm claims: 7.1.4
Going on, assuming VBoxService is correct...

@inwoker what have you tried to fix/mitigate this beside besides disabling auto_update? I'll try to recall what I did to fix this

@svpernova09 maybe we could run a command installing virtual box guest additions AFTER FIRST installing of homestead? what do you think? or do you have a suggestion about this? Iet me know what you think I'll work on this.

I'm also planning to update the current node and npm default version to v24 LTS, since I was the one who updated it last time too

The virtual box guest additions are installed in the base box, not at Homestead run time. Unfortunately, we're beholden to suffer whatever bugs Vagrant and any providers you use.

[skeeith]

@svpernova09 I see, going out of our necks to mitigate this will probably eat a lot of time, since they're also being update from time to time.

BTW I'm happy you continued this project outside of Laravel, I'm pretty sure my and my colleagues will still be using this in the near future as Herd is still young and is behind a pay wall.

[svpernova09]

@svpernova09 I see, going out of our necks to mitigate this will probably eat a lot of time, since they're also being update from time to time.

BTW I'm happy you continued this project outside of Laravel, I'm pretty sure my and my colleagues will still be using this in the near future as Herd is still young and is behind a pay wall.

Thanks for the kind words, wish I could do more here but the project has always struggled with VirtualBox :/

[skeeith]

@svpernova09 yeah, it's been a roller coaster ride with Virtual Box lately. I'm still happy that I see this project still being updated, cause Herd for me was a disappointment that they lock most of the free stuff behind a subscription that was all free in Homestead.

Since Laravel ignored all our request to keep this package and maintain it, I thought of helping you maintain this, there was also a guy back on the original repo that commented, that he wanted to help maintain this as well. Homestead is still way WAY better than Herd by a long shot, as you're able to actually do a lot of stuff on it or mimic infra and architecture configs or setups before deploying to production, not only that everything you need is actually there, unlike Herd you need to pay first and you barely get what you get on Homestead, so that's a bad thing for me.

Anyway, I'll be helping to maintain and improve this as much as I can on my free time, I was about to make a pull request for putting PHP-8.4 on this, but happy to see someone did it already.

I'll be making a pull request for updating NodeJS, npm, and MongoDB to current LTS version.

[skeeith]

@inwoker I've found a solution for this, just follow these steps.

Update FIRST your homestead server before doing this.

• Install the latest Ruby on your local machine (NOT on your VM)
• Then clone this repository https://github.com/dheerapat/vagrant-vbguest.git and go inside that repository.
• Run the following command gem build vagrant-vbguest.gemspec and then vagrant plugin install vagrant-vbguest-0.32.1.gem
• Then run vagrant up, it should upgrade your guest additions.

this also takes time, your server might also get stuck saying you need to reload or restart as your screen size doesn't reflect etc. just shut it down manually on your VM and run vagrant up again, but this is rare.

You might need to reload your server a couple of times to clean things up too.

Let me know how it goes

[inwoker]

@skeeith Yeah, I saw a suggestion of installing fork of vagrant-vgguest in some other place. Did not try it though. Thank you for exact steps.

[skeeith]

@inwoker let me or @svpernova09 know if it works, so he could close this, I'll be making an after installation command for this setup if I'm free.