-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix vagrant config for libvirt #42
Conversation
I have zero experience with that. @gauravgahlot somebody is can verify that from your end?! Or @thebsdbox do you use libvirt? :) |
|
libvirt__dhcp_enabled: false, | ||
libvirt__forward_mode: 'none', | ||
libvirt__adapter: 1, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was needed to ensure that the private network isn't accidentally picked up as eth0 instead of eth1.
@@ -56,6 +60,8 @@ Vagrant.configure('2') do |config| | |||
lv.cpus = 1 | |||
lv.boot 'network' | |||
lv.mgmt_attach = false | |||
lv.storage :file, :size => '40G' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Without this, you cannot actually run a workflow that does something like install an OS to disk.
CI check seems to be failing on an issue unrelated to this PR. |
Yep fixed via #44 , do you mind rebasing, please? |
Description
Fixes the vagrant configuration when using libvirt
Why is this needed
Without this issue the vagrant provisioner fails when using libvirt with the following error:
How Has This Been Tested?
Reran vagrant up after making the changes and the provisioner machine successfully was created
How are existing users impacted? What migration steps/scripts do we need?
Should not affect existing users unless they were trying to use vagrant/libvirt and were unsuccessful before.
No migration should be needed.