Hi Alvaro,
Thank you very much for your help.
I redo "vagrant up" for the precise32 and centos6.7-i386 under the same
Windows user directory. It still failed with centos6.7-i386. But the
errors is different.
Both are able to deploy VM in VirtualBox.
precise32 is able to SSH to the VM, and saw the shared folder "/vagrant"
from the VM console.
However, for Centos6.7-i386, it only deployed the VM, and showed
connection "timeout" info on Windows console. It was not able to SSH
to Centos6.7 VM. When logon to the Centos6.7 VM, there was no shared
folder "/vagrant"from the VM console.
In this case, the home directory is the same for both precise32 and
centos6.7-i386 at the same machine.
What is the difference between precise32 and centos6.7-i386 when "vagrant
up"? What may cause the communicate with VM failure for Centos6.7 but
success for precise32 ?
Here is the Windows console output for centos6.7-i386
---------------------------------------------------------------------------------------------
C:\Users\dev\vm_test>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'bento/centos-6.7-i386' 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
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.
C:\Users\dev\vm_test>vagrant ssh
ssh_exchange_identification: Connection closed by remote host
Thanks,
Irene
On Tuesday, April 26, 2016 at 5:18:57 PM UTC-4, Alvaro Miranda Aguilera
wrote:
>
> On Wed, Apr 27, 2016 at 2:06 AM, Irene <[email protected] <javascript:>>
> wrote:
>
>> bento/centos-6.7-i386"
>
>
>
> Hello,
>
> After the VM is deployed, you should be able to run Virtualbox gui and see
> the VM there.
>
> If you stop start the VM you should be able to see the console and that
> may provide more information.
>
> If your server is connected to a domain, please check the home directory
> between the command prompt and the GUI is the same.
>
> In some cases due profiles, and that the user did logon on/off AD the home
> directory change.
>
> Vagrant and Virtualbox create folders based on the home directory they see.
>
> Thanks
> alvaro.
>
>
--
This mailing list is governed under the HashiCorp Community Guidelines -
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of
those guidelines may result in your removal from this mailing list.
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/vagrant-up/ddcaff17-7615-40f4-808c-30619e265c20%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
