Following Hyperpill example for QEMU 8.0.0 with ASAN doesnt find crashes

[NoHandsMate]

Hi,
I've followed the example in Hyperpill-snap for QEMU 8.0.0 with ASAN but Hyperpill didnt trigger any crashes after running the fuzzer for more than 24 hours. Reading the logs got me nowhere. Some entries in the log are like bad data written to virtio-scsi configuration space or write: eepro100: feature is missing in this emulation: unknown byte write . Others instead caught my attention: write: eepHotspot Pos 3 Hint: fd0000fd (vs fd) PC: 559c0d81634d; Hotspot Pos 3 Hint: fe0000fd (vs fd) PC: 559c0d817292.
I wanted also to use symbolization but for some reason the scp commands fails because some auth errors.
Google Drive link to one of the logs if someone wants to take a look
Thank you for your help

[NoHandsMate]

I think that even in my case the enumeration process remains stuck at PIO READ ADDR: 3f9 and PIO READ ADDR:3fd, like in the issue #9

[cyruscyliu]

bad data written to virtio-scsi configuration space

write: eepro100: feature is missing in this emulation: unknown byte write

write: eepHotspot Pos 3 Hint: fd0000fd (vs fd)  PC: 559c0d81634d; Hotspot Pos 3   Hint: fe0000fd (vs fd)  PC: 559c0d817292.

They are mixed output of QEMU and HyperPill. Unfortunately, they are not crashes.

[cyruscyliu]

Regarding the hang,

Please retake the snapshot by updating the command line to run L1 VM.

-cpu host,-pku,-xsaves,-kvmclock,-kvm-pv-unhalt,-hle,-rtm

[cyruscyliu]

Currently, clock_stop() has not been added to this version. So very hard to trigger any crash.

Please be patient. Please follow #6.

[cyruscyliu]

Regarding scp, is there any error message? It should work perfectly if you correctly set up port forwarding.