Hi, If you refer to something like 'vagrant plugin license xxx', then I did not run it... ... and I'll anticipate the next question : "why ?"... That's because I do not have a license (hopefully!)
When I first read the vmware provider plugin doc, I saw something about licensing fees but though that it was referring to the fact that vmware isn't free, not the plugin itself. As a vmware user I though I'd give this provider a try instead of the proposed VirtualBox... Now, I'm not so sure... I followed Shawn's advice to install the latest vagrant version from vagrantup.com. I assume that the new setup should work because vagrant no longer complains when it loads its plugins (including the vmware plugin). I must confess that vagrant got stuck because I do not have a license, and I had to remove the plugin from the list in ~/.vagrant.d to return to normal behaviour. I won't insist so much with vmware because: 1. I'm not a paypal user... don't really want to open an account for the plugin 2. the little glitches when setting up vagrant and the plugin got me cold feet 3. my vmware version is so old/deprecated/patched that I can predict more troubles ahead 4. I was just testing: I don't *need* vmware... (I just like it better) Thanks a lot for your help though 2014-10-25 20:11 GMT+02:00 Umair Chagani <[email protected]>: > I'm not seeing where you applied the license for the vmware plugin. > On Oct 25, 2014 9:52 AM, "Lionel VICTOR" <[email protected]> wrote: > >> Hi, >> >> I'm having a similar issue. I agree that the message makes the "problem" >> clear indeed... but not the solution. At least not to me :o( >> I'm afraid I need to ask for a few more details. >> >> I installed the plugin with 'vagrant plugin install >> vagrant-vmware-workstation' >> 'vagrant plugin list' indeed lists the plugin and shows no error. >> Then 'vagrant init hashicorp/precise32' already triggers the error... >> >> Here are the points that are not clear to me. I hope someone may shed >> some light or point me in the right direction: >> - What's the 'Vagrant installer' ? >> - Where is the plugin supposed to go ? For now it lies somewhere in >> ~/.vagrant.d/ can I just move it somewhere else ? >> - what's the use case for 'vagrant plugin install xxx' if it does not >> install things where they are supposed to go ? When should I use it ans >> when should I avoid using it ? >> - If there is no easy solution, then what am I missing to get past this >> problem ? Would you advise me to learn more about Ruby or more about >> Vagrant ? >> >> Thanks for your help. >> >> Le jeudi 16 janvier 2014 19:22:28 UTC+1, Mitchell Hashimoto a écrit : >>> >>> Hi, >>> >>> I'll just respond here: Both of you have installations of Vagrant >>> outside of binary Vagrant installer. For example, Jonathan, your install is >>> in "/opt/boxen". >>> >>> The providers only work with the installers provided on the Vagrant >>> site: http://www.vagrantup.com >>> >>> This error message I think makes it clear: "Encoded files can't be read >>> outside of the Vagrant installer." >>> >>> Best, >>> Mitchell >>> >> -- >> 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 a topic in the > Google Groups "Vagrant" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/vagrant-up/7EkpfFIaFRw/unsubscribe. > To unsubscribe from this group and all its topics, 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.
