lets work on p64

to confirm

win10, virtualbox installed you can create VM and boot them and those work
fine ?

if yes, then do


vagrant up --debug

and share all the verbose log in a gist . (gist.github.com)

Thanks
Alvaro.

On Tue, Feb 20, 2018 at 11:14 AM, suresh kumar <[email protected]> wrote:

> Hi Alvaro,
>
> Thanks for your reply.
>
> I tried the steps below you mentioned.
>
> Copyright (C) 2009 Microsoft Corporation. All rights reserved.
>
> PS C:\Users\suresh.adusumilli> mkdir p64
>
>
>     Directory: C:\Users\suresh.adusumilli
>
>
> Mode                LastWriteTime     Length Name
> ----                -------------     ------ ----
> d----         2/20/2018   3:35 PM            p64
>
>
> PS C:\Users\suresh.adusumilli> cd p64
> PS C:\Users\suresh.adusumilli\p64> vagrant init -m hashicorp/precise64
> A `Vagrantfile` has been placed in this directory. You are now
> ready to `vagrant up` your first virtual environment! Please read
> the comments in the Vagrantfile as well as documentation on
> `vagrantup.com` for more information on using Vagrant.
> PS C:\Users\suresh.adusumilli\p64> vagrant up
>
>
> After that there is no response from vagrant up command. waitted for more
> than 30 mins.
>
> i am using Vbox version : 5.2.0 and vagrant  version 2.0.2
> *.vagrant file :*
> Vagrant.configure("2") do |config|
>   config.vm.box = "hashicorp/precise64"
> end
>
> i tried with bento/centos-7.1 also please find the .vagrant file below.
> *.Vagrant file:*
>
> # -*- mode: ruby -*-
> # vi: set ft=ruby :
>
> # All Vagrant configuration is done below. The "2" in Vagrant.configure
> # configures the configuration version (we support older styles for
> # backwards compatibility). Please don't change it unless you know what
> # you're doing.
> Vagrant.configure("2") do |config|
>   # The most common configuration options are documented and commented
> below.
>   # For a complete reference, please see the online documentation at
>   # https://docs.vagrantup.com.
>
>   # Every Vagrant development environment requires a box. You can search
> for
>   # boxes at https://vagrantcloud.com/search.
>   config.vm.box = "bento/centos-6.7"
>
>   # Disable automatic box update checking. If you disable this, then
>   # boxes will only be checked for updates when the user runs
>   # `vagrant box outdated`. This is not recommended.
>   # config.vm.box_check_update = false
>
>   # Create a forwarded port mapping which allows access to a specific port
>   # within the machine from a port on the host machine. In the example
> below,
>   # accessing "localhost:8080" will access port 80 on the guest machine.
>   # NOTE: This will enable public access to the opened port
>   # config.vm.network "forwarded_port", guest: 80, host: 8080
>
>   # Create a forwarded port mapping which allows access to a specific port
>   # within the machine from a port on the host machine and only allow
> access
>   # via 127.0.0.1 to disable public access
>   # config.vm.network "forwarded_port", guest: 80, host: 8080, host_ip:
> "127.0.0.1"
>
>   # Create a private network, which allows host-only access to the machine
>   # using a specific IP.
>   # config.vm.network "private_network", ip: "192.168.33.10"
>
>   # Create a public network, which generally matched to bridged network.
>   # Bridged networks make the machine appear as another physical device on
>   # your network.
>   # config.vm.network "public_network"
>
>   # Share an additional folder to the guest VM. The first argument is
>   # the path on the host to the actual folder. The second argument is
>   # the path on the guest to mount the folder. And the optional third
>   # argument is a set of non-required options.
>   # config.vm.synced_folder "../data", "/vagrant_data"
>
>   # Provider-specific configuration so you can fine-tune various
>   # backing providers for Vagrant. These expose provider-specific options.
>   # Example for VirtualBox:
>   #
>   # config.vm.provider "virtualbox" do |vb|
>   #   # Display the VirtualBox GUI when booting the machine
>   #   vb.gui = true
>   #
>   #   # Customize the amount of memory on the VM:
>   #   vb.memory = "1024"
>   # end
>   #
>   # View the documentation for the provider you are using for more
>   # information on available options.
>
>   # Enable provisioning with a shell script. Additional provisioners such
> as
>   # Puppet, Chef, Ansible, Salt, and Docker are also available. Please see
> the
>   # documentation for more information about their specific syntax and use.
>   # config.vm.provision "shell", inline: <<-SHELL
>   #   apt-get update
>   #   apt-get install -y apache2
>   # SHELL
> end
>
>
>
> *There is no output or error message after vagrant up. *
>
> *Regards,*
> *Suresh*
>
>
>
>
>
>
>
>
> On Tuesday, February 20, 2018 at 2:12:58 PM UTC+5:30, Alvaro Miranda
> Aguilera wrote:
>>
>> hello
>>
>> you don't provide enough info to help, you describe how you got there but
>> you don't show any relevant file/output
>>
>> so, lets stick to latest vagrant and latest virtualbox
>>
>> create a vm that works, ie use hashicorp/precise64
>>
>> mkdir p64
>> cd p64
>> vagrant init -m hashicorp/precise64
>>
>> vagrant up
>>
>>
>> i expect this to work
>>
>>
>> now you add the network
>> then do vagrant reload
>>
>> if here this fails
>>
>> share
>>
>> vagrant version
>> the output of the vagrant up command
>> the content of Vagrantfile
>>
>> Thanks
>> Alvaro
>>
>> On Tue, Feb 20, 2018 at 9:25 AM, suresh kumar <[email protected]> wrote:
>>
>>> Hi,
>>>
>>> i tired below things
>>>
>>> Vagrant init bento/centos-6.7
>>> removed comment fro IP host  and changed ip address( config.vm.network
>>> "private_network", IP: 192.168.33.50")
>>> next i gave
>>> vagrant up
>>> This vagrant up command is not giving any information hanged.
>>> Vbox: 5.2.0 and vagrant 2.0.2 and i tried with vagrant 1.9.4 also
>>> i tried in powershell 2009  and cmnder also.
>>> vagrant up not working.  no error information or no warnings nothing.
>>>
>>> Regards,
>>> Suresh
>>>
>>> --
>>> 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/ms
>>> gid/vagrant-up/124aa1dd-7bbc-48d6-a129-f5c8ef5c37ce%40googlegroups.com
>>> <https://groups.google.com/d/msgid/vagrant-up/124aa1dd-7bbc-48d6-a129-f5c8ef5c37ce%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> 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/ff026b74-6644-403a-9070-e702bbbad14c%40googlegroups.com
> <https://groups.google.com/d/msgid/vagrant-up/ff026b74-6644-403a-9070-e702bbbad14c%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
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/CAHqq0eye6Hnqk1ZSD0OpF9O2sCYU%3D3d%3DXKAq9FCWynKoa5Oh8Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to