yes , it happens with both vm downloaded from vagrantbox.es or build by myself. I rename the VM in the vagrantfile with the config.vm.name command. so it create a folder named as wished but the vmdk doesnt follow and stay in the original folder used by the basebox.
I join a vbox file and a vagrant file , in the .VBOX file line 12 is the location(../Template_test/*.vmdk) of the harddisk even if i have rename my VM in the VagranFile (vb.name=002) thank you . Le lundi 17 mars 2014 14:53:57 UTC+13, Alvaro Miranda Aguilera a écrit : > > uhmmmm, > > from where are you getting those boxes or how are you creating them? > > I don't face that problem. > > I have seen that when you create a new disk as part of the vagrant file > > for that situation (create a new disk) > > What you may want to do, is set a specific name to the vm, so the path to > the folder in the virtualbox default path will be known, then you can > create the file in that known path > > config.vm.hostname is the hostname inside the vm > config.vm.name is the name of the vm in the VirtualBox space > > > can you share a Vagrantfile and one of those base box ??? > > > > > On Mon, Mar 17, 2014 at 2:39 PM, Nic' <[email protected] <javascript:>>wrote: > >> Hi , >> >> after few deployments with Vagrant either with a base box or with a new >> packaged one , I face to a problem with the hard disk location within VBox. >> Actually , each time I Vagrant up a new machine , even if i renamed it , >> the new hard disk (vmdk) wil take place in the same original folder define >> in the base box. >> e.g. ~\myvms\basebox\xxxx.vmdk >> and all my next VMs based on a specific basebox will put the .vmdk in the >> above folder . >> >> Wich is logical because it's defined in the .OVF file but it's not really >> handy and I don't really like to mix all hard drive together. >> >> Work around : I manage the hard disk afterward with VBoxmanage and move >> it in a specific VM folder >> >> But where is the automate way to do that ? >> >> If anyone has an idea ? >> >> thank you. >> Nic" >> >> -- >> 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:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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]. For more options, visit https://groups.google.com/d/optout.
# -*- mode: ruby -*-
# vi: set ft=ruby :
# Vagrantfile API/syntax version. Don't touch unless you know what you're doing!
VAGRANTFILE_API_VERSION = "2"
Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
# All Vagrant configuration is done here. The most common configuration
# options are documented and commented below. For a complete reference,
# please see the online documentation at vagrantup.com.
config.vm.box = "Fridaytest"
# Every Vagrant virtual environment requires a box to build off of.
config.vm.define "001" do |first|
first.vm.provider :virtualbox do |vb|
# # Don't boot with headless mode
#vb.gui = true
vb.name = "001"
end
config.vm.network :forwarded_port, guest: 80, host: 8080
config.vm.provision :shell, :path => "bootstrap/ubuntu.sh"
end
config.vm.define "002" do |second|
second.vm.box = "Fridaytest"
second.vm.provider :virtualbox do |vb|
# # Don't boot with headless mode
#vb.gui = true
vb.name = "002"
end
config.vm.network :forwarded_port, guest: 80, host: 8081
config.vm.provision :shell, :path => "bootstrap/ubuntu.sh"
end
# The url from where the 'config.vm.box' box will be fetched if it
# doesn't already exist on the user's system.
# config.vm.box_url = "http://domain.com/path/to/above.box";
# 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.
# 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
# If true, then any SSH connections made will enable agent forwarding.
# Default value: false
# config.ssh.forward_agent = true
# 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|
# # Don't boot with headless mode
# vb.gui = true
#end
#
# # Use VBoxManage to customize the VM. For example to change memory:
# vb.customize ["modifyvm", :id, "--memory", "1024"]
#
# View the documentation for the provider you're using for more
# information on available options.
# Enable provisioning with Puppet stand alone. Puppet manifests
# are contained in a directory path relative to this Vagrantfile.
# You will need to create the manifests directory and a manifest in
# the file base.pp in the manifests_path directory.
#
# An example Puppet manifest to provision the message of the day:
#
# # group { "puppet":
# # ensure => "present",
# # }
# #
# # File { owner => 0, group => 0, mode => 0644 }
# #
# # file { '/etc/motd':
# # content => "Welcome to your Vagrant-built virtual machine!
# # Managed by Puppet.\n"
# # }
#
# config.vm.provision :puppet do |puppet|
# puppet.manifests_path = "manifests"
# puppet.manifest_file = "site.pp"
# end
# Enable provisioning with chef solo, specifying a cookbooks path, roles
# path, and data_bags path (all relative to this Vagrantfile), and adding
# some recipes and/or roles.
#
# config.vm.provision :chef_solo do |chef|
# chef.cookbooks_path = "../my-recipes/cookbooks"
# chef.roles_path = "../my-recipes/roles"
# chef.data_bags_path = "../my-recipes/data_bags"
# chef.add_recipe "mysql"
# chef.add_role "web"
#
# # You may also specify custom JSON attributes:
# chef.json = { :mysql_password => "foo" }
# end
# Enable provisioning with chef server, specifying the chef server URL,
# and the path to the validation key (relative to this Vagrantfile).
#
# The Opscode Platform uses HTTPS. Substitute your organization for
# ORGNAME in the URL and validation key.
#
# If you have your own Chef Server, use the appropriate URL, which may be
# HTTP instead of HTTPS depending on your configuration. Also change the
# validation key to validation.pem.
#
# config.vm.provision :chef_client do |chef|
# chef.chef_server_url = "https://api.opscode.com/organizations/ORGNAME";
# chef.validation_key_path = "ORGNAME-validator.pem"
# end
#
# If you're using the Opscode platform, your validator client is
# ORGNAME-validator, replacing ORGNAME with your organization name.
#
# If you have your own Chef Server, the default validation client name is
# chef-validator, unless you changed the configuration.
#
# chef.validation_client_name = "ORGNAME-validator"
end
002.vbox
Description: Binary data
