can you test a different vagrant box? mkdir precise32 cd precise32 vagrant ini hashicorp/precise32 vagrant up
if that works, vagrant is installed OK, and working and you will need to check with the people at arkos. On Tue, May 27, 2014 at 2:39 PM, Cem Girit <[email protected]> wrote: > Hello Terrance, > > > I downloaded from https://arkos.io/downloads/ and followed the > instructions given at https://arkos.io/dev/genesis/vagrant. > > On Monday, May 26, 2014 9:36:22 PM UTC-4, Terrance Shepherd wrote: >> >> Where did you get the box file from? >> >> >> On Mon, May 26, 2014 at 9:34 PM, Cem Girit <[email protected]> wrote: >> >>> >>> Hello, >>> >>> I have been trying to set up a Linix distro on a VirtualBox. I >>> believe the disto (arkOS) was installed properly since VirtualBox consol >>> reports that it is running. But when I try to connect by "vagrant ssh" I >>> get timeout error. Box is local on the same computer. So the network >>> connection is set to NAT. SSH authorization is through vagrant generated(?) >>> key. Why can't I connect the box? Do I have to set up something else? >>> >>> >>> C:/ArchOS/Vagrantfile:5: warning: previous definition of >>> VAGRANTFILE_API_VERSION >>> >>> was here >>> >>> VM must be running to open SSH connection. Run `vagrant up` >>> >>> to start the virtual machine. >>> >>> >>> >>> C:\ArchOS>vagrant up >>> >>> C:/Users/girit/.vagrant.d/boxes/genesis-dev/0/virtualbox/include/_ >>> Vagrantfile:1: >>> >>> warning: already initialized constant VAGRANTFILE_API_VERSION >>> >>> C:/ArchOS/Vagrantfile:5: warning: previous definition of >>> VAGRANTFILE_API_VERSION >>> >>> was here >>> >>> Bringing machine 'default' up with 'virtualbox' provider... >>> >>> ==> 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: 8000 => 8000 (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... >>> >>> 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. >>> >>> -- >>> 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. >>> >> >> -- > 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. > -- 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.
