chore(vagrant): drop the libvirt provider, VirtualBox only - #4
Merged
Conversation
libvirt cannot share AMD-V with VirtualBox on one host, and every other Forail Vagrant environment is VirtualBox -- see forail-dev-cluster docs/TROUBLESHOOTING-vagrant.md. Verified by destroying and rebuilding this VM from scratch on the virtualbox provider.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
libvirt cannot share AMD-V with VirtualBox on one host, and every other Forail Vagrant environment is VirtualBox. The libvirt provider block is removed and the provider is pinned explicitly.
Root cause and the host-side fix are documented in
forail-dev-cluster/docs/TROUBLESHOOTING-vagrant.md.Verified: this VM destroyed and rebuilt from scratch on the virtualbox provider,
vagrant upexit 0.