# Data Object - VirtualSerialPortPipeBackingOption(vim.vm.device.VirtualSerialPortOption.PipeBackingOption)

Extends
  VirtualDevicePipeBackingOption
See also
  BoolOption, ChoiceOption

## Data Object Description

The `VirtualSerialPortPipeBackingOption` data object contains the options for backing a serial port device with a pipe to another process.

Properties

Name | Type | Description
--- | --- | ---
endpoint | ChoiceOption | Indicates the choices available and the default setting for the pipe endpoint. As an endpoint, the virtual machine can act as a client or a server.
noRxLoss | BoolOption | Indicates whether the server supports optimized data transfer over the pipe and also specifies default behavior. When this feature is supported and enabled, the server buffers data to prevent data overrun. This allows the virtual machine to read all of the data transferred over the pipe with no data loss. If optimized data transfer is supported (`noRxLoss.supported` is `true`): You can enable (or disable) the feature explicitly by setting the `noRxLoss` property on the pipe backing information object. If you do not set the `noRxLoss` property on the the pipe backing information object, the server enables optimized data transfer if the `noRxLoss.defaultValue` property on the pipe backing options object is `true`. If `noRxLoss.supported` is `false`, the server ignores the optimization settings. Note: You can use this feature even if the other end of the pipe is not an application, but it is more likely to fail.
Properties inherited from VirtualDevicePipeBackingOption
None
Properties inherited from VirtualDeviceBackingOption
type
Properties inherited from DynamicData
None

Show WSDL type definition
<complexType xmlns="http://www.w3.org/2001/XMLSchema" xmlns:sms="urn:sms" name="VirtualSerialPortPipeBackingOption"> <complexContent> <extension base="sms:VirtualDevicePipeBackingOption"> <sequence> <element name="endpoint" type="sms:ChoiceOption"/> <element name="noRxLoss" type="sms:BoolOption"/> </sequence> </extension> </complexContent> </complexType>