Opened 7 years ago
Last modified 7 years ago
#17239 new defect
Serial port missing characters.
| Reported by: | jim_ | Owned by: | |
|---|---|---|---|
| Component: | uart | Version: | VirtualBox 5.2.0 |
| Keywords: | Cc: | ||
| Guest type: | Linux | Host type: | Windows |
Description
Using 'Windows 10' as host, and being Linux 'Ubuntu 14.04 LTS' as guest, with Virtual Box 5.2.0 and its associated guest additions, once the guest Ubuntu has been launched, by using the serial port: /dev/ttyS0, from within the guest, some characters are missed (they don't appear in the serialized stream of data shown in the terminal's screen).
This problem is also present in other versions of virtual box (for example: 5.1.18). On the other hand, this issue works fine under Windows 7 as host using virtual box 5.1.18.
¿Perhaps is there some incompatibility between guest additions and windows 10?
Attachments (5)
Change History (14)
by , 7 years ago
| Attachment: | Ubuntu-2017-11-03-18-33-12.log added |
|---|
follow-up: 2 comment:1 by , 7 years ago
Do you miss data in the guest, on the host or in both directions?
This might be the same regression as in #17093 but you say you see it with 5.1.18. Do I understand correctly that you see it with 5.1.18 on Windows 10, but not with 5.1.18 on Windows 7?
Can you try the tests from #17093 to see if you are seeing the same problem?
comment:2 by , 7 years ago
Replying to vushakov:
Do you miss data in the guest, on the host or in both directions?
In the guest.
This might be the same regression as in #17093 but you say you see it with 5.1.18. Do I understand correctly that you see it with 5.1.18 on Windows 10, but not with 5.1.18 on Windows 7?
Yes, I see it with 5.1.18 on Windows 10, but not with 5.1.18 on Windows 7.
Can you try the tests from #17093 to see if you are seeing the same problem?
I think that the problem is different, because in my case, the communication in the guest is established with the only problem that randomly some serial characters are missed.
The serial communication is started from within the guest [Ubuntu 14.04] by using /dev/ttyS0 (physical RS232 port of my PC) from a Linux terminal. The communication works fine although randomly some characters are missed. All the communication process is taking place in the guest (in order to obtain debug traces).
My host operating system is: Windows 10 Enterprise (version: 1709, compilation: 16299.19).
follow-up: 4 comment:3 by , 7 years ago
Ok, I was not clear enough. Do you miss characters sent to the guest, or characters sent from the guest?
comment:4 by , 7 years ago
Replying to vushakov:
Ok, I was not clear enough. Do you miss characters sent to the guest, or characters sent from the guest?
Well, I see traces sent by an IED to my PC. This serial traces can be seen in my Linux terminal, so the missed characters are sent 'to' the guest 'from' an external IED connected to the PC by means of a RS232 com port.
Best regards.
comment:5 by , 7 years ago
Hi, are you going to do something about this issue? I see that is stopped five weeks ago. I think that is an important issue. Please go for it.
Regards.
comment:6 by , 7 years ago
Keep in mind that psychological pressure, the sort that you tried to apply in your comment, actually makes the developers less keen to look at an issue. Developers have their own priorities and schedule, and unless you're a paying customer, you can't pressure too much for a fix.
comment:7 by , 7 years ago
At least, I have warned you about the existence of the problem (thanks for nothing). The effect of the serial port missing characters is very regrettable. Have a nice day and excuse me if I have offend you in any way.
comment:8 by , 7 years ago
You have not offended me at all, not sure why you got this as a personal offense. I was simply stating that the developers are aware of these issues and they're working on it. "Bumping" a thread and "demanding" a fix is not the best approach. They have their own priorities and schedule. That's all I was saying...
comment:9 by , 7 years ago
We are aware of the issue but didn't had time to look deeper into this yet because of higher priority issues. Please understand that this bug tracker is handled on a best effort basis, issues from paying customers naturally have a higher priority than issues from non paying users (we still highly appreciate the reports and testing the community does). This also doesn't look like a recent regression (or regression at all) which also has an impact on the priority.
VirtualBox logs.