diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 16:27:09 +0000 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 16:27:09 +0000 |
| commit | 4d9e26c0333abd39bdbd039dcdb30ed429c475ba (patch) | |
| tree | 4010d5fb3e8bc48c110a2c1ff2a16b8648cb86bb /results/classifier/accel-gemma3:12b/kvm/1888 | |
| parent | 5541099586dbd6018574cb44e1934907c121526f (diff) | |
| download | qemu-analysis-4d9e26c0333abd39bdbd039dcdb30ed429c475ba.tar.gz qemu-analysis-4d9e26c0333abd39bdbd039dcdb30ed429c475ba.zip | |
add gemma accelerator classification results
Diffstat (limited to 'results/classifier/accel-gemma3:12b/kvm/1888')
| -rw-r--r-- | results/classifier/accel-gemma3:12b/kvm/1888 | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/results/classifier/accel-gemma3:12b/kvm/1888 b/results/classifier/accel-gemma3:12b/kvm/1888 new file mode 100644 index 000000000..358b731b8 --- /dev/null +++ b/results/classifier/accel-gemma3:12b/kvm/1888 @@ -0,0 +1,13 @@ + +megasas: Buffer I/O error on dev sda / critical target error, dev sda, sector 0 op 0x0:(READ) +Description of problem: +Since QEMU 7.2.0 when using `megasas` device the guest kernel is unable to I/O with the device (Input/output error) also producing errors messages in `dmesg` like these: +``` +[ 18.739344] critical target error, dev sda, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 +[ 18.739925] Buffer I/O error on dev sda, logical block 0, async page read +[ 18.740374] Dev sda: unable to read RDB block 0 +``` + +Relevant options are: `-device megasas -blockdev driver=null-co,read-zeroes=on,node-name=null -device scsi-hd,drive=null` then in guest `modprobe megaraid-sas`. With qcow2 images - errors are the same. + +I also tested that the same commands produce no errors on QEMU 6.0.0 - 7.1.0. |