VirtualBox

Changes between Initial Version and Version 1 of Ticket #17093, comment 3


Ignore:
Timestamp:
Nov 13, 2017 4:46:32 AM (6 years ago)
Author:
domyes

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #17093, comment 3

    initial v1  
    1 Replying to [comment:2 MihaiH.]:
    2 > I can't reproduce it on real hardware. I've tested with two bare-metal PCs, one running Windows 10 with VirtualBox 5.2 and an Ubuntu 17.10 64 bit guest, having attached a USB-to-serial adapter (guest serial is set to Host device). The 2nd PC, an older PC, with a build-in serial port, running Windows 7 32 bit and Python3. It doesn't matter which one runs client.py or host.py.
    3 
    4 
    5 Okay, it seems to work fine with some hardware. I can verify that it works without a fault using a setup similar to yours (usb-to-serial --> null modem --> usb-to-serial)
     1Okay, it seems to work fine with some hardware. I can verify that it works without a fault using a setup similar to [comment:2 MihaiH]. The setup I used is (usb-to-serial --> null modem --> usb-to-serial)
    62
    73However - the problem still occurs when using ports created with com0com. I reiterate that there is only a problem when forwarding the port through VirtualBox, since it works perfectly when running host.py and client.py outside of VirtualBox. The problem also occurs on a serial device with different hardware

© 2023 Oracle
ContactPrivacy policyTerms of Use