hello Can you confirm the following:
Host OS and bit (like 32/64) Guest VM OS and bit (like 32/64) if you are trying this Host + Virtualbox => VM + Virtualbox => new VM I am afraid that won't work on the last part if 64 bits since 64 bits need hardware assisted virtualization that is not available on nested virtualization you may have some luck with virtualbox 32 bit + guest 32 bit but I can tell you will work for sure, you need to test. Having said that, why you need virtualbox inside a VM? if you can explain, I will be more than happy to give you ideas how to attack that problem Thanks alvaro On Fri, Jun 26, 2015 at 4:34 PM, zhz shi <[email protected]> wrote: > Hi All, > > I have a virtual machine running CentOS 6.6 and I installed vagrant 1.7.2 > and VirtualBox 4.3 on it. I'm trying to use vagrant to run guest machine > with ubuntu or some other OS, but during the 'vagrant up' phase, vagrant > always failed to ssh to the guest machine. > > Logs I got is: > > $ vagrant up > [2/47] > Bringing machine 'default' up with 'virtualbox' provider... > ==> default: Importing base box 'ubuntu/trusty64'... > ==> default: Matching MAC address for NAT networking... > ==> default: Checking if box 'ubuntu/trusty64' is up to date... > ==> default: Setting the name of the VM: > vagrant-base_default_1435292165676_93887 > ==> 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 => 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. > > ------------------- > > Seems the guest machine is running: > $ vagrant status > Current machine states: > > default running (virtualbox) > > ----------- > > Does anybody here have any idea what's the problem is? > > Thanks a lot for any help. > > BR, zhz > > -- > 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/3d57f5fd-5627-4635-a6f5-a33952dac591%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- 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/CAHqq0eyzCsshX6RQfBwTBUnjv8bCQDP6dQkDWQV-s0hhoAMoKg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
