Hi folks, Sorry to open this old email chain. I'm facing the exact same problem as the OP and wanted to make sure I understood the workaround. I couldn't quite parse the last message in this thread
> > a. New proccess. > b. You set the HOME VBOX for that process > c. You use setproperty that will overrride the GLOBAL file in step b What does "no proccess" mean? How can setproperty be used to override the "GLOBAL file" in step b? It does not appear there is a way to locally override the virtualbox machinefolder, is there? Absent this workaround, what is the suggested way around this problem? I appreciate all the information in this thread, and want to make sure the workaround (if any) is well understood. Thanks, Srikanth On Tuesday, December 1, 2015 at 1:42:22 PM UTC-8, Alvaro Miranda Aguilera wrote: > > > On Wed, Dec 2, 2015 at 3:47 AM, <[email protected] <javascript:>> wrote: > >> he solution you offer though does not protect concurrent runs since >> setproperty is global. > > > > Hello, > > Just to close this look. > > a. New proccess. > b. You set the HOME VBOX for that process > c. You use setproperty that will overrride the GLOBAL file in step b > > If you do that per job, each job will get his own VirtualBox home and his > own global Virtualbox folder. > > > Thanks > > Alvaro. > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/36ae1e1e-1f20-48a7-ace0-7fe4dc971c5e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
