> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/parallels-desktop-developers-guide/command-line-interface-utility/manage-virtual-machines-from-cli/virtual-machine-configuration-tasks/device-management/virtual-serial-port.md).

# Virtual Serial Port

### Adding a Serial Port

{% hint style="info" %}
**Note**: Adding a Serial port is not supported in macOS virtual machines.
{% endhint %}

**--device-add serial** {**--device** <*name*>|**--output** <*file*>|**--socket** <*name*>

\[**--socket-mode** <**server**|**client**>]}

Modify a serial port

**--device-set** <*port\_name*> {**--device** <*name*>|**--output** <*file*>|**--socket** <*name*>

\[**--socket-mode** <**server**|**client**>]}

#### Parameters

*port\_name*: the name of the port to modify (**--device-set** command only). To obtain the list of the available ports, use the *prlctl list --info* command.

**--device**: the number of the host computer serial port that will be used by the virtual machine.

**--output**: the path to the file where the output of the virtual serial port will be sent.

**--socket**: the name of the host computer socket to which the serial port will be connected.

**--socket-mode**: the socket operation mode.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.parallels.com/landing/parallels-desktop-developers-guide/command-line-interface-utility/manage-virtual-machines-from-cli/virtual-machine-configuration-tasks/device-management/virtual-serial-port.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.