Hi John,
I've just tested with the latest Vagrant box, and this looks good to me
now:
$ vagrant box update
==> default: Checking for updates to 'ubuntu/cosmic64'
default: Latest installed version: 20181008.0.0
default: Version constraints:
default: Provider: virtualbox
==> default: Updating 'ubuntu/cosmic64' with provider 'virtualbox' from version
==> default: '20181008.0.0' to '20181014.0.0'...
==> default: Loading metadata for box 'https://vagrantcloud.com/ubuntu/cosmic64'
==> default: Adding box 'ubuntu/cosmic64' (v20181014.0.0) for provider:
virtualbox
default: Downloading:
https://vagrantcloud.com/ubuntu/boxes/cosmic64/versions/20181014.0.0/providers/virtualbox.box
==> default: Successfully added box 'ubuntu/cosmic64' (v20181014.0.0) for
'virtualbox'!
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'ubuntu/cosmic64'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'ubuntu/cosmic64' is up to date...
==> default: Setting the name of the VM: vagrant_default_1539625374537_90792
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
default: Warning: Connection reset. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Connection reset. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Connection reset. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Connection reset. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Connection reset. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default:
default: Vagrant insecure key detected. Vagrant will automatically replace
default: this with a newly generated keypair for better security.
default:
default: Inserting generated public key within guest...
default: Removing insecure key from the guest if it's present...
default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Mounting shared folders...
default: /vagrant => /home/daniel/scratch/vagrant
$ vagrant ssh -- ls /vagrant
Vagrantfile
ubuntu-cosmic-18.10-cloudimg-console.log
$ ls -1
ubuntu-cosmic-18.10-cloudimg-console.log
Vagrantfile
I'm going to mark this bug as Fix Released; if you continue to see this
issue (after updating to the latest box!), please move it back to
Confirmed. For any other issues, please file a new bug.
Thanks again for the report!
** Changed in: cloud-images
Status: Confirmed => Fix Released
--
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/1796647
Title:
Shared folders cannot be mounted in ubuntu/cosmic64 due to missing
vbox modules
Status in cloud-images:
Fix Released
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Bug description:
SRU Justification
Impact: Vagrant environments are no longer able to use virtualbox
feartures like shared folders. This is due to Ubuntu Cosmic kernels
currently shipping the upstream vboxguest module and not importing
modules from the virtualbox-guest-dkms package.
Fix: One solution would be to use the dkms modules for Vagrant, but
this is not ideal. At this late stage the simplest solution is to go
back to importing the out-of-tree modules.
Regression Potential: Minimal. Will have no impact outside of
virtualbox environments, and the drivers being imported come from the
virtualbox-guest-dkms package in cosmic and are thus expected to work
well.
---
In bionic, the vboxsf module was included in linux-
modules-...-generic:
$ dpkg -c linux-modules-4.15.0-36-generic_4.15.0-36.39_amd64.deb | grep
vboxsf.ko
-rw-r--r-- root/root 63238 2018-09-24 10:08
./lib/modules/4.15.0-36-generic/kernel/ubuntu/vbox/vboxsf/vboxsf.ko
In cosmic, it isn't:
$ dpkg -c ~/Downloads/linux-
modules-4.18.0-9-generic_4.18.0-9.10_amd64.deb | grep vboxsf.ko
This results in shared folders no longer being mountable in Ubuntu
Vagrant boxes (and, as the other vbox modules are also missing,
probably has other effects that haven't yet been reported).
[Original Report]
Just tried to test out the new cosmic64 vagrant box and get the
following error;
```
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: No such device
```
I tried with ubuntu/bionic64 and it worked fine.
I've got;
$ vagrant version
Installed Version: 2.1.5
Latest Version: 2.1.5
You're running an up-to-date version of Vagrant!
$ VBoxManage --version
5.2.18r124319
$
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1796647/+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
