RGBCube/serenity
1
Fork 0
mirror of https://github.com/RGBCube/serenity synced 2025-07-27 06:27:45 +00:00
Code Issues Activity Actions

Documentation: Move the QEMU troubleshooting section

Browse source 
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.
This commit is contained in:
Gunnar Beutner 2021-07-10 14:49:05 +02:00
parent c3e8866118
commit e2299b52de
2 changed files with 14 additions and 13 deletions
Download patch file Download diff file Expand all files Collapse all files

13
Documentation/BuildInstructionsWindows.md
View file

@ -51,19 +51,6 @@ To run SerenityOS in a WHPX-enabled QEMU VM:
- Start the VM with `Meta/serenity.sh run` as usual. - 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 ## Note on filesystems
WSL2 filesystem performance for IO heavy tasks (such as compiling a large C++ project) on the host Windows filesystem is WSL2 filesystem performance for IO heavy tasks (such as compiling a large C++ project) on the host Windows filesystem is

14
Documentation/Troubleshooting.md
View file

@ -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 if `/dev/kvm` exists and is readable+writable by the current user. On Windows, ensure that you have
WHPX acceleration enabled. 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!" ### 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. This means the kernel is too large again. Contact us on the discord server or open a GitHub Issue about it.