I am also having error "Invalid argument" as shown in #19 comment.

Vagrant says:

mount -t vboxsf -o uid=1000,gid=1000,_netdev dist /dist

The error output from the command was:

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


dmesg says:

[   10.792892] vboxsf: g_fHostFeatures=0x8000000f g_fSfFeatures=0x1 
g_uSfLastFunction=29
[   10.792962] vboxsf: Successfully loaded version 6.1.16_Ubuntu
[   10.792987] vboxsf: Successfully loaded version 6.1.16_Ubuntu on 
5.4.0-80-generic SMP mod_unload modversions  (LINUX_VERSION_CODE=0x5047c)
[   10.807936] 19:53:39.226512 main     VBoxService 6.1.22_Ubuntu r144080 
(verbosity: 0) linux.amd64 (Jun 22 2021 07:15:58) release log
               19:53:39.226514 main     Log opened 
2021-08-06T19:53:39.226504000Z
[   10.807994] 19:53:39.226603 main     OS Product: Linux
[   10.808053] 19:53:39.226650 main     OS Release: 5.4.0-80-generic
[   10.808126] 19:53:39.226749 main     OS Version: #90-Ubuntu SMP Fri Jul 9 
22:49:44 UTC 2021
[   10.808160] 19:53:39.226778 main     Executable: /usr/sbin/VBoxService
               19:53:39.226779 main     Process ID: 792
               19:53:39.226779 main     Package type: LINUX_64BITS_GENERIC (OSE)
[   10.819491] 19:53:39.238084 main     6.1.22_Ubuntu r144080 started. Verbose 
level = 0
[   10.820412] 19:53:39.239016 main     
vbglR3GuestCtrlDetectPeekGetCancelSupport: Supported (#1)
[   16.552729] vboxsf: Invalid info signature: 0x75 0x69 0x64 0x3d!
[   16.552731] vbsf_read_super_aux err=-22
[   16.574695] vboxsf: Invalid info signature: 0x75 0x69 0x64 0x3d!
[   16.574697] vbsf_read_super_aux err=-22
[   21.608093] vboxsf: Invalid info signature: 0x75 0x69 0x64 0x3d!
[   21.608095] vbsf_read_super_aux err=-22
[   26.638080] vboxsf: Invalid info signature: 0x75 0x69 0x64 0x3d!
[   26.638082] vbsf_read_super_aux err=-22

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

Reply via email to