ubuntu/focal64 fails to mount Vagrant shared folders
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-images |
Fix Released
|
Undecided
|
John Chittum | ||
linux (Ubuntu) |
Fix Released
|
High
|
Seth Forshee | ||
Eoan |
Fix Released
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned |
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-
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
CVE References
Changed in cloud-images: | |
status: | New → Confirmed |
tags: | added: id-5ea2fffbe0f69035134ff94f |
affects: | linux → linux (Ubuntu) |
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
assignee: | nobody → Seth Forshee (sforshee) |
importance: | Undecided → High |
status: | Confirmed → In Progress |
description: | updated |
Changed in linux (Ubuntu Eoan): | |
status: | New → In Progress |
Changed in linux (Ubuntu Focal): | |
status: | New → In Progress |
Changed in linux (Ubuntu Eoan): | |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu Focal): | |
status: | In Progress → Fix Committed |
tags: |
added: verification-done-focal removed: verification-needed-focal |
Changed in cloud-images: | |
assignee: | nobody → John Chittum (jchittum) |
This problem can be worked around with the vagrant-vbguest plugin and VirtualBox 6.0.20 r137117 (Qt5.6.3). With VirtualBox 6.0.6 the plugin was not able to fix it because the guest additions would not compile for the included kernel. This does make the start-up time much slower because they are found to be missing and compiled on the fly during `vagrant up`.