From 54cbc73031cad7d13b19c59a29979a077fc94425 Mon Sep 17 00:00:00 2001 From: Andrey Konovalov Date: Mon, 29 Jun 2020 15:00:45 +0200 Subject: Update setup_ubuntu-host_qemu-vm_x86-64-kernel.md --- docs/linux/setup_ubuntu-host_qemu-vm_x86-64-kernel.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'docs') diff --git a/docs/linux/setup_ubuntu-host_qemu-vm_x86-64-kernel.md b/docs/linux/setup_ubuntu-host_qemu-vm_x86-64-kernel.md index db5803b6a..ed63c4cdf 100644 --- a/docs/linux/setup_ubuntu-host_qemu-vm_x86-64-kernel.md +++ b/docs/linux/setup_ubuntu-host_qemu-vm_x86-64-kernel.md @@ -166,12 +166,14 @@ ssh -i $IMAGE/stretch.id_rsa -p 10021 -o "StrictHostKeyChecking no" root@localho If this fails with "too many tries", ssh may be passing default keys before the one explicitly passed with `-i`. Append option `-o "IdentitiesOnly yes"`. -To kill the running QEMU instance: +To kill the running QEMU instance press `Ctrl+A` and then `X` or run: ``` bash kill $(cat vm.pid) ``` +If QEMU works, the kernel boots and ssh succeeds, you can try to run syzkaller. + ## syzkaller Build syzkaller as described [here](/docs/linux/setup.md#go-and-syzkaller). -- cgit mrf-deployment