Vagrant/libvirt #13150
Vagrant/libvirt #13150
Conversation
As seems impossible (or at least not easy) to have a single Vagrantfile with suitable configuration for different backends, this commit add two backend-specific Vagrantfile. It's up to the user to choose which to symlink (or copy) to `Vagranfile` before running vagrant. - Rename Vagrantfile to Vagrantfile.vbox - Add Vagrantfile.libvirt - Add libvirt specific provision script - Add 'Vagrantfile' to gitignore
|
I have this on disk from a while now. Maybe could be useful? |
|
I'm using libvirt and KVM for a long time with the current vargrantfile. The only thing was to replace the sync folder to use nfs. What are your current pitfalls when using libvirt? I'm open about this change, but it sounds strange for me that I don't experience problems :D |
|
I don't remember, but I'm not expert in Vagrant nor a fan of Ruby, so could be that I overlooked something. One thing that I remember is that it was raising the "vagrant-vbguest plugin is not installed!" error despite telling vagrant to use libvirt and not having virtualbox installed at all on the system. Anyway I haven't tried that for a while: I was tiding up my disk a little and I thought it could be useful.. I'll leave to vagrant experts to decide what to do. |
|
@tobiasd You're familiar with Vagrant, aren't you? |
|
In case this PR shall be part of the 2023.09 (10) release, please redirect it towards the 2023.09-rc branch. |
I could get it working on my notebook without much troubles, but have not looked into it for some time now. |
As seems impossible (or at least not easy) to have a single Vagrantfile
with suitable configuration for different backends, this commit add two
backend-specific Vagrantfile.
It's up to the user to choose which to symlink (or copy) to
Vagranfilebefore running vagrant.