From c36e5a1b645bfe1f885b631cb7ba27026dca1681 Mon Sep 17 00:00:00 2001
From: Jonas DOREL <jonas@dorel.me>
Date: Sat, 15 Feb 2020 14:05:27 +0100
Subject: [PATCH] Create gui-not-working.md

---
 external/troubleshooting/gui-not-working.md | 33 +++++++++++++++++++++
 1 file changed, 33 insertions(+)
 create mode 100644 external/troubleshooting/gui-not-working.md

diff --git a/external/troubleshooting/gui-not-working.md b/external/troubleshooting/gui-not-working.md
new file mode 100644
index 00000000..769db6fb
--- /dev/null
+++ b/external/troubleshooting/gui-not-working.md
@@ -0,0 +1,33 @@
+---
+layout: doc
+title: GUI Troubleshooting
+  permalink: /doc/gui-troubleshooting/
+redirect_from:
+- /en/doc/gui-troubleshooting/
+- /doc/GuiTroubleshooting/
+- /wiki/GuiTroubleshooting/
+---
+
+# GUI Troubleshooting
+
+If you can start your VM, but can't launch any applications, then you need to fix the issues from the `VM console`, accessible from xen through:
+
+~~~
+qvm-start <VMname> # Make sure the VM is started
+sudo xl console <VMname>
+~~~
+
+## Tips
+
+### Disable auditd messages
+
+To disable auditd messages, you need to edit your VM kernel parameters:
+
+~~~
+previous_kernel_parameters=$(qvm-prefs --get <VMname> kernelopts) # Get current kernel parameters
+qvm-prefs --set <VMname> kernelopts "<previous_kernel_parameters> audit=0"
+~~~
+
+Then, restart your VM.
+
+Once your troubleshooting is done, don't forget to remove this kernel parameters, it makes troubleshooting VMs not starting easier.