With FlexiHub’s advanced functionality, you can create a virtual copy of a real serial port on any networked computer and then connect that COM port to the virtual machine’s guest OS via the network. After that, any serial device attached to the physical serial port will instantly show up in your VM’s guest system like it was connected to that virtual machine directly.
Above that, with FlexiHub you’ll have no trouble connecting to remote serial devices over all distances. This is particularly useful when you don’t have an opportunity to directly plug a device into your computer’s physical serial port. Thanks to the cutting-edge COM port virtualization technology, FlexiHub is ideal for COM port redirection to virtual machines all over the network.
How to redirect COM ports to virtual machines with FlexiHub - Video Guide
As FlexiHub works over the Internet, a COM port device’s physical location will make no matter at all. Once you install FlexiHub on the server machine with an attached serial device and the client computers, you’ll be able to connect virtual serial ports over IP and access COM devices in a virtual machine remotely.
The devices connected to the host’s serial ports will become accessible in a virtual machine. No further adjustments or setting configurations are required. You can manage serial ports from a virtual machine simply and conveniently. FlexiHub is compatible with all major virtualization software, including Hyper-V, VirtualBox, and VMWare.
Now let’s have a look at the Hyper-V native method of setting up COM to VM passthrough. Here is what you need to do to configure a COM port for a virtual machine Windows 10:
Note: The name must be unique so it’s a good idea to check if the name is already in use by running this command in the PowerShell terminal:
After that, you’ll see that pipe in the list of all named pipes that you currently use.
To see the list, run this command in a PowerShell terminal:
Now you can use the named pipe path to connect to Windows virtual machine COM ports on the Hyper-V host machine.
VirtualBox also has some built-in functionality you can use to access RS232 in virtual machines.
From the Settings tab or the VBox Manage command, you can configure the Port Mode and Port Number to create up to four virtual serial ports in each virtual machine. But to ensure compatibility with the guest OS, you’ll need to configure your virtual serial ports as a “standard UART device”.
This will allow you to send and receive serial data but the whole set-up process differs for each specific operating system and may require certain technical skills to perform.
For the detailed setup description, please check out this comprehensive guide: VirtualBox serial port passthrough →
In VMware, you can create up to 4 virtual interfaces for each VM that can be used to redirect data to physical serial ports, files, or named pipes.
You can try this method to access a serial modem or some other COM-based peripheral during your next VMware Workstation session. On top of that, with its help, you can send debugging data to the host or another virtual machine.
And here is a much more detailed guide on setting up VMware serial port passthrough →
It’s up to you to decide which of the methods described here is best suited for your specific situation, needs, and level of competence. But to make the right choice, please note that using a purpose-designed software application has many significant advantages compared to all the native methods.
First and foremost, FlexiHub has no limit of serial ports you can redirect to each of your virtual machines. On top of that, it’s a truly universal solution that works on every platform and is compatible with all popular virtualization environments. And, the cherry on top, you won’t need any technical training to use the app as FlexiHub has a very self-explanatory user interface.