Naturally, I’m running 64-bit Windows 2008, and there doesn’t appear to be a version compiled for 64-bit Windows, so I had to compile my own. The idea is to make a COM port on the host available via TCP/IP, and then attach to it via the guest, then make this process automatic.įirst, on the guest, you’ll need an appropriate version of hub4com, and the batch file bundled with it, com2tcp-rfc2217.bat. What follows is a recipe to access the physical COM ports on the host from a guest using com0com, and its related utilities. “Note: No access to a physical COM port is available from a virtual machine.” The Hyper-V Deployment guide contains little more than this: (It appears that this option is used primarily for debugging programs, rather than for using actual serial ports - it doesn’t appear to have been intended to be used to provide actual serial port access from the guest.) Perversely, there are settings to connect the guest COM ports to “named pipes,” but there’s no way on the host to connect COM ports to named pipes. Unlike many other virtualization solutions, it’s not particularly easy to connect a Windows 2008 Hyper-V guest to its host serial ports.
0 kommentar(er)
