In general, if these don't work I'd recommend doing some searching on this error, and/or posting in a Vagrant or Virtualbox forum. I found a post that helps explain how to do this - I've never had to do this myself, so I can't personally recommend it - proceed with caution! For some users, they had to modify their computer BIOS settings to enable VT-x.Some users who were using 4.3.14 solved it by either downgrading to 4.3.12 or upgrading to 4.3.16 some using 4.3.16 solved it by upgrading to 5.x, etc. First disabling, and then re-enabling, the Virtualbox NDIS6 Bridged Networking Driver option - so even if it was already on, try disabling it, saving, then re-enabling, saving, and try the Vagrant box again, or:.Sounds like many people were able to resolve the issue by either: I've looked at some online forums, searching for your answer. I don't think this is specific to the AtoM vagrant box. that Windows is not creating new ones every time you try to boot, where this is not enabled). If you've double-checked that all Virtual Box connections have the Virtualbox NDIS6 Bridged Networking Driver option enabled (e.g. The box is apparently built using 64-bit, so it's possible that selecting 32-bit is causing issues. So it's possible that something went wrong with your first attempt, and then with this attempt, you were inadvertently using the remnants of the first installation attempt?
I'm guessing that you tried to follow the installation more than once, and there were perhaps some remnants from previous attempts - or from earlier versions of the vagrant box? I don't see the older init being removed, so when you ran vagrant up, I think Vagrant was trying to boot up whatever was in there previously, not the most recent download - the most recent one got placed in C:\Users\Lydia>. Second: I noticed that when you initially tried to create the atom-vagrant directory, your command prompt returned that such a subdirectory already existed - meaning it did not at that time make a new one, or switch you to it - you are still at C:\Users\Lydia> at the time that you ran vagrant init - then you seem to realize this, and switched into the existing directory, and tried to run the init command again, but the command prompt responds that there is already an init file in there, which you must remove before you can run it again.
0 kommentar(er)
