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
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
|
peripherals: 0.783
socket: 0.755
network: 0.710
performance: 0.706
x86: 0.703
device: 0.662
graphic: 0.654
kernel: 0.627
architecture: 0.620
user-level: 0.617
vnc: 0.602
semantic: 0.579
permissions: 0.536
virtual: 0.505
files: 0.492
mistranslation: 0.490
hypervisor: 0.468
PID: 0.466
i386: 0.439
debug: 0.428
register: 0.410
ppc: 0.388
arm: 0.370
risc-v: 0.362
VMM: 0.357
boot: 0.352
TCG: 0.278
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.
|