From 63b9af13c817a7ea1418813e4c5318557d0cc50b Mon Sep 17 00:00:00 2001
From: zacharymnp <56311867+zacharymnp@users.noreply.github.com>
Date: Fri, 14 Feb 2025 16:38:52 -0500
Subject: [PATCH] reminder to keep VM terminal open

---
 _docs/developer/troubleshooting/installation_troubleshooting.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/_docs/developer/troubleshooting/installation_troubleshooting.md b/_docs/developer/troubleshooting/installation_troubleshooting.md
index 7010b4b9..e94acf99 100644
--- a/_docs/developer/troubleshooting/installation_troubleshooting.md
+++ b/_docs/developer/troubleshooting/installation_troubleshooting.md
@@ -9,6 +9,7 @@ category: Developer > Development Troubleshooting
    Having the VM's terminal GUI open can seem to keep it awake for communication. While developing on Submitty,
    this "Show" terminal option can sometimes lead to the VM being faster with loads, so it may be worth having the GUI
    open even after your vagrant up.
+  * If the VM environment becomes stuck on any command for more than three minutes, opening the VM's terminal GUI may prompt it to continue. Keeping the terminal open is generally a good idea.
 
 * If your install seems to randomly freeze during `vagrant up` 
 with no explanation, then there are a couple of things that may be going wrong: