Hi, Thanks for that direction. I am able to create a directory in C:/users/Acer. and then do the vagrant up from there.
The first time it downloaded the box and came to the command Booting VM.. and then went into an invalid state. After a vagrant halt and vagrant up again, it continues past that point and removed the in-secure and installed a new one, then updated the Guest versions that were not matching with the version of Virtual Box. Gave the following error : *Got different reports about installed GuestAdditions version:* *Virtualbox on your host claims: 4.2.0* *VBoxService inside the vm claims: 5.1.16* *Going on, assuming VBoxService is correct...* *Got different reports about installed GuestAdditions version:* *Virtualbox on your host claims: 4.2.0* *VBoxService inside the vm claims: 5.1.16* *Going on, assuming VBoxService is correct...* *Got different reports about installed GuestAdditions version:* *Virtualbox on your host claims: 4.2.0* *VBoxService inside the vm claims: 5.1.16* *Going on, assuming VBoxService is correct...* *Restarting VM to apply changes...* *==> default: Attempting graceful shutdown of VM...* *==> default: Booting VM...* *==> default: Waiting for machine to boot. This may take a few minutes...* * default: SSH address: 127.0.0.1:2222 <http://127.0.0.1:2222>* * default: SSH username: vagrant* * default: SSH auth method: private key* *==> default: Checking for guest additions in VM...* * default: The guest additions on this VM do not match the installed version o* *f* * default: VirtualBox! In most cases this is fine, but in rare cases it can* * default: prevent things such as shared folders from working properly. If you* * see* * default: shared folder errors, please make sure the guest additions within t* *he* * default: virtual machine match the version of VirtualBox you have installed* *on* * default: your host and reload your VM.* * default:* * default: Guest Additions Version: 4.2.0* * default: VirtualBox Version: 5.1* *The guest machine entered an invalid state while waiting for it* *to boot. Valid states are 'starting, running'. The machine is in the* *'unknown' state. Please verify everything is configured* *properly and try again.* By the way, I even tried the vagrant up with the GUI enabled and it gets stuck waiting for the network devices and waits for like 120 seconds and continues without the settings for that and it happens again down the line and finally it boots there. Meanwhile the bash window times out saying another process, (the GUI is accessing the processes) Last evening I tried this for trusty32 and for bento32, but this is what happened each time OR it got stuck with no access at the index,lock files. Should I revert back to the previous version of VB? Any other option ? Thanks loads ! On Tue, Mar 14, 2017 at 3:54 AM, Alvaro Miranda Aguilera <[email protected]> wrote: > > On Mon, Mar 13, 2017 at 12:24 PM, Ap Seh <[email protected]> wrote: > >> C:/Users/Acer > > > Hello > > the best is open a cmd.exe window > and go to a directory insude your user. > > see if you can create a directory > and do the vagrant init -m hashicorp/precise32 > vagrant up > > per your message, is seems there is no access to *C:/Users/Acer home > directory from the user you are using.* > > > > > -- > 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 a topic in the > Google Groups "Vagrant" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/vagrant-up/R2gPXfXxnGQ/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/vagrant-up/CAHqq0eyNh-ndL1ktdsQ-E0g-yfWEtPCdW0VjQ7vKfzV0H3JnsQ% > 40mail.gmail.com > <https://groups.google.com/d/msgid/vagrant-up/CAHqq0eyNh-ndL1ktdsQ-E0g-yfWEtPCdW0VjQ7vKfzV0H3JnsQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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/CA%2BnFXPE4TAT0LBON5j0VEFbWK23iDWTr5v4Xap30HUgtKP%3Daog%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
