$ vagrant plugin uninstall vagrant-vbguest
Uninstalling the 'vagrant-vbguest' plugin...
Successfully uninstalled micromachine-3.0.0
Successfully uninstalled vagrant-vbguest-0.29.0
frankie@legolas:~/vagrant
$ vagrant plugin list
No plugins installed.
frankie@legolas:~/vagrant
$ vagrant destroy testing1
testing1: Are you sure you want to destroy the 'testing1' VM? [y/N] y
==> testing1: Forcing shutdown of VM...
==> testing1: Destroying VM and associated drives...
frankie@legolas:~/vagrant
$ vagrant up testings1
^Cfrankie@legolas:~/vagrant
$ vagrant up testing1
Bringing machine 'testing1' up with 'virtualbox' provider...
==> testing1: Importing base box 'debian/testing64'...
==> testing1: Matching MAC address for NAT networking...
==> testing1: Checking if box 'debian/testing64' version '20210207.1' is
up to date...
==> testing1: Setting the name of the VM: testing1
==> testing1: Clearing any previously set network interfaces...
==> testing1: Preparing network interfaces based on configuration...
testing1: Adapter 1: nat
testing1: Adapter 2: hostonly
==> testing1: Forwarding ports...
testing1: 22 (guest) => 2222 (host) (adapter 1)
==> testing1: Running 'pre-boot' VM customizations...
==> testing1: Booting VM...
==> testing1: Waiting for machine to boot. This may take a few minutes...
testing1: SSH address: 127.0.0.1:2222
testing1: SSH username: vagrant
testing1: SSH auth method: private key
testing1:
testing1: Vagrant insecure key detected. Vagrant will automatically
replace
testing1: this with a newly generated keypair for better security.
testing1:
testing1: Inserting generated public key within guest...
testing1: Removing insecure key from the guest if it's present...
testing1: Key inserted! Disconnecting and reconnecting using new SSH
key...
==> testing1: Machine booted and ready!
==> testing1: Checking for guest additions in VM...
testing1: The guest additions on this VM do not match the installed
version of
testing1: VirtualBox! In most cases this is fine, but in rare cases
it can
testing1: prevent things such as shared folders from working
properly. If you see
testing1: shared folder errors, please make sure the guest additions
within the
testing1: virtual machine match the version of VirtualBox you have
installed on
testing1: your host and reload your VM.
testing1:
testing1: Guest Additions Version: 6.0.0 r127566
testing1: VirtualBox Version: 6.1
==> testing1: Setting hostname...
==> testing1: Configuring and enabling network interfaces...
==> testing1: Mounting shared folders...
testing1: /vagrant => /home/frankie/vagrant
==> testing1: Machine 'testing1' has a post `vagrant up` message. This
is a message
==> testing1: from the creator of the Vagrantfile, and not from Vagrant
itself:
==> testing1:
==> testing1: Vanilla Debian box. See https://app.vagrantup.com/debian
for help and bug reports
This looks good to me. Vagrant/Virtualbox on testing are using the
mainline kernel guest additions, probably with a fake Virtualbox version.
You can see on the guest that the additions come from mainline kernel:
dpkg --search
/lib/modules/5.10.0-3-amd64/kernel/drivers/virt/vboxguest/vboxguest.ko
/lib/modules/5.10.0-3-amd64/kernel/fs/vboxsf/vboxsf.ko
linux-image-5.10.0-3-amd64:
/lib/modules/5.10.0-3-amd64/kernel/drivers/virt/vboxguest/vboxguest.ko
linux-image-5.10.0-3-amd64:
/lib/modules/5.10.0-3-amd64/kernel/fs/vboxsf/vboxsf.ko
