From c229735f7fa7c90abc69d4412d37c126cd40eec7 Mon Sep 17 00:00:00 2001 From: Alex Rougebec <122404476+arougey@users.noreply.github.com> Date: Wed, 31 Jan 2024 11:45:02 -0500 Subject: [PATCH] [Documentation:Developer] Fedora VM installation instructions (#575) Added Fedora Linux/RHEL install instructions for vagrant and VirtualBox to the Submitty.org developer page, as well as a few common issues. --- .../vm_install_using_vagrant.md | 34 +++++++++++++++++++ 1 file changed, 34 insertions(+) diff --git a/_docs/developer/getting_started/vm_install_using_vagrant.md b/_docs/developer/getting_started/vm_install_using_vagrant.md index 43c1c9cc..2863c9f4 100644 --- a/_docs/developer/getting_started/vm_install_using_vagrant.md +++ b/_docs/developer/getting_started/vm_install_using_vagrant.md @@ -147,6 +147,40 @@ Below are quick steps to get everything installed and running. Vagrant: (if that doesn't work, try: ) + **Fedora/Red Hat Linux** + + * For Fedora, the latest version of VirtualBox is recommended to prevent errors. Download the RPM from the virtual box website. Make sure your version of + Fedora is up to date using + ``` + sudo dnf update + sudo dnf upgrade + ``` + and inputting your password. Then install the Virtual Box rpm using: + ``` + sudo dnf install VirtualBox-xxxxx.rpm + ``` + Install Vagrant using: + ``` + sudo dnf install vagrant + ``` + Now move on to step 5. + + **NOTE** + when running vagrant up, use `vagrant up --provider=virtualbox` so it doesnt default to libvirt + + **Common errors when running vagrant up(Fedora/RHEL)** + 1. Missing virtnetworkd: + Enable it in your terminal by running: + ``` + sudo systemctl start virtnetworkd + ``` + 2. If your vagrant ever freezes kill it with + ''' + VBoxManage controlvm VM_NAME poweroff + ''' + or if that doesn't work, reboot the computer and then run `vagrant destroy` before re-running `vagrant up --provider=virtualbox` again. + + 5. Clone [the Submitty repository](https://github.com/Submitty/Submitty) to a location on your computer (the "host").