VirtualBox COM port configuration
In this scenario, the VirtualBox can be configured to create the local domain socket non-Windows hosts, the named pipe, or itself, etc. Also, the VirtualBox must assume that the socket or pipe is in existence already.
In the case of a direct connection between two virtual machines, configure one virtual machine to develop a socket or pipe and the other one to attach to it.
Raw File: The virtual serial port output can be sent to a file. This is helpful for collecting diagnostic output. Any file can be used. The only requirement is that VirtualBox users has enough privileges to write and create.
TCP Socket: This helps forward serial traffic over TCP/IP. It can act as a TCP client that connects to servers or a server itself. The option allows for the direct connection between the remote machine and the guest's serial port via TCP.
- TCP Server: The current Pipe/Socket checkbox needs to be deselected and the port number specified in the address/path field. The port number can be 23 or 2023. In the case of UNIX-like systems, the port number has to be more than 1024.
- TCP Client: For the purpose of creating virtual null-modem cable over the LAN/Internet, the other end should connect via TCP, while specifying the hostname: port in the Path/Address field. When the "Connect to Existing Pipe/Socket" box is ticked, the TCP socket will go into client mode.
As you can see, 4 serial ports can be configured or each virtual machine. However, multiple port numbers can be picked.
