Retire vagrant-kvm?

[adrahon]

I'm thinking of retiring this project for the following reasons:

1. I have less and less time to work on the project and have achieved my personal objectives with it.
2. There is another plugin, https://github.com/pradels/vagrant-libvirt/, that is a lot more widely used and vagrant-kvm doesn't have any compelling features compared to it any more.
3. vagrant-libvirt is being packaged with Vagrant for Fedora, which is my main platform.
4. Vagrant isn't essential to my workflow anymore (yes, that's because of Docker).

I think all users should switch to vagrant-libvirt, except if there's anything it's missing, I'd be happy to contribute any feature from vagrant-kvm to vagrant-libvirt if that's the case.

Of course if anyone is interested in maintaining their own fork, I'll support it being the official version.

Happy to hear any comments.

[pronix]

Same issue with docker :)

[facastagnini]

At lease makes sense to put a big disclaimer with all that information in the README, so people can figure out the state of the proyect faster.

[nspaeth]

I think one major missing feature from libvirt is the ability to specify a 9p mount as mapped rather than passthrough.
See vagrant-libvirt/vagrant-libvirt#274
Otherwise, you are probably in the best position to know if libvirt is the better alternative.

[adrahon]

I updated the README to direct people to vagrant-libvirt. Not sure how to retire the rubygem though.

[arbox]

Probably you can create an after install message in the gemspec and put a deprecation warning into the gem descriptin as well.
An extreme way to do things will be to yank all the versions.