[Bug 1895862] Re: vboxsf unable to mount old binary data in Groovy Vagrant box

[Seth Forshee]

Though it seems like upstream basically says to either use their modules
together with their userspace tools, or else don't use their userspace
tools:

https://www.virtualbox.org/ticket/17728#no1

If we take that stance then shouldn't guest-utils have a hard dependency
on virtualbox-guest-dkms? Those driver will then have to be signed with
a MOK under secure boot, but I don't even know if virtualbox does secure
boot for guests, so that may be a non-issue.

** Bug watch added: Virtualbox Trac #17728
   http://www.virtualbox.org/ticket/17728

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/1895862

Title:
  vboxsf unable to mount old binary data in Groovy Vagrant box

Status in cloud-images:
  Confirmed
Status in cloud-images groovy series:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in virtualbox package in Ubuntu:
  Confirmed

Bug description:
  When booting the Groovy vagrant box, Guest Additions is unable to
  mount the shared folder

  
  ```
  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:

  /sbin/mount.vboxsf: mounting failed with the error: Invalid argument
  ```

  If one `vagrant ssh` into the box and try the command, it fails with
  the same error. systemctl and dmesg didn't show any errors. However,
  capturing the serial log showed the following on boot:

  ```
  ubuntu-groovy login: [   17.100243] vboxsf: Old binary mount data not supported, remove obsolete mount.vboxsf and/or update your VBoxService.
  [   17.219577] vboxsf: Old binary mount data not supported, remove obsolete mount.vboxsf and/or update your VBoxService.
  [   22.353951] vboxsf: Old binary mount data not supported, remove obsolete mount.vboxsf and/or update your VBoxService.
  [   27.412062] vboxsf: Old binary mount data not supported, remove obsolete mount.vboxsf and/or update your VBoxService.
  [  829.055100] vboxsf: Old binary mount data not supported, remove obsolete mount.vboxsf and/or update your VBoxService.
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1895862/+subscriptions