I don't mean to this sound snarky, and I really appreciate vagrant. I've had patches merged over the years, so I'm a strong supporter.
BUT, I'd be genuinely interested on the reasoning behind charging for a vmware provider but not the hyperv one? Is it simply that nobody else bothered to develop a vmware provider?
I've considered developing a vmware provider, but don't like the idea of cutting off a vagrant revenue source.
Hi! I'd be happy to say why. VMware itself costs money, unlike VirtualBox which is free. We felt it was fair to charge for a provider where the underlying hypervisor cost money. Additionally, it was our first and only way to support ourselves in developing this product.
If we had a ton of money we'd make the VMware provider free, too. :) But as it is, it is our primary source of income at the moment. Based on interest in on-premise Vagrant Cloud solutions, that may quickly change (hopefully!).
Hyper-V, on the hand, was developed mostly by MS OpenTech. It would be unfair (and likely illegal) to charge for their work they did and contributed as MIT licensed code to Vagrant core.
BUT, I'd be genuinely interested on the reasoning behind charging for a vmware provider but not the hyperv one? Is it simply that nobody else bothered to develop a vmware provider?
I've considered developing a vmware provider, but don't like the idea of cutting off a vagrant revenue source.