| 2018-10-08 09:48:41 |
John Patrick |
bug |
|
|
added bug |
| 2018-10-08 09:48:41 |
John Patrick |
attachment added |
|
what i see https://bugs.launchpad.net/bugs/1796647/+attachment/5198547/+files/cosmic64.log |
|
| 2018-10-08 09:48:59 |
John Patrick |
attachment added |
|
console log https://bugs.launchpad.net/cloud-images/+bug/1796647/+attachment/5198548/+files/ubuntu-cosmic-18.10-cloudimg-console.log |
|
| 2018-10-09 16:21:14 |
Dan Watkins |
cloud-images: status |
New |
Confirmed |
|
| 2018-10-09 16:21:16 |
Dan Watkins |
cloud-images: importance |
Undecided |
High |
|
| 2018-10-09 16:34:38 |
Dan Watkins |
summary |
ubuntu/cosmic64 vboxsf error |
Shared folders cannot be mounted in ubuntu/cosmic64 due to missing vbox modules |
|
| 2018-10-09 16:42:34 |
Dan Watkins |
description |
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
$ |
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
$ |
|
| 2018-10-09 16:42:57 |
Dan Watkins |
bug task added |
|
linux (Ubuntu) |
|
| 2018-10-09 17:00:06 |
Ubuntu Kernel Bot |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2018-10-09 17:00:07 |
Ubuntu Kernel Bot |
tags |
|
bionic |
|
| 2018-10-09 17:22:53 |
Dan Watkins |
bug |
|
|
added subscriber Dan Watkins |
| 2018-10-09 17:23:22 |
Dan Watkins |
tags |
bionic |
apport-collected bionic cosmic uec-images |
|
| 2018-10-09 17:23:26 |
Dan Watkins |
attachment added |
|
CurrentDmesg.txt https://bugs.launchpad.net/bugs/1796647/+attachment/5199143/+files/CurrentDmesg.txt |
|
| 2018-10-09 17:23:27 |
Dan Watkins |
attachment added |
|
Lspci.txt https://bugs.launchpad.net/bugs/1796647/+attachment/5199144/+files/Lspci.txt |
|
| 2018-10-09 17:23:29 |
Dan Watkins |
attachment added |
|
PciMultimedia.txt https://bugs.launchpad.net/bugs/1796647/+attachment/5199145/+files/PciMultimedia.txt |
|
| 2018-10-09 17:23:30 |
Dan Watkins |
attachment added |
|
ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1796647/+attachment/5199146/+files/ProcCpuinfo.txt |
|
| 2018-10-09 17:23:32 |
Dan Watkins |
attachment added |
|
ProcCpuinfoMinimal.txt https://bugs.launchpad.net/bugs/1796647/+attachment/5199147/+files/ProcCpuinfoMinimal.txt |
|
| 2018-10-09 17:23:33 |
Dan Watkins |
attachment added |
|
ProcInterrupts.txt https://bugs.launchpad.net/bugs/1796647/+attachment/5199148/+files/ProcInterrupts.txt |
|
| 2018-10-09 17:23:35 |
Dan Watkins |
attachment added |
|
ProcModules.txt https://bugs.launchpad.net/bugs/1796647/+attachment/5199149/+files/ProcModules.txt |
|
| 2018-10-09 17:23:36 |
Dan Watkins |
attachment added |
|
UdevDb.txt https://bugs.launchpad.net/bugs/1796647/+attachment/5199150/+files/UdevDb.txt |
|
| 2018-10-09 17:23:37 |
Dan Watkins |
attachment added |
|
WifiSyslog.txt https://bugs.launchpad.net/bugs/1796647/+attachment/5199151/+files/WifiSyslog.txt |
|
| 2018-10-09 17:23:57 |
Dan Watkins |
linux (Ubuntu): status |
Incomplete |
Confirmed |
|
| 2018-10-10 12:36:06 |
Francis Ginther |
tags |
apport-collected bionic cosmic uec-images |
apport-collected bionic cosmic id-5bbcaca75adf6a4fe571e8ad uec-images |
|
| 2018-10-10 13:36:53 |
Seth Forshee |
description |
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
$ |
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
$ |
|
| 2018-10-10 13:37:03 |
Seth Forshee |
linux (Ubuntu): importance |
Undecided |
High |
|
| 2018-10-10 13:37:03 |
Seth Forshee |
linux (Ubuntu): status |
Confirmed |
In Progress |
|
| 2018-10-10 13:37:03 |
Seth Forshee |
linux (Ubuntu): assignee |
|
Seth Forshee (sforshee) |
|
| 2018-10-10 13:37:10 |
Seth Forshee |
nominated for series |
|
Ubuntu Dd-series |
|
| 2018-10-10 13:37:10 |
Seth Forshee |
nominated for series |
|
Ubuntu Cosmic |
|
| 2018-10-10 13:37:10 |
Seth Forshee |
bug task added |
|
linux (Ubuntu Cosmic) |
|
| 2018-10-10 13:57:27 |
Gianfranco Costamagna |
bug |
|
|
added subscriber Gianfranco Costamagna |
| 2018-10-11 12:16:56 |
Seth Forshee |
linux (Ubuntu Cosmic): status |
In Progress |
Fix Committed |
|
| 2018-10-15 17:47:06 |
Dan Watkins |
cloud-images: status |
Confirmed |
Fix Released |
|
| 2019-02-14 13:11:03 |
Brad Figg |
tags |
apport-collected bionic cosmic id-5bbcaca75adf6a4fe571e8ad uec-images |
apport-collected bionic cosmic id-5bbcaca75adf6a4fe571e8ad uec-images verification-needed-bionic |
|
| 2019-02-14 16:54:39 |
Andy Whitcroft |
tags |
apport-collected bionic cosmic id-5bbcaca75adf6a4fe571e8ad uec-images verification-needed-bionic |
apport-collected bionic cosmic id-5bbcaca75adf6a4fe571e8ad kernel-fixup-verification-needed-bionic uec-images verification-done-bionic |
|
| 2019-07-24 20:56:17 |
Brad Figg |
tags |
apport-collected bionic cosmic id-5bbcaca75adf6a4fe571e8ad kernel-fixup-verification-needed-bionic uec-images verification-done-bionic |
apport-collected bionic cosmic cscc id-5bbcaca75adf6a4fe571e8ad kernel-fixup-verification-needed-bionic uec-images verification-done-bionic |
|
