diff options
| author | Simon Haegler <simon.haegler@protonmail.ch> | 2022-12-30 13:00:27 +0100 |
|---|---|---|
| committer | Andrew Kaster <andrewdkaster@gmail.com> | 2023-02-02 02:02:23 -0700 |
| commit | 5220afcf738a4299b1a2e753ec25060c9766caa6 (patch) | |
| tree | 2a2f51f4c1c8610bd552987fe0fd3d61cfe63794 | |
| parent | bfbb4bcd9bd91bc83fcd98097e664cf56916ca67 (diff) | |
| download | serenity-5220afcf738a4299b1a2e753ec25060c9766caa6.zip | |
Documentation: Add troubleshooting note regarding KVM GDB
| -rw-r--r-- | Documentation/Troubleshooting.md | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/Documentation/Troubleshooting.md b/Documentation/Troubleshooting.md index b5a3752b62..5d973eb065 100644 --- a/Documentation/Troubleshooting.md +++ b/Documentation/Troubleshooting.md @@ -58,3 +58,8 @@ extensions, or you try to use VirtualBox without using a x64 virtualization mode - If booting on bare metal, your CPU is too old to boot Serenity. - If you're using VirtualBox, you need to enable PAE/NX. Check the instructions [here.](VirtualBox.md) - If you're using QEMU, the [CPU model configuration](https://qemu-project.gitlab.io/qemu/system/qemu-cpu-models.html) is not exposing PAE. + +### Boot fails with "KVM doesn't support guest debugging" +- Update your host kernel to at least version `5.10`. This is the oldest kernel which properly supports the required KVM capability `KVM_CAP_SET_GUEST_DEBUG` (see corresponding [kernel commit](https://github.com/torvalds/linux/commit/b9b2782cd5)). +- Make sure that your distro has the qemu debug feature actually enabled (the corresponding check is [here](https://gitlab.com/qemu-project/qemu/-/blob/222059a0fccf4af3be776fe35a5ea2d6a68f9a0b/accel/kvm/kvm-all.c#L2540)). +- Or, disable KVM debugging by setting this env var when running serenity: `SERENITY_DISABLE_GDB_SOCKET=1` |