Re: [vagrant-up] Re: mysterious errors with concurrent vagrant cmds: Could not find a registered machine with UUID

On Wed, Dec 2, 2015 at 3:47 AM, 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

Re: [vagrant-up] Re: mysterious errors with concurrent vagrant cmds: Could not find a registered machine with UUID

I understand better the issue you've described. The solution you offer though does not protect concurrent runs since setproperty is global. I've ended up patching the vagrant driver for kitchen to include a lock (per user) around vagrant up. Thanks a lot for your help. -- Grégoire -- This

Re: [vagrant-up] Re: mysterious errors with concurrent vagrant cmds: Could not find a registered machine with UUID

Thanks Alvaro for your answer. I have succeeded to set a machinefolder using the following command: > VBoxManage setproperty machinefolder "/home/jenkins/vbox/" This modifies the .config/VirtualBox/VirtualBox.xml to contain: > I could run the setproperty command before each job uses

Re: [vagrant-up] Re: mysterious errors with concurrent vagrant cmds: Could not find a registered machine with UUID

Hello, My suggestion is to create one VBOX_USER_HOME and run the other command per job so each job will have his own VBOX_USER_HOME folder, in this way parallel runs will be run on separate VBOX folders. and setproperty will be run and configure that VBOX_USER_HOME config, so need to be unique

Re: [vagrant-up] Re: mysterious errors with concurrent vagrant cmds: Could not find a registered machine with UUID

Thanks Alvarro for your answer. We have the same setup as Chris, a jenkins cluster launching `kitchen test --concurrency=2`. The jenkins cluster uses mesos plugin to launch jenkins slave on our mesos cluster. There are multiple jenkins slaves running on a physical mesos slave and they all uses

Re: [vagrant-up] Re: mysterious errors with concurrent vagrant cmds: Could not find a registered machine with UUID

Hello. Do you use Virtualbox? I think I know the answer. It was some messages back on the same email thread, https://groups.google.com/d/msg/vagrant-up/UeGrB82PSTs/ad6JTz6AsQkJ If you are using the same user same source box, etc, you can have some collisions: Try to setup this as part of the

Re: [vagrant-up] Re: mysterious errors with concurrent vagrant cmds: Could not find a registered machine with UUID

Hello, About the solution you suggest, I am concerned the setproperty is a global operation that will not isolate builds if several tests are running in parallel. Could you infirm that hypothesis? Anyway the command you gave has some weird answer: > VBoxManage: error: Given default machine

Re: [vagrant-up] Re: mysterious errors with concurrent vagrant cmds: Could not find a registered machine with UUID

Hello, That error (from the subject) can happen in several cases. - When you copy a folder and that include a .vagrant folder, you can delete the folder and do vagrant up and that will create a new box. This apply to projectd where they don't ignore this folder. - You have some shared folder