Contents

Using Serial Ports

The following sections describe how to use serial ports with VMware GSX Server:

A VMware GSX Server virtual machine can use up to four virtual serial ports. The virtual serial ports can be configured in several ways.

You can also select whether to connect the virtual serial port when you power on the virtual machine.

Note: The serial port implementation is new in this release and deprecates the use of TTY type of virtual serial ports in a virtual machine.

Using a Serial Port on the Host Computer

You can set up the virtual serial port in a virtual machine to use a physical serial port on the host computer. This is useful, for example, if you want to use an external modem or a hand-held device in your virtual machine.

To install a virtual serial port that connects to a physical serial port on the host computer, take the following steps:

  1. Open the Configuration Editor (Settings > Configuration Editor).

  2. Select one of the virtual serial ports (COM1 through COM4).

  3. Choose Device from the Type pull-down menu.

  4. In the Path field, enter the path to the device you want to connect to the virtual serial port, for example, /dev/ttyS0 to use the first serial port on the host computer.

    Note: If you are connecting with a Linux remote console to add a physical serial port to a virtual machine on a Windows host, be sure to specify a Windows device name here, such as COM1.

  5. Click Install.

  6. Click OK to save your configuration and close the Configuration Editor.

  7. Power on the virtual machine.

Using a File on the Host Computer

You can set up the virtual serial port in a virtual machine to send its output to a file on the host computer. This is useful, for example, if you want to capture the data a program running in the virtual machine sends to the virtual serial port or if you need a quick way to transfer a file from the guest to the host.

To install a virtual serial port that connects to a file on the host computer, take the following steps:

  1. Open the Configuration Editor (Settings > Configuration Editor).

  2. Select one of the virtual serial ports (COM1 through COM4).

  3. Choose File from the Type pull-down menu.

  4. In the Path field, enter the path to the file on the host computer that you want to use to store the output of the virtual serial port.

  5. Click Install.

  6. Click OK to save your configuration and close the Configuration Editor.

  7. Power on the virtual machine.

Connecting an Application on the Host to a Virtual Machine

You can set up the virtual serial port in a virtual machine to connect to an application on the host computer. This is useful, for example, if you want to use an application on the host to capture debugging information sent from the virtual machine’s serial port.

To install a direct serial connection between an application on the host and a virtual machine, take the following steps:

  1. Open the Configuration Editor (Settings > Configuration Editor).

  2. Select one of the virtual serial ports (COM1 through COM4).

  3. Choose Pipe from the Type pull-down menu.

  4. In the Path field, enter /tmp/<pipe> as the name of the pipe.

  5. Select Server or Client. In general, select Server if you plan to start this end of the connection first.

  6. Click Install.

  7. Click OK to save your configuration and close the Configuration Editor.

  8. On your host computer, configure the application that communicates with the virtual machine to use the same pipe name.

  9. Power on the virtual machine.

Connecting Two Virtual Machines

You can set up the virtual serial ports in two virtual machines to connect to each other. This is useful, for example, if you want to use an application in one virtual machine to capture debugging information sent from the other virtual machine’s serial port.

To install a direct serial connection between two virtual machines (a server and a client), take the following steps:

In the server virtual machine

  1. Open the Configuration Editor (Settings > Configuration Editor).

  2. Select one of the virtual serial ports (COM1 through COM4).

  3. Choose a type of Pipe from the pull-down menu.

  4. In the Path field, enter /tmp/<pipe> as the name of the pipe.

  5. Select Server.

  6. Click Install.

  7. Click OK to save your configuration and close the Configuration Editor.

In the client virtual machine

  1. Open the Configuration Editor (Settings > Configuration Editor).

  2. Select one of the virtual serial ports (COM1 through COM4).

  3. Choose a type of Pipe from the pull-down menu.

  4. In the Path field, enter /tmp/<pipe> as the name of the pipe. The pipe name must be the same on server and client.

  5. Select Client.

  6. Click Install.

  7. Click OK to save your configuration and close the Configuration Editor.

Special Configuration Options for Advanced Users

Two special configuration options are available for serial connections between a virtual machine and the host or between two virtual machines. These options are of interest primarily to developers who are using debugging tools that communicate over a serial connection.

In one case, you activate the option by using a text editor to add the specified line to the configuration file of the affected virtual machine. The other option is set in the Configuration Editor.

Improving CPU Performance when Debugging

The second option must be set in the Configuration Editor. It is useful when the serial port is being used by the guest operating system in polled mode as opposed to interrupt mode. Polled mode causes the virtual machine to consume a disproportionate share of CPU time. This makes the host and other guests run sluggishly.

To restore performance for the host and other guests, in the Configuration Editor, select the serial port, and check the Yield CPU on poll check box. This configuration option forces the affected virtual machine to yield processor time if the only thing it is trying to do is poll the serial port.

Changing the Speed of the Serial Connection

The first option — serial<n>.pipe.charTimePercent = <x> — is useful to squeeze every possible bit of speed from your serial connection over a pipe. Add this line to your virtual machine’s configuration file.

<n> is the number of the serial port, starting from 0. So the first serial port is serial0. <x> is any positive integer. It specifies the time taken to transmit a character, expressed as a percentage of the default speed set for the serial port in the guest operating system. For example, a setting of 200 forces the port to take twice as long per character, or send data at half the default speed. A setting of 50 forces the port to take only half as long per character, or send data at twice the default speed.

You should first use the guest operating system to configure the serial port for the highest setting supported by the application you are running in the virtual machine.

Once the serial port speed is set appropriately in the guest operating system, experiment with this setting. Start with a value of 100 and gradually decrease it until you find the highest speed at which your connection works reliably.

Usage Scenarios: Debugging Over a Virtual Serial Port

You can use Debugging Tools for Windows (WinDbg) or Kernel Debugger (KD) to debug kernel code in a virtual machine over a virtual serial port. You can download Debugging Tools for Windows from the Windows DDK Web site at http://www.microsoft.com/ddk.

The following two examples illustrate how to use a virtual serial port to debug kernel code in a virtual machine:

Using either of these methods lets you debug kernel code on one system, without the need for two physical computers, a modem or serial cable.

Debugging an Application in a Virtual Machine from the Windows Host

In this situation, you have kernel code to debug in a virtual machine (called the target virtual machine) and are running WinDbg or KD on your Windows host.

To prepare the target virtual machine, follow the steps for a Windows host in Connecting an Application on the Host to a Virtual Machine. Make sure you configure the virtual machine’s virtual serial port as follows:

To prepare the host, make sure you have downloaded the correct version of Debugging Tools for Windows. You need version 4.0.18.0, dated December 21, 2001, as it supports debugging over a pipe.

Note: Pipe support is not documented in the WinDbg and KD in-product help or on Microsoft's Web site.

When you are ready to begin, complete the following steps:

  1. Power on the virtual machine.

  2. Check to make sure the serial port is connected. On the Devices menu, serial<n> should say Connecting…, as it is waiting to connect to the host on the other end of the pipe.

    Note: If the serial<n> says (Not connected), then the serial port may not be connected. Choose the virtual serial port, then Connect.

  3. On the host, open a Command Prompt window and do one of the following:

    Then press Enter to start debugging.

Debugging an Application in a Virtual Machine from another Virtual Machine

In this situation, you have kernel code to debug in a virtual machine (called the target virtual machine) and are running Debugging Tools for Windows (WinDbg) or Kernel Debugger (KD) in another virtual machine (called the debugger virtual machine) on the same host.

This is useful if you are running VMware GSX Server on a Linux host. The debugger virtual machine must be running Debugging Tools for Windows (WinDbg) or Kernel Debugger (KD) in a Windows guest operating system.

To prepare the target virtual machine, follow the steps for the server virtual machine for the appropriate host in Connecting Two Virtual Machines. Make sure when you configure the target virtual machine’s virtual serial port that you select the Yield CPU on poll check box, as the kernel in the target virtual machine uses the virtual serial port in polled mode, not interrupt mode.

To prepare the debugger virtual machine, make sure you have downloaded Debugging Tools for Windows. Then follow the steps for the client virtual machine in Connecting Two Virtual Machines.

When you are ready to begin, complete the following steps:

  1. Power on both virtual machines.

  2. Check to make sure the serial port is connected in each virtual machine. On the Devices menu, serial<n> should say /tmp/<pipe>.

    If the serial<n> says (Not connected), then the serial port may not be connected. Choose the virtual serial port, then Connect.

  3. In the debugger virtual machine, start debugging with WinDbg or KD normally.

Back to top

© 2001-2002 VMware, Inc. All rights reserved.