From e2299b52deec1b189e9d692b2c7d7e3ffa77466e Mon Sep 17 00:00:00 2001 From: Gunnar Beutner Date: Sat, 10 Jul 2021 14:49:05 +0200 Subject: [PATCH] Documentation: Move the QEMU troubleshooting section This is no longer relevant for most users because due to an unrelated change to Meta/run.sh the default display backend is now SDL which does not exhibit this problem. --- Documentation/BuildInstructionsWindows.md | 13 ------------- Documentation/Troubleshooting.md | 14 ++++++++++++++ 2 files changed, 14 insertions(+), 13 deletions(-) diff --git a/Documentation/BuildInstructionsWindows.md b/Documentation/BuildInstructionsWindows.md index 23ea81778c1..9d7fc218740 100644 --- a/Documentation/BuildInstructionsWindows.md +++ b/Documentation/BuildInstructionsWindows.md @@ -51,19 +51,6 @@ To run SerenityOS in a WHPX-enabled QEMU VM: - Start the VM with `Meta/serenity.sh run` as usual. -### Known issues with WHPX - -#### Slow boot on HiDPI systems - -On some Windows systems running with >100% scaling, the booting phase of Serenity might slow to a crawl. Changing the -zoom settings of the QEMU window will speed up the emulation, but you'll have to squint harder to read the smaller display. - -A quick workaround is opening the properties of the QEMU executable at `C:\Program Files\qemu\qemu-system-x86_64.exe`, and -in the Compatibility tab changing the DPI settings to force the scaling to be performed by the System, by changing the -setting at at the bottom of the window. The QEMU window will now render at normal size while retaining acceptable emulation speeds. - -This is being tracked as issue [#7657](https://github.com/SerenityOS/serenity/issues/7657). - ## Note on filesystems WSL2 filesystem performance for IO heavy tasks (such as compiling a large C++ project) on the host Windows filesystem is diff --git a/Documentation/Troubleshooting.md b/Documentation/Troubleshooting.md index 752f24f7c12..359a296fddc 100644 --- a/Documentation/Troubleshooting.md +++ b/Documentation/Troubleshooting.md @@ -28,6 +28,20 @@ On Linux, QEMU is significantly faster if it's able to use KVM. The run script w if `/dev/kvm` exists and is readable+writable by the current user. On Windows, ensure that you have WHPX acceleration enabled. +### Slow boot on HiDPI systems + +On some Windows systems running with >100% scaling, the booting phase of Serenity might slow to a crawl. Changing the +zoom settings of the QEMU window will speed up the emulation, but you'll have to squint harder to read the smaller display. + +The default display backend (`SERENITY_QEMU_DISPLAY_BACKEND=sdl,gl=off`) does _not_ have this problem. If you're +running into this problem, make sure you haven't changed the QEMU display backend. + +A quick workaround is opening the properties of the QEMU executable at `C:\Program Files\qemu\qemu-system-x86_64.exe`, and +in the Compatibility tab changing the DPI settings to force the scaling to be performed by the System, by changing the +setting at at the bottom of the window. The QEMU window will now render at normal size while retaining acceptable emulation speeds. + +This is being tracked as issue [#7657](https://github.com/SerenityOS/serenity/issues/7657). + ### Boot fails with "Error: Kernel Image too big for memory slot. Halting!" This means the kernel is too large again. Contact us on the discord server or open a GitHub Issue about it.