try the gui test, that will tell you what the error is. 32 bit OS can run without the bios change
64 bit OS require the bios change. On Wed, Aug 5, 2015 at 4:05 PM, <[email protected]> wrote: > > Adding config.ssh.insert_key = false into Vagrantfile has no effect. > There is no virtualization option in my BIOS. > But if it was the reason - i couldn't mount hashicorp/precise32 too, isn't > it? > > > среда, 5 августа 2015 г., 13:49:22 UTC+10 пользователь Alvaro Miranda > Aguilera написал: >> >> Hello, >> >> Try to add: >> >> config.ssh.insert_key = false >> >> to the Vagrantfile >> >> Other option is, If you go to the virtualbox gui, and turn off/on the >> VM should should see any error. >> >> most of the times is due Virtualzation option OFF on the bios >> If this is the cause, this change vendor to vendor, so you should >> check the manual and enable virtualization on the Bios >> >> Thanks >> Alvaro. >> >> On Wed, Aug 5, 2015 at 3:43 PM, <[email protected]> wrote: >> > When i'm trying use any box ubuntu/trusty* i got this: >> > >> > vagrant up >> > Bringing machine 'default' up with 'virtualbox' provider... >> > ==> default: Importing base box 'ubuntu/trusty32'... >> > ==> default: Matching MAC address for NAT networking... >> > ==> default: Checking if box 'ubuntu/trusty32' is up to date... >> > ==> default: Setting the name of the VM: >> > namivam_default_1438737430150_93449 >> > ==> default: Clearing any previously set forwarded ports... >> > ==> default: Clearing any previously set network interfaces... >> > ==> default: Preparing network interfaces based on configuration... >> > default: Adapter 1: nat >> > ==> default: Forwarding ports... >> > default: 80 => 8080 (adapter 1) >> > default: 22 => 2222 (adapter 1) >> > ==> default: Booting VM... >> > ==> default: Waiting for machine to boot. This may take a few minutes... >> > default: SSH address: 127.0.0.1:2222 >> > default: SSH username: vagrant >> > default: SSH auth method: private key >> > default: Warning: Connection timeout. Retrying... >> > default: Warning: Connection timeout. Retrying... >> > default: Warning: Connection timeout. Retrying... >> > default: Warning: Connection timeout. Retrying... >> > default: Warning: Connection timeout. Retrying... >> > default: Warning: Connection timeout. Retrying... >> > default: Warning: Connection timeout. Retrying... >> > default: Warning: Connection timeout. Retrying... >> > default: Warning: Connection timeout. Retrying... >> > default: Warning: Connection timeout. Retrying... >> > default: Warning: Connection timeout. Retrying... >> > default: Warning: Connection timeout. Retrying... >> > default: Warning: Connection timeout. Retrying... >> > default: Warning: Connection timeout. Retrying... >> > default: Warning: Connection timeout. Retrying... >> > default: Warning: Connection timeout. Retrying... >> > default: Warning: Connection timeout. Retrying... >> > default: Warning: Connection timeout. Retrying... >> > default: Warning: Connection timeout. Retrying... >> > >> > >> > It happens as x32 as x64 boxes. >> > But hashicorp/precise32 is working ok. >> > >> > Is there any way to fix it? >> > >> > >> > My Environment: >> > >> > Linux Mint 17.2 Rafaela (x64) >> > virtualbox-5.0_5.0.0-101573~Ubuntu~trusty_amd64 >> > vagrant_1.7.4_x86_64 >> > >> > If i can provide any info - let me know. >> > >> > >> > >> > -- >> > 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/d62e8374-ce6e-4895-8f8d-2ade75ecbe09%40googlegroups.com. >> > 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/71c4a240-b5a6-4011-95c6-1391e92c36a9%40googlegroups.com. > 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/CAHqq0ew-r_TDVJD1o%3Df1GOh2F7SjK0Jdn_TO4%2BGFtCOYXbmKBA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
