diff options
| author | Andrey Konovalov <andreyknvl@google.com> | 2017-10-26 19:28:24 +0200 |
|---|---|---|
| committer | Andrey Konovalov <andreyknvl@gmail.com> | 2017-10-27 10:04:34 +0200 |
| commit | 127b1dd85c3fb269b5091e57d35974b54a2af668 (patch) | |
| tree | a40640a9136b0c540a7524364992185b440ef4df /docs/troubleshooting.md | |
| parent | 26d265c811929d03c4d27e5fe53f7de5bde32215 (diff) | |
docs: move linux kernel specific docs to docs/linux/ dir
Diffstat (limited to 'docs/troubleshooting.md')
| -rw-r--r-- | docs/troubleshooting.md | 25 |
1 files changed, 2 insertions, 23 deletions
diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index ed6e66186..bd705ee38 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -2,29 +2,6 @@ Here are some things to check if there are problems running syzkaller. - - Check that QEMU can successfully boot the virtual machine. For example, - if `IMAGE` is set to the VM's disk image (as per the `image` config value) - and `KERNEL` is set to the test kernel (as per the `kernel` config value) - then something like the following command should start the VM successfully: - - ```qemu-system-x86_64 -hda $IMAGE -m 256 -net nic -net user,host=10.0.2.10,hostfwd=tcp::23505-:22 -enable-kvm -kernel $KERNEL -append root=/dev/sda``` - - - Check that inbound SSH to the running virtual machine works. For example, with - a VM running and with `SSHKEY` set to the SSH identity (as per the `sshkey` config value) the - following command should connect: - - ```ssh -i $SSHKEY -p 23505 root@localhost``` - - - Check that the `CONFIG_KCOV` option is available inside the VM: - - `ls /sys/kernel/debug # Check debugfs mounted` - - `ls /sys/kernel/debug/kcov # Check kcov enabled` - - Build the test program from `Documentation/kcov.txt` and run it inside the VM. - - - Check that debug information (from the `CONFIG_DEBUG_INFO` option) is available - - Pass the hex output from the kcov test program to `addr2line -a -i -f -e $VMLINUX` (where - `VMLINUX` is the vmlinux file, as per the `vmlinux` config value), to confirm - that symbols for the kernel are available. - - Use the `-debug` command line option to make syzkaller print all possible debug output, from both the `syz-manager` top-level program and the `syz-fuzzer` instances. With this option syzkaller will only run one VM instance. @@ -44,6 +21,8 @@ Here are some things to check if there are problems running syzkaller. In this case, running the `syz-execprog` test with the `-sandbox=setuid` option fixes the problem, so the main configuration needs to be updated to set `sandbox` to `setuid`. +Also see [this](linux/troubleshooting.md) for Linux kernel specific troubleshooting advice. + If none of the above helps, file a bug on [the bug tracker](https://github.com/google/syzkaller/issues) or ask us directly on the syzkaller@googlegroups.com mailing list. Please include syzkaller commit id that you use and `syz-manager` output with `-debug` flag enabled if applicable. |