Looking at the upstream vboxsf driver, this "Old binary mount data not supported ..." message happens due to this old-style mount data being explicitly provided via mount(2). It seems to me that whatever is doing that (presumably /sbin/mount.vboxsf) should just retry the mount without the binary mount data if mount(2) returns EINVAL.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895862 Title: vboxsf unable to mount old binary data in Groovy Vagrant box To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1895862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
