#11768 closed defect (obsolete)
Missing characters using serial port (reopen).
Reported by: | Neofit | Owned by: | |
---|---|---|---|
Component: | uart | Version: | VirtualBox 4.2.6 |
Keywords: | virtual UART lost and swap bytes | Cc: | |
Guest type: | Windows | Host type: | Linux |
Description
Good day, ladies and genlemens.
I collide with issue decribed at https://www.virtualbox.org/ticket/1548.
I use VirtualBox 4.2.6 build 82870 under Xubuntu 12.04 LTS AMD64 for emulate Windows XP prof SP3. Some time ago I see that data received in XP (115200, 8 bit of data, no parity, no flow control, 2 stop bits) from my hardware temporary out of trend. Now I check this ussie.
For tight coverage today I use GtkTerm for send 8k pseudo-random data from Xubuntu (ttyS1) to XP (ttyS0 mirrored to COM1). Normally I use under XP "Br@y terminal" and today I try to use standart Hyperterminal aslo. I use same setting as I use with my hardware. In attaced files you can see outgoing data (noise8k.bin) and differences between reseived and transmitted data (bray.txt, hterm.txt).
As I see - Br@y lost approx. 1k series byte after receive first 1k bytes. Hyperterminal - lost by one byte randomly and swap bytes.
Attachments (4)
Change History (9)
by , 11 years ago
Attachment: | Noise8k.bin added |
---|
comment:1 by , 11 years ago
Same problems with 4.2.14 and also with the older build 4.1.26. XP SP3 host on debian jessie, 64 bit.
follow-up: 5 comment:2 by , 8 years ago
Resolution: | → obsolete |
---|---|
Status: | new → closed |
Please reopen if still relevant with a recent VirtualBox release.
comment:3 by , 7 years ago
Resolution: | obsolete |
---|---|
Status: | closed → reopened |
This still is a problem while running the latest VirtualBox (5.2.0) under Windows 10 (64bit). I have tracked this issue down and it seems like the last version that the COM ports were working properly was 4.1.44
comment:4 by , 7 years ago
Resolution: | → obsolete |
---|---|
Status: | reopened → closed |
comment:5 by , 7 years ago
Replying to aeichner:
Please reopen if still relevant with a recent VirtualBox release.
This bug is still relevant with the most recent VirtualBox release, as well as a couple dozen other recent ones.
As I guess tracking it down to the release that broke it isn't "new information".
Outgoing binary data