{"action":"created","issue":{"url":"https://api.github.com/repos/mitchellh/vagrant/issues/6789","labels_url":"https://api.github.com/repos/mitchellh/vagrant/issues/6789/labels{/name}","comments_url":"https://api.github.com/repos/mitchellh/vagrant/issues/6789/comments","events_url":"https://api.github.com/repos/mitchellh/vagrant/issues/6789/events","html_url":"https://github.com/mitchellh/vagrant/issues/6789","id":124756654,"number":6789,"title":"Unable to start a machine on El Capitan copied from Ysemite","user":{"login":"codecowboy","id":178432,"avatar_url":"https://avatars.githubusercontent.com/u/178432?v=3","gravatar_id":"","url":"https://api.github.com/users/codecowboy","html_url":"https://github.com/codecowboy","followers_url":"https://api.github.com/users/codecowboy/followers","following_url":"https://api.github.com/users/codecowboy/following{/other_user}","gists_url":"https://api.github.com/users/codecowboy/gists{/gist_id}","starred_url":"https://api.github.com/users/codecowboy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/codecowboy/subscriptions","organizations_url":"https://api.github.com/users/codecowboy/orgs","repos_url":"https://api.github.com/users/codecowboy/repos","events_url":"https://api.github.com/users/codecowboy/events{/privacy}","received_events_url":"https://api.github.com/users/codecowboy/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/mitchellh/vagrant/labels/waiting-reply","name":"waiting-reply","color":"5319e7"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2016-01-04T13:10:34Z","updated_at":"2016-01-12T19:29:36Z","closed_at":null,"body":"I have tried copying over a vagrant box from a Yosemite install to a clean El Capitan install.\r\n\r\nThe procedure I used was this:\r\n\r\nCopied vagrant.d to the new user folder\r\nAdded machine to virtualbox manually\r\nChanged Virtualbox VM's directory in preferences (to a path which exists and contains all my old VMs, incuding the vagrant ones)\r\n\r\nIf I issue ```vagrant up```, vagrant imports the original base box (Centos in my case) and then creates a new box which I can see in Virtualbox. What I want is for vagrant to use the exact box I had before so that all my customisations are there.\r\n\r\nIn any case, the vagrant up command fails with the following error:\r\n\r\n```\r\nA customization command failed:\r\n\r\n[\"modifyvm\", :id, \"--name\", \"local.puphpet\"]\r\n\r\nThe following error was experienced:\r\n\r\n#<Vagrant::Errors::VBoxManageError: There was an error while executing `VBoxManage`, a CLI used by Vagrant\r\nfor controlling VirtualBox. The command and stderr is shown below.\r\n\r\nCommand: [\"modifyvm\", \"86fbe0b0-c119-4553-84b3-4596a7934e62\", \"--name\", \"local.puphpet\"]\r\n\r\nStderr: VBoxManage: error: Could not rename the directory '/Volumes/Data/Users/myuser/VirtualBox VMs/kickasscentos_default_1451911861767_76796' to '/Volumes/Data/Users/myuser/VirtualBox VMs/local.puphpet' to save the settings file (VERR_ALREADY_EXISTS)\r\nVBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component SessionMachine, interface IMachine, callee nsISupports\r\nVBoxManage: error: Context: \"SaveSettings()\" at line 3016 of file VBoxManageModifyVM.cpp\r\n>\r\n\r\nPlease fix this customization and try again.\r\n```\r\n\r\nThe suggestions here - https://github.com/mitchellh/vagrant/issues/6092 - have not worked for me."},"comment":{"url":"https://api.github.com/repos/mitchellh/vagrant/issues/comments/171025746","html_url":"https://github.com/mitchellh/vagrant/issues/6789#issuecomment-171025746","issue_url":"https://api.github.com/repos/mitchellh/vagrant/issues/6789","id":171025746,"user":{"login":"codecowboy","id":178432,"avatar_url":"https://avatars.githubusercontent.com/u/178432?v=3","gravatar_id":"","url":"https://api.github.com/users/codecowboy","html_url":"https://github.com/codecowboy","followers_url":"https://api.github.com/users/codecowboy/followers","following_url":"https://api.github.com/users/codecowboy/following{/other_user}","gists_url":"https://api.github.com/users/codecowboy/gists{/gist_id}","starred_url":"https://api.github.com/users/codecowboy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/codecowboy/subscriptions","organizations_url":"https://api.github.com/users/codecowboy/orgs","repos_url":"https://api.github.com/users/codecowboy/repos","events_url":"https://api.github.com/users/codecowboy/events{/privacy}","received_events_url":"https://api.github.com/users/codecowboy/received_events","type":"User","site_admin":false},"created_at":"2016-01-12T19:29:36Z","updated_at":"2016-01-12T19:29:36Z","body":"Thanks Seth!. Do you know of any way to work around the uid issue?  I'm not sure I understand what implication this problem has in the virtualbox / vagrant context. When is this checked by virtualbox?\r\n\r\nBy adding manually I mean launching Virtualbox and using the gui to add the machine from the files in the virtualbox vms folder - that is on a disk which was previously mounted on the old osx install so what you are saying about UIDs makes sense. A number of 'guides' online suggest doing this."}}