On Sun, Nov 2, 2014 at 7:03 PM, Alvaro Miranda Aguilera <[email protected]> wrote: > > On Mon, Nov 3, 2014 at 11:37 AM, Larry Martell <[email protected]> > wrote: >> >> default: Adapter 1: nat >> default: Adapter 2: hostonly > > > Hello, > > hard to say what can be.. so let's troubleshoot. > > I saw you had 2 nics, so better stay simple. > > 1. Can be VT not enabled on bios. > > 1.0 on the VM got created, so go to the virtualbox gui, and try to turn it > one.. what does happen? > > 1.1 Enable gui > Edit the Vagrantfile, and enable the gui.. there must be a Virtualbox > block.. > > config.vm.provider "virtualbox" do |v| > v.gui = true > end > > Add something like that. > > vagrant up and check the console
This is what I got in the console: VT-x/AMD-V hardware acceleration is not available on your system. Your 64-bit guest will fail to detect a 64-bit CPU and will not be able to boot. > > 1.2 Test with 32bits > > create a new folder and test a 32bit machine > outside the path where you are not > > mkdir precise32 > cd precise32 > vagrant init hashicorp/precise32 -m > vagrant up Seems to work in 32 bit mode. Thanks for all the help. > > > Around these lines you should able to get more information to find the cause > of the problem > > Alvaro,. > > -- > 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/HMfk2OMn_tE/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. -- 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]. For more options, visit https://groups.google.com/d/optout.
