newbie vargant issues on Ubuntu 14.04

[Larry Martell]

I am trying to get vagrant running for the first time on a brand new Ubuntu 14.04 system. When I run vagrant up I get:

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'chef/ubuntu-14.04'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'chef/ubuntu-14.04' is up to date...
==> default: Setting the name of the VM: default_1414964120299_22674
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
    default: Adapter 2: hostonly
==> default: Forwarding ports...
    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...
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.


I can ssh locally to 127.0.0.1, but not to port 2222. I tried opening port 2222, but that didn't help. Googling this, one thing I found was that the port is in use. I don't see any evidance of that, but I tried forwarding to another port, but still no joy. This question seems to be asked a lot, but none of the sites I looked at had a answer that worked for me. Any advise or pointers are welcome.

[Alvaro Miranda Aguilera]

On Mon, Nov 3, 2014 at 11:37 AM, Larry Martell <larry....@gmail.com> 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 

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

Around these lines you should able to get more information to find the cause of the problem

Alvaro,.

[Larry Martell]

On Sun, Nov 2, 2014 at 7:03 PM, Alvaro Miranda Aguilera
<kik...@gmail.com> wrote:
>
> On Mon, Nov 3, 2014 at 11:37 AM, Larry Martell <larry....@gmail.com>
> 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
> vagrant-up+...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Alvaro Miranda Aguilera]

Check if your hardware have 64 bits capabilities, check the manual how to enable on Bios, and enable it.

that is a requirement if you want to run 64 bits OS guest with Virtualbox.

Alvaro.

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 vagrant-up+...@googlegroups.com.