It is a never ending story. New dist release, new problems with Virtualbox.
What is the current problem with a Fedora 30 guest on a Windows host and Virtualbox 6.0.8? Well, the guest additions won’t work, especially
vboxadd.service refuses to start.
After asking my search engine of choice it revealed the libxcrypt to be the culprit. There are some changes mentioned at https://fedoraproject.org/wiki/Releases/30/ChangeSet and it is referenced at https://forums.virtualbox.org/viewtopic.php?f=3&t=92953.
libxcrypt-compat package and the
vboxadd.service will start again, problem fixed.
This piece of hardware is from 1996. I found it in our old server room parked under a table next to a box with cables and rack equipment.
And then I remembered the time when I sat in front of it, doing sysadmin stuff with Novell Netware 4.2. Oh my, this was a long time ago!
What do you do if you find such a long forgotten treasure? You want to see if it will boot your favorite OS from back then, right? And it booted really fast into a DOS prompt: C:\>
The ver command revealed a Windows 98 installation. After firing win, good old Windows 98 booted into the beloved GUI. I immediately felt 20 years younger 😉
As it turned out, the PC Server was in very good shape, fully functional and booting super fast. Even the CMOS battery was alive. Wow.
Awestruck as I was I shut it down (well, I just hit power-off as in the good old days) and put it back under the table. There it is waiting for someone else cleaning up and wondering if it will boot one more time …
A quick overview of the most useful vagrant commands.
Hint: “ve” means vagrant environment – the virtual machine(s) you run.
|vagrant up||start ve
|vagrant halt||stop ve
|vagrant reload||reload Vagrantfile, restart ve
|vagrant destroy||destroy ve
|vagrant status||show status of ve(s)
|vagrant box list||show local baseboxes
|vagrant box add http://local.example.com/vagrant/box.json --box-version 2019.05.04||explicitly install a box from the given location and version
|vagrant box update||update all baseboxes currently installed
|vagrant box update --box prefix/boxname||update just the given basebox
|vagrant box prune||remove outdated baseboxes
|vagrant box prune --name prefix/boxname||remove just the given outdated baseboxes
|vagrant box remove prefix/boxname||remove all cached instances of the given basebox
|vagrant box remove prefix/boxname --box-version 2019.05.04||remove just the given basebox and version
|vagrant up --provision ve||provision the ve with all provisioners (again)
|vagrant up --provision-with ansible ve||provision the ve with ansible (again)
|vagrant reload --provision ve||reload Vagrantfile, restart the ve and provision it again
|vagrant provision ve||provision the running ve without restart
|vagrant provision --provision-with-ansible ve||provision the running ve with ansible and without restart
How to return to a previous version of a vagrant basebox
- remove any vagrant environment based on the basebox you want to remove:
- remove the basebox:
vagrant box remove prefix/basebox --box-version xyz
- if you already pruned the previous basebox you have to download it again:
vagrant box add http://local.example.com/vagrant/basebox.json --box-version xyz
- check if it is there:
vagrant box list
- create a new vagrant environment: