← Back to team overview

group.of.nepali.translators team mailing list archive

[Bug 1565985] Re: vagrant vb ubuntu/xenial64 cannot mount synced folders

 

This bug was fixed in the package livecd-rootfs - 2.408.3

---------------
livecd-rootfs (2.408.3) xenial-proposed; urgency=medium

  [ Louis Zuckerman ]
  * Fixes for vagrant box builder in ubuntu-cpc LP: #1565985
    - Install virtualbox-guest-utils
    - Don't disable default synced folder
    - Don't set vm name
    - Add cloud-init config to manage /etc/hosts LP: #1561250

 -- Brian Murray <brian@xxxxxxxxxx>  Tue, 30 Aug 2016 13:17:55 -0700

** Changed in: livecd-rootfs (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1565985

Title:
  vagrant vb ubuntu/xenial64 cannot mount synced folders

Status in cloud-images:
  In Progress
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Fix Released

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
  VBoxGuestAdditions.iso and is readable.

  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1565985/+subscriptions