mirror of
https://github.com/RGBCube/serenity
synced 2025-07-27 17:17:45 +00:00
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.
This commit is contained in:
parent
c3e8866118
commit
e2299b52de
2 changed files with 14 additions and 13 deletions
|
@ -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
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue