I still get the issue with the latest version of ubuntu/focal64 (several
versions checked: 20210803.0.0, 20210802.1.0, 20210624.0.0):
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'ubuntu/focal64'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'ubuntu/focal64' version '20210624.0.0' is up to
date...
==> default: Setting the name of the VM: pxeserver_default_1628068101055_78025
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
default: Warning: Connection reset. Retrying...
default:
default: Vagrant insecure key detected. Vagrant will automatically replace
default: this with a newly generated keypair for better security.
default:
default: Inserting generated public key within guest...
default: Removing insecure key from the guest if it's present...
default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Mounting shared folders...
default: /vagrant => /home/***/***/***
Vagrant was unable to mount VirtualBox shared folders. This is usually
because the filesystem "vboxsf" is not available. This filesystem is
made available via the VirtualBox Guest Additions and kernel module.
Please verify that these guest additions are properly installed in the
guest. This is not a bug in Vagrant and is usually caused by a faulty
Vagrant box. For context, the command attempted was:
mount -t vboxsf -o uid=1000,gid=1000,_netdev vagrant /vagrant
The error output from the command was:
: Invalid argument
$ vagrant --version
Vagrant 2.2.16
$ pacman -Qi virtualbox | grep Version
Version : 6.1.26-1
$ pacman -Qi virtualbox-ext-oracle | grep Version
Version : 6.1.26-1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1873506
Title:
ubuntu/focal64 fails to mount Vagrant shared folders
Status in cloud-images:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Eoan:
Fix Released
Status in linux source package in Focal:
Fix Released
Bug description:
SRU Justification
Impact: When our kernel packaging was updated to build the virtualbox
guest packages by downloading the dkms package, the modules were
accidentally moved to linux-modules-extra instead of linux-modules.
This has caused the modules to go missing in our Vagrant images.
Fix: Move the modules back to linux-modules.
Test Case: Build the kernel packages and confirm that the vboxguest
and vboxsf drivers are now in linux-modules rather than linux-modules-
extra.
Regression Potential: Since linux-modules is required, anyone who is
using the vbox drivers will continue to have them after this change.
Therefore the risk of regression is extremely low.
---
Attempting to `vagrant up` using the `ubuntu/focal64` box fails to mount the
`/vagrant` shared folder. `ubuntu/bionic64` works as expected. Here is the
Vagrant error message:
Vagrant was unable to mount VirtualBox shared folders. This is usually
because the filesystem "vboxsf" is not available. This filesystem is
made available via the VirtualBox Guest Additions and kernel module.
Please verify that these guest additions are properly installed in the
guest. This is not a bug in Vagrant and is usually caused by a faulty
Vagrant box. For context, the command attempted was:
mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant
The error output from the command was:
: No such device
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1873506/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
