For all new commenters -- what you're experiencing is a new bug with
similar symptoms, though slightly different root cause. Note the
original bug was "no device found" and this is "Invalid argument."
This appears to be a new bug. I don't see an identical bug to this new
issues, so i've opened
Further to my previous comment #21 above, I have found a workaround to
get the shared folders working again with the latest image. It appears
that the problem is with the virtualbox-guest-utils package included in
the image.
Here are the steps that I performed in order to get a virtualbox
I am also having the same "Invalid argument" error with 'ubuntu/focal64'
version '20210803.0.0' when doing vagrant up.
Manually running the mount command from inside the guest machine brings the
same error.
The host machine (also Ubuntu focal64) is running vagrant 2.2.18 and Virtualbox
6.1.22
I
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:
I still get the issue with the latest version of ubuntu/focal64 (several
versions checked: 20210803.0.0, 20210802.1.0, 20210624.0.0):
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'ubuntu/focal64'...
==> default: Matching MAC address for
This bug was fixed in the package linux - 5.4.0-42.46
---
linux (5.4.0-42.46) focal; urgency=medium
* focal/linux: 5.4.0-42.46 -proposed tracker (LP: #1887069)
* linux 4.15.0-109-generic network DoS regression vs -108 (LP: #1886668)
- SAUCE: Revert "netprio_cgroup: Fix
Yes, there is some lag. Although the image is named 0522, it was not
available until the 25th of May, note the created message from your
link:
"v20200522.0.0 currently released version
This version was created about 24 hours ago."
I did test the 0518 focal image and it was not fixed, 0522 is
Confirmed, it is available now and fixes the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873506
Title:
ubuntu/focal64 fails to mount Vagrant shared folders
To manage notifications about
apologies -- the 0518 Focal image has the fix as well. That may not have
been clear since the comments came on the 19th, and I updated on the
22nd. The eoan 22nd made it up on the 22nd, but there was lag with the
Focal 0522 serial syncing on our end. It's up there now.
--
You received this bug
May 22nd was made available when I commented. Not sure why your update
didn't find it. Maybe there's lag with specific mirrors. Official
listings show them available:
https://app.vagrantup.com/ubuntu/boxes/focal64
https://app.vagrantup.com/ubuntu/boxes/eoan64
--
You received this bug
New images do not appear to be available quite yet, still getting the
May 18 image.
$ vagrant box update
==> default: Checking for updates to 'ubuntu/focal64'
default: Latest installed version: 20200518.0.0
default: Version constraints:
default: Provider: virtualbox
==> default: Box
Focal and Eoan boxes with the above kernels have been pushed to Vagrant
and verified. Please run a `vagrant box update` to get the latest
versions.
** Changed in: cloud-images
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: cloud-images
Assignee: (unassigned) => John Chittum (jchittum)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873506
Title:
ubuntu/focal64 fails to mount Vagrant shared folders
This bug was fixed in the package linux - 5.3.0-53.47
---
linux (5.3.0-53.47) eoan; urgency=medium
* eoan/linux: 5.3.0-53.47 -proposed tracker (LP: #1877257)
* Intermittent display blackouts on event (LP: #1875254)
- drm/i915: Limit audio CDCLK>=2*BCLK constraint back to GLK
This bug was fixed in the package linux - 5.4.0-31.35
---
linux (5.4.0-31.35) focal; urgency=medium
* focal/linux: 5.4.0-31.35 -proposed tracker (LP: #1877253)
* Intermittent display blackouts on event (LP: #1875254)
- drm/i915: Limit audio CDCLK>=2*BCLK constraint back to
Ok, I tested 5.3.0-52-generic on eoan, the modules are present, the
system boots and runs normally.
vagrant@ubuntu-eoan:~$ ls -1
/lib/modules/5.3.0-52-generic/kernel/virtualbox-guest/*
/lib/modules/5.3.0-52-generic/kernel/virtualbox-guest/vboxguest.ko
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873506
Title:
ubuntu/focal64 fails to mount Vagrant shared folders
I performed a test with 5.4.0-30-generic on focal. The update in
proposed fixes the problem for me as it provides the necessary kernel
modules. I have not seen any problems with the new kernel version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag
Not sure how to test this as requested by the bot. I don't think just
enabling proposed on an existing published image is sufficient. Are
there proposed cloud image builds posted somewhere?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
eoan' to 'verification-done-eoan'. If the problem still exists, change
the tag
** Changed in: linux (Ubuntu Eoan)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu Eoan)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873506
Fix sent: https://lists.ubuntu.com/archives/kernel-
team/2020-April/109405.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873506
Title:
ubuntu/focal64 fails to mount Vagrant shared folders
To
** Description changed:
- 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:
+ SRU Justification
+
+ Impact: When our kernel packaging was updated to build the
** Project changed: linux => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu)
Assignee:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873506
Title:
27 matches
Mail list logo
