vccw.md

PD@PD-VAIO MINGW64 /c/vccw-2.19.0
$ vagrant -v
Vagrant 1.8.1
PD@PD-VAIO MINGW64 /c
$ vagrant box add miya0001/vccw
==> box: Loading metadata for box 'miya0001/vccw'
    box: URL: https://atlas.hashicorp.com/miya0001/vccw
==> box: Adding box 'miya0001/vccw' (v2.19.0) for provider: virtualbox
    box: Downloading: https://atlas.hashicorp.com/miya0001/boxes/vccw/versions/2.19.0/providers/virtualbox.box
    box:
==> box: Successfully added box 'miya0001/vccw' (v2.19.0) for 'virtualbox'!
PD@PD-VAIO MINGW64 /c
$ cd vccw-2.19.0/
PD@PD-VAIO MINGW64 /c/vccw-2.19.0
$ vagrant up
Bringing machine 'vccw.dev' up with 'virtualbox' provider...
==> vccw.dev: Removing hosts
==> vccw.dev: No machine id, nothing removed from C:/WINDOWS/system32/drivers/etc/hosts
==> vccw.dev: Importing base box 'miya0001/vccw'...
==> vccw.dev: Matching MAC address for NAT networking...
==> vccw.dev: Checking if box 'miya0001/vccw' is up to date...
==> vccw.dev: Setting the name of the VM: vccw.dev
==> vccw.dev: Auto-generating node name for Chef...
==> vccw.dev: Fixed port collision for 22 => 2222. Now on port 2200.
==> vccw.dev: Clearing any previously set network interfaces...
==> vccw.dev: Preparing network interfaces based on configuration...
    vccw.dev: Adapter 1: nat
    vccw.dev: Adapter 2: hostonly
==> vccw.dev: Forwarding ports...
    vccw.dev: 22 (guest) => 2200 (host) (adapter 1)
==> vccw.dev: Checking for host entries
==> vccw.dev: adding to (C:/WINDOWS/system32/drivers/etc/hosts) : 192.168.33.10  vccw.dev  # VAGRANT: 468b84e9bbd3cad1d4118ffa4cd90d58 (vccw.dev) / de9ef5b2-d0a3-4996-bbf2-863926a2594b
==> vccw.dev: Running 'pre-boot' VM customizations...
==> vccw.dev: Booting VM...
==> vccw.dev: Waiting for machine to boot. This may take a few minutes...
    vccw.dev: SSH address: 127.0.0.1:2200
    vccw.dev: SSH username: vagrant
    vccw.dev: 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.