Seems like the problems isn't really new and might be at least 6 years
old if not more. https://robert.penz.name/550/mapping-a-serial-device-
to-a-kvm-guest-may-lead-to-communication-problems/
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to
After doing a bit of research I think line 142 in file chardev/char-
serial.c is problematic.
https://github.com/qemu/qemu/blob/master/chardev/char-serial.c#L142
It enables output processing, which is something unwanted here. With a
simple test program I found out that by default, besides OPOST, O
I am unable to provide complete QEMU command line as I'm using virt-manager to
deal with configuration. I can say that two serial ports are linked with
physical ones through the /dev/ttyS* files.
The guests I tested it with are Windows 98 and Windows XP. For the testing I
connected one port to a
Public bug reported:
When sending data through serial from guest each time 0x0A byte is sent
0x0D is sent before it. For example, when sending {0x29, 0x0A} on the
other end I receive {0x29, 0x0D, 0x0A}.
** Affects: qemu
Importance: Undecided
Status: New
** Tags: com serial
--
Yo
