vagrant con 32bits

[s-nt-s]

Aunque sigue exisitiendo la opción de instalación manual, lo más comodo y que desincentiva menos a la hora de ponerse a colaborar es usar vagrant, pero lo teneis montaado en un ubuntu de 64bits por lo tanto los que tenemos ordenadores viejos que solo pueden emular 32bits no podemos arrancarlo.

¿Podriais montar un entorno vagrant con ubuntu - u otro linux - 32bits?

(*) Virtualbox dice con la actual máquina: La aceleración por hardware VT-x/AMD-V no se encuentra en su sistema. Por lo tanto el sistema invitado de 64 bits no podrá detectar una CPU de 64 bits y no podrá iniciarse.

[andreslucena]

Hola @s-nt-s !
Podrías probarlo cambiando esta linea en el Vagrantfile?

[s-nt-s]

Ahora la maquina si arranca, pero tarda tanto que al vargrant no le da tiempo a conectarse:

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'ubuntu/trusty32' is up to date...
==> 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: 3000 (guest) => 3000 (host) (adapter 1)
    default: 1080 (guest) => 8081 (host) (adapter 1)
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> 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
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.

Así que he añaddo la linea config.vm.boot_timeout = 600 al Vagrantfile justo debajo de la que tu me indicas pero el resultado ha sido el mismo.

Así que al final he añadido:

  config.ssh.username = "vagrant"
  config.ssh.password = "vagrant"

a ver si mejoraba la cosa, per nada, sigue petando.

Sin embargo si le digo a VirtualBox que me muestre la maquina virtual se ve que ha arrancado sin problemas, incluso me puedo logear en ella.