Hi Alvaro,
My host machine have 8GB memory. Please find below my vagrantfile ( for
ubuntu) -
*$ cat Vagrantfile*
*# -*- 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 = "ubuntu/trusty64"*
* # 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 = "4096"*
* vb.cpus = 8*
* # 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*
On Tuesday, 4 September 2018 11:58:01 UTC+5:30, Alvaro Miranda Aguilera
wrote:
>
> Hello.
>
> If you could share the Vagrantfile to confirm syntax is correct will help
>
> How much memory your host computer have?
>
> On Tue, Sep 4, 2018 at 1:53 AM Bot_Learn <[email protected] <javascript:>>
> wrote:
>
>> I am bit new to vagrant. Created three virtual machines using vagrant. I
>> need 4GB memory to be assigned in a virtual machine( presently having less
>> than 1GB memory on that).
>> I have edited the vagrantfile and tried to restart the vm ( using *vagrant
>> up <vm_name> *) but it's still showing old memory there.
>>
>> Can anyone please advise how i can increase memory size here?
>>
>> Thanks
>>
>> --
>> 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] <javascript:>.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/vagrant-up/9ccb0eaa-3035-4206-9440-8610b850d3a2%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/vagrant-up/9ccb0eaa-3035-4206-9440-8610b850d3a2%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/f6de2df9-1b51-4dc9-95e8-4c9f3bc7614a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
