> 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/common-options.md).

# Common Options

The options described here are common for all types of devices.

**--device-connect** <*device\_name*>

Connects the specified device to a running virtual machine. The device can be of type fdd, cdrom, sound, or net. To obtain a device name, use the **prlctl list -i** command.

**--device-disconnect** <*device\_name*>

Disconnects the specified device from a running virtual machine.

**--device-set** <*device\_name*> <<**--enable** | **--disable**> | <**--connect** | **--disconnect**>>

Enables/disables or connects/disconnects the specified device to/from a virtual machine. Please note that the **--device-set** command is also used to modify a device configuration and has additional parameters, which are different for different types of devices. The parameters for each device type are described in subsequent sections of this guide.

**--device-del** <*device\_name*> \[**--detach-only** | **--destroy-image** | **--destroy-image-force**]

Removes the specified device from the virtual machine.

If **--detach-only** is specified and the device is a virtual hard disk drive, the disk image is preserved.

If **--destroy-image** is specified, the virtual HDD image is removed from the server.

If **--destroy-image-force** is specified, the virtual HDD image is removed from all snapshots and from the server.

The default action on deleting a virtual HDD is to detach the HDD image as if **--detach-only** was specified.


---

# 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/common-options.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.