3 Replies Latest reply on Feb 21, 2020 5:32 AM by AlessandroRomeo68

    How to configure VMs with Serial Ports to be vMotion compatible?

    GordonPM Novice

      We have two VMs which test for a physical environment:

       

      VM #1: Windows server with the analyzer controller software

      VM #2: Windows server with emulator for a physical analyzer.

       

      In the physical environment the software and analyzer are connected via serial ports, thus in order to test, these two VMs need to be connected via serial connections.

       

      I can get this to work fine by adding a serial port to each VM as follows:

       

      VM#1

      Serial Port 1: Use Named Pipe  Connected

      Status:          Connect At Power On

      Pipe:             /dev/ttys2

      Ner End:       Client

      Far End:       A Virtual Machine

      I/O mode:     Yield CPU on Poll

       

      VM#2

      Serial Port 1: Use Named Pipe  Connected

      Status:          Connect At Power On

      Pipe:             /dev/ttys2

      Ner End:       Server

      Far End:       A Virtual Machine

      I/O mode:     Yield CPU on Poll

       

      Minor issue: Both VMs have to be on the same ESX host in order for this to work

       

      My major issue and question is:

       

      Currently in order to Vmotion these VMs, they have to be turned off thus requiring downtime of the test system. Is there any way to set up serial ports between two VMs so that they are vMotion enabled? At present, because these VMs will not vMotion unless powered off this means that host patching of our environment can be delayed by weeks while a test period is in progress (this is a medical environment).


      Is there a way to configure this without something like a virtual serial port concentrator?