summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/105/socket/1299566
blob: 1a475daa9628945d5e1503ee5283cac0008bc90a (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
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.