Last modified: 2014-07-10 00:20:19 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T69575, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 67575 - Mounting shared folders for new VM fails (windows host)
Mounting shared folders for new VM fails (windows host)
Status: RESOLVED WONTFIX
Product: MediaWiki-Vagrant
Classification: Unclassified
General (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Ori Livneh
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-07-06 22:58 UTC by Yuri Astrakhan
Modified: 2014-07-10 00:20 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Yuri Astrakhan 2014-07-06 22:58:50 UTC
For latest master, rebuilding the box gives this at the end. Tried rebuilding box several times, on both 1.6.3 and 1.5.4

...
==> default: Mounting shared folders...
    default: /vagrant => C:/Users/user/mw/v
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 vagrant`,gid=`getent group www-data | cut -d: -f3` /vagrant /vagrant
mount -t vboxsf -o uid=`id -u vagrant`,gid=`id -g www-data` /vagrant /vagrant
Comment 1 Yuri Astrakhan 2014-07-09 23:19:58 UTC
This bug went away after fully removing vagrant dir, cloning it anew, moving old /mediawiki to it, and rebuilding. I suspect this had to do with the .settings having old box or that some packages were cached.
Comment 2 Bryan Davis 2014-07-10 00:20:19 UTC
I'm pretty sure this would be an upstream bug for VirtualBox or Vagrant if it was reproducible.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links