From 001fc1f0f803e1df3fd85dd5aa2a9aade34a2c90 Mon Sep 17 00:00:00 2001 From: Jonas DOREL Date: Sat, 15 Feb 2020 15:00:45 +0100 Subject: [PATCH] Move gui-troubleshooting to gui-configuration-and-troubleshooting --- troubleshooting/gui-not-working.md | 33 ------------------------------ 1 file changed, 33 deletions(-) delete mode 100644 troubleshooting/gui-not-working.md diff --git a/troubleshooting/gui-not-working.md b/troubleshooting/gui-not-working.md deleted file mode 100644 index 769db6f..0000000 --- a/troubleshooting/gui-not-working.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -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 # Make sure the VM is started -sudo xl console -~~~ - -## Tips - -### Disable auditd messages - -To disable auditd messages, you need to edit your VM kernel parameters: - -~~~ -previous_kernel_parameters=$(qvm-prefs --get kernelopts) # Get current kernel parameters -qvm-prefs --set kernelopts " 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.