Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
udp chardev works for me.
Terminal #1:
nc -4 -u -l 12345
Terminal #2:
qemu-kvm -chardev udp,id=test,port=12345,localport=54321,ipv4 \
-device isa-debugcon,iobase=0x402,chardev=test
seabios log messages show up in Terminal #1 just fine.
Now and then there is a piece missing. But note that unlike TCP the UDP protocol doesn't make any guaranties whatsoever. In case buffers are full packets are simply dropped and lost. So this is normal behavior. Packets can also be reordered.
Note that both qemu+netcat are forced into ipv4 mode to make sure they speak the same protocol.
Also note that I'm explicitly setting localport to avoid a random port being picked. This allows to keep netcat in terminal #1 running while starting qemu multiple times even though netcat will only accept packets from a single peer address.
Final note: The UDP protocol is stateless. There is no "connected" and "disconnected" state. Consequently the UDP chardev backend doesn't send open/close chardev events. Which virtio-serial might depend on to work correctly. Amit?
Bottom line: Testing the udp chardev with anything which requires a reliable stream is bogus in the first place. The only remotely useful use case for the udp chardev backend I can think of is to send guest output to a remote syslog server (which traditionally listens on udp port 514).
(In reply to Gerd Hoffmann from comment #3)
> Bottom line: Testing the udp chardev with anything which requires a
> reliable stream is bogus in the first place. The only remotely useful use
> case for the udp chardev backend I can think of is to send guest output to a
> remote syslog server (which traditionally listens on udp port 514).
I think that the right test is to validate that data is received. If some/many of the packets are lost, this is OK, as long as many packets are also received.
(In reply to Gerd Hoffmann from comment #3)
> Final note: The UDP protocol is stateless. There is no "connected" and
> "disconnected" state. Consequently the UDP chardev backend doesn't send
> open/close chardev events. Which virtio-serial might depend on to work
> correctly. Amit?
Yep, good point.