From c36e5a1b645bfe1f885b631cb7ba27026dca1681 Mon Sep 17 00:00:00 2001 From: Jonas DOREL Date: Sat, 15 Feb 2020 14:05:27 +0100 Subject: [PATCH 1/3] 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 # 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. From a0c773d4a4ad855e8e0e5bb19039cea3ed05965b Mon Sep 17 00:00:00 2001 From: Jonas DOREL Date: Sat, 15 Feb 2020 15:00:45 +0100 Subject: [PATCH 2/3] Move gui-troubleshooting to gui-configuration-and-troubleshooting --- external/troubleshooting/gui-not-working.md | 33 ------------------ .../gui-configuration.md | 34 ++++++++++++++++--- 2 files changed, 29 insertions(+), 38 deletions(-) delete mode 100644 external/troubleshooting/gui-not-working.md diff --git a/external/troubleshooting/gui-not-working.md b/external/troubleshooting/gui-not-working.md deleted file mode 100644 index 769db6fb..00000000 --- a/external/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. diff --git a/user/advanced-configuration/gui-configuration.md b/user/advanced-configuration/gui-configuration.md index f8dd096b..37a71cdf 100644 --- a/user/advanced-configuration/gui-configuration.md +++ b/user/advanced-configuration/gui-configuration.md @@ -1,14 +1,14 @@ --- layout: doc title: GUI Configuration and Troubleshooting -permalink: /doc/gui-configuration/ +permalink: /doc/gui-configuration-and-troubleshooting/ +redirect_from: + - /doc/gui-configuration/ --- -GUI Configuration and Troubleshooting -===================================== +# GUI Configuration and Troubleshooting -Video RAM adjustment for high-resolution displays -------------------------------------------------- +## Video RAM adjustment for high-resolution displays **Problem:** You have a 4K external display, and when you connect it, you can't click on anything but a small area in the upper-right corner. @@ -50,3 +50,27 @@ Section "Device" Option "TearFree" "true" EndSection ``` + +## 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: + +```sh +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: + +```sh +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. From da74d6ba825065efc118e5e343244b57da4e5011 Mon Sep 17 00:00:00 2001 From: Andrew David Wong Date: Fri, 28 Feb 2020 10:53:29 -0600 Subject: [PATCH 3/3] Fix typos --- user/advanced-configuration/gui-configuration.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/user/advanced-configuration/gui-configuration.md b/user/advanced-configuration/gui-configuration.md index 37a71cdf..fcfb37a2 100644 --- a/user/advanced-configuration/gui-configuration.md +++ b/user/advanced-configuration/gui-configuration.md @@ -62,9 +62,9 @@ sudo xl console ### Tips -#### Disable auditd messages +#### Disable audited messages -To disable auditd messages, you need to edit your VM kernel parameters: +To disable audited messages, you need to edit your VM kernel parameters: ```sh previous_kernel_parameters=$(qvm-prefs --get kernelopts) # Get current kernel parameters