diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-06-03 12:04:13 +0000 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-06-03 12:04:13 +0000 |
| commit | 256709d2eb3fd80d768a99964be5caa61effa2a0 (patch) | |
| tree | 05b2352fba70923126836a64b6a0de43902e976a /results/classifier/105/socket/1299566 | |
| parent | 2ab14fa96a6c5484b5e4ba8337551bb8dcc79cc5 (diff) | |
| download | emulator-bug-study-256709d2eb3fd80d768a99964be5caa61effa2a0.tar.gz emulator-bug-study-256709d2eb3fd80d768a99964be5caa61effa2a0.zip | |
add new classifier result
Diffstat (limited to 'results/classifier/105/socket/1299566')
| -rw-r--r-- | results/classifier/105/socket/1299566 | 31 |
1 files changed, 31 insertions, 0 deletions
diff --git a/results/classifier/105/socket/1299566 b/results/classifier/105/socket/1299566 new file mode 100644 index 00000000..1a475daa --- /dev/null +++ b/results/classifier/105/socket/1299566 @@ -0,0 +1,31 @@ +socket: 0.755 +network: 0.710 +device: 0.662 +graphic: 0.654 +instruction: 0.616 +vnc: 0.602 +semantic: 0.579 +mistranslation: 0.490 +other: 0.486 +boot: 0.352 +assembly: 0.268 +KVM: 0.245 + +virtio serial doesn't work with virtio nic + +If virtio NIC is not used virtserialport works and delivers data written to /dev/vport0p1 to localhost:4444: + +qemu-system-x86_64 -enable-kvm -kernel mykernel -initrd myramdisk -device virtio-serial -chardev socket,host=localhost,port=4444,id=agent -device virtserialport,chardev=agent,name=hera.agent -net user -net nic + +If using virtio nic, write to /dev/vport0p1 succeeds, but no data is delivered to localhost:4444: + +qemu-system-x86_64 -enable-kvm -kernel mykernel -initrd myramdisk -device virtio-serial -chardev socket,host=localhost,port=4444,id=agent -device virtserialport,chardev=agent,name=hera.agent -net user -net nic,model=virtio + +This bug exists in 2.0 release, Debian's QEMU 1.7 package and b3706faf from git. + +Triaging old bug tickets... can you still reproduce this issue with the latest version of QEMU? Or could we close this ticket nowadays? + +I can't reproduce it now, I don't even remember this issue. + +Ok, thanks for your answer. Then let's assume that it has been fixed by one of the past releases. + |
