summary refs log tree commit diff stats
path: root/results/classifier/deepseek-2-tmp/output/manual-review/1224444
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/deepseek-2-tmp/output/manual-review/1224444')
-rw-r--r--results/classifier/deepseek-2-tmp/output/manual-review/122444455
1 files changed, 0 insertions, 55 deletions
diff --git a/results/classifier/deepseek-2-tmp/output/manual-review/1224444 b/results/classifier/deepseek-2-tmp/output/manual-review/1224444
deleted file mode 100644
index 59730b19..00000000
--- a/results/classifier/deepseek-2-tmp/output/manual-review/1224444
+++ /dev/null
@@ -1,55 +0,0 @@
-
-virtio-serial loses writes when used over virtio-mmio
-
-virtio-serial appears to lose writes, but only when used on top of virtio-mmio.  The scenario is this:
-
-/home/rjones/d/qemu/arm-softmmu/qemu-system-arm \
-    -global virtio-blk-device.scsi=off \
-    -nodefconfig \
-    -nodefaults \
-    -nographic \
-    -M vexpress-a15 \
-    -machine accel=kvm:tcg \
-    -m 500 \
-    -no-reboot \
-    -kernel /home/rjones/d/libguestfs/tmp/.guestfs-1001/kernel.27944 \
-    -dtb /home/rjones/d/libguestfs/tmp/.guestfs-1001/dtb.27944 \
-    -initrd /home/rjones/d/libguestfs/tmp/.guestfs-1001/initrd.27944 \
-    -device virtio-scsi-device,id=scsi \
-    -drive file=/home/rjones/d/libguestfs/tmp/libguestfsLa9dE2/scratch.1,cache=unsafe,format=raw,id=hd0,if=none \
-    -device scsi-hd,drive=hd0 \
-    -drive file=/home/rjones/d/libguestfs/tmp/.guestfs-1001/root.27944,snapshot=on,id=appliance,cache=unsafe,if=none \
-    -device scsi-hd,drive=appliance \
-    -device virtio-serial-device \
-    -serial stdio \
-    -chardev socket,path=/home/rjones/d/libguestfs/tmp/libguestfsLa9dE2/guestfsd.sock,id=channel0 \
-    -device virtserialport,chardev=channel0,name=org.libguestfs.channel.0 \
-    -append 'panic=1 mem=500M console=ttyAMA0 udevtimeout=600 no_timer_check acpi=off printk.time=1 cgroup_disable=memory root=/dev/sdb selinux=0 guestfs_verbose=1 TERM=xterm-256color'
-
-After the guest starts up, a daemon writes 4 bytes to a virtio-serial socket.  The host side reads these 4 bytes correctly and writes a 64 byte message.  The guest never sees this message.
-
-I enabled virtio-mmio debugging, and this is what is printed (## = my comment):
-
-## guest opens the socket:
-trying to open virtio-serial channel '/dev/virtio-ports/org.libguestfs.channel.0'
-virtio_mmio: virtio_mmio_write offset 0x50 value 0x3
-opened the socket, sock = 3
-udevadm settle
-## guest writes 4 bytes to the socket:
-virtio_mmio: virtio_mmio_write offset 0x50 value 0x5
-virtio_mmio: virtio_mmio setting IRQ 1
-virtio_mmio: virtio_mmio_read offset 0x60
-virtio_mmio: virtio_mmio_write offset 0x64 value 0x1
-virtio_mmio: virtio_mmio setting IRQ 0
-sent magic GUESTFS_LAUNCH_FLAG
-## host reads 4 bytes successfully:
-main_loop libguestfs: recv_from_daemon: received GUESTFS_LAUNCH_FLAG
-libguestfs: [14605ms] appliance is up
-Guest launched OK.
-## host writes 64 bytes to socket:
-libguestfs: writing the data to the socket (size = 64)
-waiting for next request
-libguestfs: data written OK
-## hangs here forever with guest in read() call never receiving any data
-
-I am using qemu from git today (2d1fe1873a984).
\ No newline at end of file