On Sat, Sep 26, 2020 at 1:21 PM Borislav Petkov <[email protected]> wrote: > > On Wed, Sep 23, 2020 at 05:20:06PM +0200, Dmitry Vyukov wrote: > > It's a random fuzzing workload. You can get this workload by running > > syzkaller locally: > > https://github.com/google/syzkaller/blob/master/docs/linux/setup_ubuntu-host_qemu-vm_x86-64-kernel.md > > Yeah, the my.cfg example suggests that the syz-manager starts the guest > and supplies the kernel, etc. > > Is there a possibility to run the workload in an already existing guest > which I've booted prior? > > I'm asking because I have all the infra for testing kernels in guests > already setup here and it would be easier for me to simply run the > workload directly in the guest and then poke at it.
+syzkaller mailing list There is also "isolated" VM type, which allows to connect to a set of external machines via ssh: https://github.com/google/syzkaller/blob/master/vm/isolated/isolated.go#L29-L37 However, it's better to have lots of them and with a console cables, and still sometimes they may brick for various reasons. There is also syz-stress utility that may run some workload directly on the underlying kernel: https://github.com/google/syzkaller/blob/master/tools/syz-stress/stress.go#L29 However, it does not use corpus/coverage, so I don't know if it will be able to reproduce these crashes or not. It will also be up to you then to restart the VM/fuzzing every minute.
