Hello, I don't use vmware, so I can't comment on the VMX part.
let me check here what i think what you may try if you use packer, and create a box, OR, you create a new base box with the extra options you want on top of boot2docker and then export Check this: https://github.com/mitchellh/boot2docker-vagrant-box Alvaro. On Mon, Jul 14, 2014 at 2:25 PM, Alex Sherwin <[email protected]> wrote: > In this scenario: > > Built custom boot2docker box for vmware provider, the Vagrantfile in the > box sets vmware_fusion and vmware_workstation provider-specific settings to > specify the included boot2docker.iso to be auto mounted in the CD-ROM and > set it as the default in the boot order. > > The end-user creates a project-level Vagrantfile and needs to specify > vmware provider-specific settings to specify the VMX memsize and numvcpus. > > At this point the project-specific Vagrantfile overrides the Box file, and > the CD ROM is not automounted and booted from anymore. The > project-specific Vagrant file needs re-specify the CD-ROM VMX settings in > addition to the desired memory and cpu settings. > > Is there a way to instead inherit/extend the provider-specific settings so > that re-specifying the box's provider-specific VMX settings is unnecessary? > > -- > 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. > -- 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.
