Hello,
I was able to get the VMs up on my mac mini.
How much ram your host computer does have?
Can you try to upgrade to Vagrant 1.8.5 and use the following Vagrantfile:
Vagrant.configure("2") do |config|
config.ssh.insert_key=false
config.vm.provider "virtualbox" do |vb|
vb.gui = true
vb.memory = "1024"
end
config.vm.define "lb1" do |lb1|
lb1.vm.box="centos/7"
end
config.vm.define "web1" do |web1|
web1.vm.box="centos/7"
end
config.vm.define "web2" do |web2|
web2.vm.box="centos/7"
end
end
If still fails, can you share more info please:
Version of VirtualBox
output of
vagrant version
vagrant plugin list
On Thu, Jul 21, 2016 at 11:27 PM, <[email protected]> wrote:
> Hi Alvaro,
>
> Any update on how to get it fixed? I tried all options available on the
> internet/google.
>
> Regards,
> Jim
>
>
> On Wednesday, July 20, 2016 at 8:36:37 PM UTC+10, [email protected]
> wrote:
>>
>> Hi Alavro,
>>
>> I have to double click on VM from VirtualBox GUI and looking at
>> /var/log/messages doesn't show any spectacular errors which may refrain the
>> other two VM from starting.
>>
>> I did vagrant destroy and then did vagrant up and it started well.
>> Thereafter consequent vagrant up commands does not allow the machines to
>> boot properly. I even increased RAM from 1GB to 1.5GB for first machine
>> (lb1) but still the same issue(the other two do not start).
>>
>> Might be the bug in product ? is it ok to start VM's from Virtual box ?
>> instead of vagrant up ?
>>
>> Regards,
>> Jim
>>
>> On Wednesday, July 20, 2016 at 7:17:22 PM UTC+10, Alvaro Miranda Aguilera
>> wrote:
>>>
>>> Hello, it looks ok your vagrant file and the box should be working.
>>>
>>> So, can you confirm you can use the Virtualbox gui, stop and start the
>>> VM lb1 from there, and check whats the message from the Virtualbox GUI ?
>>>
>>> Alvaro
>>>
>>> On Wed, Jul 20, 2016 at 7:10 PM, <[email protected]> wrote:
>>>
>>>> G'day All,
>>>>
>>>> Please find below the contents of my Vagrantfile:
>>>>
>>>> ENV['VBOX_INSTALL_PATH'] = ENV['VBOX_MSI_INSTALL_PATH']
>>>> Vagrant.configure("2") do |config|
>>>> config.vm.define "lb1" do |lb1|
>>>> lb1.vm.box="centos/7"
>>>> end
>>>> config.vm.define "web1" do |web1|
>>>> web1.vm.box="centos/7"
>>>> end
>>>> config.vm.define "web2" do |web2|
>>>> web2.vm.box="centos/7"
>>>> end
>>>> config.vm.provider "virtualbox" do |vb|
>>>> vb.gui = true
>>>> vb.memory = "1024"
>>>> end
>>>> end
>>>>
>>>> When I do vagrant up: Only one of the three machines start and the
>>>> error message is below:
>>>> Bringing machine 'lb1' up with 'virtualbox' provider...
>>>> Bringing machine 'web1' up with 'virtualbox' provider...
>>>> Bringing machine 'web2' up with 'virtualbox' provider...
>>>> ==> lb1: Checking if box 'centos/7' is up to date...
>>>> ==> lb1: Clearing any previously set forwarded ports...
>>>> ==> lb1: Clearing any previously set network interfaces...
>>>> ==> lb1: Preparing network interfaces based on configuration...
>>>> lb1: Adapter 1: nat
>>>> ==> lb1: Forwarding ports...
>>>> lb1: 22 (guest) => 2222 (host) (adapter 1)
>>>> ==> lb1: Running 'pre-boot' VM customizations...
>>>> ==> lb1: Booting VM...
>>>> ==> lb1: Waiting for machine to boot. This may take a few minutes...
>>>> lb1: SSH address: 127.0.0.1:2222
>>>> lb1: SSH username: vagrant
>>>> lb1: 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.
>>>>
>>>> I google a bit and people say have gui=true/delete , delete the private
>>>> key but it seems ot to be working.
>>>>
>>>> When lb1 starts I do enter username and password as they say it could
>>>> be waiting for that but not working but neither seems to be make it working
>>>> ...
>>>>
>>>> Would appreciate help from members
>>>>
>>>> Regards,
>>>> Jim
>>>>
>>>> --
>>>> 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/bbef782f-86a8-43a8-a70d-4d74d25204ea%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/vagrant-up/bbef782f-86a8-43a8-a70d-4d74d25204ea%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>> 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/44e6224e-d563-4ec8-9f54-3d552f83cb9e%40googlegroups.com
> <https://groups.google.com/d/msgid/vagrant-up/44e6224e-d563-4ec8-9f54-3d552f83cb9e%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> 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/CAHqq0ey12TEu-jtX9L-%3Dmu8HQkYZZDgctGH9kb4br4K3EPobKA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
