@sb68 wrote:
Hi, due to lack of a PC that is powerful enough for VIRL I was going to use the VIRL launcher app for packet.net on an old laptop running Linux Mint 17.3 (386). I followed the instructions provided on the website and in the tutorial. Unfortunately I got stuck when I tried to launch the guest vm (virl boxcutter) by "vagrant up". Vagrant attempts to launch it, but is unable to communicate with the box.
sb68@laptop ~/virl_boxcutter $ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'boxcutter/ubuntu1404' 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: 22 (guest) => 2222 (host) (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... after some time (2 minutes or so) ...
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.boottimeout" 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.The VM seems to run somehow. If I attempt to start vagrant again, the following message appears:
sb68@laptop ~/virl_boxcutter $ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'boxcutter/ubuntu1404' is up to date...
==> default: VirtualBox VM is already running.Any ideas or suggestions? There are no error messages or something else that gives an indication of what is going wrong. Should the "config.vm.boot__timeout" value be changed? If yes, in which file and what is a reasonable value?
Thanks a lot in advance.
Posts: 1
Participants: 1