VirtualBox

Ticket #11768 (closed defect: obsolete)

Opened 5 years ago

Last modified 5 weeks ago

Missing characters using serial port (reopen).

Reported by: Neofit Owned by:
Priority: major 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

Noise8k.bin Download (8.0 KB) - added by Neofit 5 years ago.
Outgoing binary data
bray.txt Download (17.5 KB) - added by Neofit 5 years ago.
Differences when receive by Br@y terminal
hterm.txt Download (132.6 KB) - added by Neofit 5 years ago.
Differences when receive by Hyperterminal
VBoxSVC.log Download (1.6 KB) - added by Neofit 5 years ago.
Session log file

Change History

Changed 5 years ago by Neofit

Outgoing binary data

Changed 5 years ago by Neofit

Differences when receive by Br@y terminal

Changed 5 years ago by Neofit

Differences when receive by Hyperterminal

Changed 5 years ago by Neofit

Session log file

comment:1 Changed 4 years ago by nothx

Same problems with 4.2.14 and also with the older build 4.1.26. XP SP3 host on debian jessie, 64 bit.

comment:2 follow-up: ↓ 5 Changed 16 months ago by aeichner

  • Status changed from new to closed
  • Resolution set to obsolete

Please reopen if still relevant with a recent VirtualBox release.

comment:3 Changed 8 weeks ago by PepSek

  • Status changed from closed to reopened
  • Resolution obsolete deleted

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 Changed 6 weeks ago by vushakov

  • Status changed from reopened to closed
  • Resolution set to obsolete

Reopening all related old bugs you can find is not helpful, especially without providing any new information.

See #17239 and its likely duplicate #17227.

comment:5 in reply to: ↑ 2 Changed 5 weeks ago by PepSek

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".

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use