Hi Alvaro, Hope you are doing good.
So I tried trusty32 and bento32 but they both either go into an *invalid state *after executing :- * default: SSH username: vagrant* * default: SSH auth method: private key* goes into an invalid state OR *I get the index.lock(Error::EACCES) like below :* * default: SSH username: vagrant* * default: SSH auth method: private key* *C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/machine_i ndex.rb:321:in `initialize': Permission denied @ rb_sysopen - C:/Users/Acer /.vagrant.d/data/machine-index/index.lock (Errno::EACCES)* * from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagr ant/machine_index.rb:321:in `open'* * from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagr ant/machine_index.rb:321:in `with_index_lock'* * from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagr ant/machine_index.rb:192:in `block in set'* . . . Totally stuck here !😨 On Mon, Mar 13, 2017 at 4:24 PM, Ap Seh <[email protected]> wrote: > Hi Alvaro, > > Thanks again for your reply and interest in this issue. > > I would have tried the 64-bit versions but my Host is a Windows 32 bit > machine and I was advised that it is not possible to run a 64-bit host on a > 32 bit machine. So i never tried installing the 64-bit VM ever. If you > think that this is incorrect and I can install a 64-bit VM on my windows > 32bit machine, I'll try it out. > > Await your return, > > Thanks loads, > Ajoo. > > On Mon, Mar 13, 2017 at 1:43 PM, Alvaro Miranda Aguilera < > [email protected]> wrote: > >> Hello >> >> If only precise32 bit worked, check you can run 64 bits at all. >> >> Since many of the VMs are 64 bits. >> >> Try to start a VM 64 bits manually, and see if you get errors. Most of >> the time the VT extension required to run 64 bits are disabled, other times >> some CPUs like tablets can't enable this features. >> >> Check the manual of your computer on how to enable this VT extensions on >> the Bios. >> >> 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 a topic in the >> Google Groups "Vagrant" group. >> To unsubscribe from this topic, visit https://groups.google.com/d/to >> pic/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/ms >> gid/vagrant-up/CAHqq0ez7uZmgNpcqP%3DBbTspLSTtnzHxxhPZ9jbLSC- >> wY59AsYQ%40mail.gmail.com >> <https://groups.google.com/d/msgid/vagrant-up/CAHqq0ez7uZmgNpcqP%3DBbTspLSTtnzHxxhPZ9jbLSC-wY59AsYQ%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%2BnFXPHRV%3DSSRSqs37N9aZ_ND7whZXeZxDFcRpzBrqfck2Vp9Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
