Searching for virtual serial port tools compatible with Virtualbox.
Searching for virtual serial port tools compatible with Virtualbox.
On my projects, certain tools need a Windows XP-based physical computer to set up and manage through RS232. I have a modern laptop with Windows 10, but I've struggled to run the same apps in Virtualbox using Windows XP, even after making COM ports shared inside the VM settings. This makes me seek guidance on suitable virtual serial port solutions that allow controlling the host's COM port from the virtual machine.
It appears there are compatibility issues with certain versions. It functions in some VirtualBox versions but not others. More information can be found here: https://forums.virtualbox.org/viewtopic.php?f=4&t=92981. It seems to have worked in VirtualBox 5.x, though the exact version you're using might affect this. I'm not sure if it's necessary, but I saw instructions suggesting adding it via Control Panel or adding hardware first.
I was in your boat a couple of months ago. I ran my XP under hyperV, set up the serial port to communicate with a pipe, and linked a pipe-to-serial tool on the host. I don't remember the utility's name, but if you're interested, I can check it back.
The cable is fine since I understand that a newer software update can still connect to the devices.
Thank you for sharing the link. This doesn't appear to be the same problem because the software didn’t crash in my case; instead, communication fails (I’m unable or don’t know how to supply any usable details beyond this point, as I can only observe that the software attempts to connect but then fails).
What version am I using? I was at home recently, and the latest version was about a month ago. It could have been VirtualBox 6.1.22, 6.1.24 or 6.1.26.
I now realize that the changelog for version 6.1.24 indicates a regression bug (bug #18668), so I need to check what version I actually have installed when I return to work.
Thanks a lot for your assistance on this. I’ll check again once I’m back and see if it matches a version that should have this issue resolved.
Today I took a test where I upgraded Virtualbox to the latest version available. Still, the mentioned fix didn’t resolve the problem. At one point, when the baud rate was set to 19200, the software managed to connect to the device successfully—but that was just a rare occurrence, and I never repeated it again.
The current state is clear: communication functions properly on the host machine but fails entirely within Virtualbox.
I have to admit giving up on connecting the guest OS because:
1
In both the host operating system and the guest OS, I can access the device manager and tweak COM port settings—but I don’t find any information indicating which one takes precedence or if it truly matters. This uncertainty forces me to spend more time adjusting parameters repeatedly.
2
I experimented extensively with various COM port configurations. I’m aware that baud rates like 19200 and 115000 work fine, so I didn’t test other values.
I haven’t compiled a comprehensive list of all the settings tried, which means I can’t rule out the existence of a single optimal configuration. However, if I were to try many different combinations, it would likely take several weeks.
The software is extremely frustrating because each time I change settings, the interface and graphics behave in a misleading way. It creates the illusion of progress—just before connection, everything seems perfect—but then, seconds before the expected success, it abruptly fails with an error message.
All these steps consume a lot of time, so if I want to make changes, I should focus only on settings I truly think could help, like modifying the FIFO buffers in the COM port configuration.