Windows Server 2012r2 running Hyper-V with a WinXP 32-bit VM. There is a particular application that will only run on WinXP that uses a serial connector to interface with an old diesel governor.
I have researched on how to pipe COM ports between guest and host but I am either doing it wrong or I am not understanding the capabilities.
Among other resources:
https://charbelnemnom.com/2014/10/hyper-v-enhanced-session-mode-show-options-issue-hyperv/
Integration tools are installed Enhanced Mode is enabled for machine and users
On the host in powershell entered:
[System.IO.Directory]::GetFiles("\\.\\pipe\\")
and it returned with \\.\pipe\\COM3
for my USB to serial adapter. In Hyper-V on the XP guest I edited the COM1 Serial Port setting by selecting Named Pipe and in the pipe name field entered \COM3
this caused the Named pipe path: field to display \\.\pipe\\COM3
I then connected the serial cable to the port ran Putty on the guest as admin and nothing displays, there is no interaction. I ran Putty as admin on the host and I am able to connect.
I am convinced the issue is somewhere in the "piping" of the two interfaces but do not know how to troubleshoot further. I am not certain it makes a difference that the host connection is USB to serial and that is causing an issue integrating with the guest. Any help would be appreciated. I will be monitoring this thread closely so should be able to provide additional requested info in a timely manner.
Thank you in advance!