vagrant vb ubuntu/xenial64 cannot mount synced folders
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-images |
Fix Released
|
Undecided
|
Patricia Gaughen | ||
livecd-rootfs (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Xenial |
Fix Released
|
High
|
Brian Murray |
Bug Description
I am unable to fully provision a xenial instance using box
ubuntu/xenial64 (virtualbox, 20160403.0.0)
because the synced folders are never mounted.
VAGRANT_LOG=DEBUG vagrant init --debug indicates that there was an error mounting the filesystem
mount: unknown filesystem type 'vboxsf'
I am using
VirtualBox 5.0.16 r105871
vagrant 1.8.1
While init/provision fails, the instance is brought up. I can get into it and see it runs. It doesn't appear that Virtualbox Guest Additions is installed. I can see that my installation of VB does have VBoxGuestAdditi
X-CPC-Real-Bug: bug 1605795
Test procedure for proposed fix:
1. Launch the ubuntu vagrant box (xenial, yakkety)
2. SSH into the box with `vagrant ssh`
3. Check if default synced folder, /vagrant, is mounted with `mount` or `df`, it should be
4. Check name of VM in virtualbox, it should be randomized
Related branches
- Steve Langasek: Needs Fixing
- Dan Watkins (community): Approve
-
Diff: 165 lines (+51/-30) (has conflicts)2 files modifieddebian/changelog (+15/-0)
live-build/ubuntu-cpc/hooks/042-vagrant.binary (+36/-30)
Changed in cloud-images: | |
status: | New → Confirmed |
information type: | Public → Public Security |
information type: | Public Security → Public |
Changed in cloud-images: | |
status: | Confirmed → In Progress |
Changed in vagrant: | |
status: | New → Invalid |
Changed in cloud-images: | |
milestone: | y-2016-06-30 → y-2016-07-14 |
Changed in livecd-rootfs (Ubuntu): | |
importance: | Undecided → High |
Changed in cloud-images: | |
milestone: | y-2016-07-14 → y-2016-07-28 |
description: | updated |
Changed in cloud-images: | |
milestone: | y-2016-07-28 → y-2016-08-11 |
Changed in cloud-images: | |
milestone: | y-2016-08-11 → y-2016-08-25 |
Changed in cloud-images: | |
assignee: | Dan Watkins (daniel-thewatkins) → Patricia Gaughen (gaughen) |
affects: | vagrant → ubuntu |
no longer affects: | ubuntu |
Changed in cloud-images: | |
milestone: | y-2016-08-25 → y-2016-09-08 |
Changed in livecd-rootfs (Ubuntu Xenial): | |
status: | New → In Progress |
importance: | Undecided → High |
assignee: | nobody → Brian Murray (brian-murray) |
description: | updated |
description: | updated |
Changed in cloud-images: | |
status: | In Progress → Fix Released |
When I attempted to reprovision the instance, I saw a warn about guest additions, then an error when the vagrant attempted to mount the synced folder:
==> default: Machine booted and ready! curtis/ Sites/Work
==> default: Checking for guest additions in VM...
default: No guest additions were detected on the base box for this VM! Guest
default: additions are required for forwarded ports, shared folders, host only
default: networking, and more. If SSH fails on this machine, please install
default: the guest additions and repackage the box to continue.
default:
default: This is not an error message; everything may continue to work properly,
default: in which case you may ignore this message.
==> default: Checking for host entries
==> default: Mounting shared folders...
default: /home/curtis/Work => /Users/
Failed to mount folders in Linux guest. This is usually because
the "vboxsf" file system is not available. Please verify that
the guest additions are properly installed in the guest and
can work properly. The command attempted was:
mount -t vboxsf -o uid=`id -u curtis`,gid=`getent group curtis | cut -d: -f3` home_curtis_Work /home/curtis/Work
mount -t vboxsf -o uid=`id -u curtis`,gid=`id -g curtis` home_curtis_Work /home/curtis/Work
The error output from the last command was:
mesg: ttyname failed: Inappropriate ioctl for device
/sbin/mount.vboxsf: mounting failed with the error: No such device
I sshed into the instances, downloaded guest additions, mounted it, installed build-essential, and installed the additions.
After halting and uping the instance, synced_folders worked without error.