ProblemType: Bug AlsaDevices: total 0 crw-rw---- 1 root audio 116, 1 Oct 9 16:18 seq crw-rw---- 1 root audio 116, 33 Oct 9 16:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcEnviron: LC_CTYPE=C.UTF-8 TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: cosmic uec-images Uname: Linux 4.18.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH
** Tags added: apport-collected cosmic uec-images -- 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: Confirmed Status in linux package in Ubuntu: Confirmed Bug 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 $ 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