![]() * shiftfs: broken shiftfs nesting (LP: #1872094) SAUCE: overlayfs: use shiftfs hacks only with shiftfs as underlay * linux-image- 5.0.0-35- generic breaks checkpointing of container Remove vbox and zfs modules from generic. Move virtualbox modules to linux-modules * ubuntu/focal64 fails to mount Vagrant shared folders (LP: #1873506) SAUCE: overlayfs: fix shitfs special-casing * Unable to handle kernel pointer dereference in virtual kernel address space drm/i915: Limit audio CDCLK>=2*BCLK constraint back to GLK only * Intermittent display blackouts on event (LP: #1875254) This bug was fixed in the package linux - 5.4.0-31.35 Mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant ![]() This is not a bug in Vagrant and is usually caused by a faulty Please verify that these guest additions are properly installed in the Made available via the VirtualBox Guest Additions and kernel module. This is usuallyīecause the filesystem "vboxsf" is not available. Vagrant was unable to mount VirtualBox shared folders. Therefore the risk of regression is extremely low.Īttempting to `vagrant up` using the `ubuntu/focal64` box fails to mount the `/vagrant` shared folder. Regression Potential: Since linux-modules is required, anyone who is using the vbox drivers will continue to have them after this change. Test Case: Build the kernel packages and confirm that the vboxguest and vboxsf drivers are now in linux-modules rather than linux-modules- extra. This has caused the modules to go missing in our Vagrant images.įix: Move the modules back to linux-modules. 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.
0 Comments
Leave a Reply. |