I'm curious if there's a reason why the SyncedFolders middleware runs so 
early in the VirtualBox boot process, and if I were to submit a pull 
request to change the order if it would cause problems (or if it would be 
accepted).

Some background:

I'm working on a Vagrant plugin to help integrate SmartOS with Vagrant, 
particularly to help manage non-global zones (source code here: 
https://github.com/sax/vagrant-smartos-zones). I've made some progress, but 
syncing folders into local zones has been challenging. I realized yesterday 
that I can forgo the problem of syncing between the host and the local zone 
by syncing into the file system as seen by the global zone. For instance, 
if a local zone is created and it gets a uuid of <zone_uuid>, the global 
zone can access its file system at /zones/<zone_uuid>/root.

The problem is that the middleware for configuring synced folders runs 
before the VM (and thus the global zone) is accessible, and thus before my 
plugin can create a local zone and get its uuid.

I can get around this (and have in the latest commits of my plugin) by 
re-running the built-in middleware after the zones are created and I can 
manipulate the vm synced_folders configuration. It works for rsync, and I'm 
starting to play around with NFS. I don't know if there's a reason not to 
do this. I was also wondering if the order of the middleware could change 
to run after Vagrant::Action::Builtin::WaitForCommunicator, so that plugins 
like mine can hook into the configuration before it's parsed by Vagrant.

I'm also more than welcoming of other ideas for solving this problem if 
something is more vagrant-y. I'm not personally attached to the code 
already written, I just want to make enough features work that people can 
start using SmartOS with Vagrant.

-- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vagrant-up+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to