| 1 | | Ran into this problem on 6.1.16 and installed 6.1.18 r142142 this morning. Still get the issue. FWIW, same guest OS; host is Mint Tricia 19.3. The guest VM in question has a number of radio-control programs installed; these all use serial ports to communicate with attached hardware. In my case, the problem is extremely easy to reproduce: Connect a serial cable to the host's physical COM ports, jumper pins 2 and 3 then start VirtualBox and the guest XP-SP3 VM. As soon as the guest's various device drivers begin to initialize you'll get the SerialIOportError. /dev/ttyS0 is an onboard port (Intel motherboard) while /dev/ttyS4 through S7 are part of a PCIe 4-port add-in card. Doesn't matter which physical hardware is used; results are the same. |
| | 1 | Ran into this problem on 6.1.16 and installed 6.1.18 r142142 this morning. Still get the issue. FWIW, same guest OS; host is Mint Tricia 19.3. The guest VM in question has a number of radio-control programs installed; these all use serial ports to communicate with attached hardware. Upon communication being initiated to any attached device, the error referenced in the original posting will display. |
| | 2 | |
| | 3 | In my case, the problem is extremely easy to reproduce: Connect a serial cable to the host's physical COM ports, jumper pins 2 and 3 then start VirtualBox and the guest XP-SP3 VM. As soon as the guest's various device drivers begin to initialize you'll get the SerialIOportError. /dev/ttyS0 is an onboard port (Intel motherboard) while /dev/ttyS4 through S7 are part of a PCIe 4-port add-in card. Doesn't matter which physical hardware is used; results are the same. |
