> 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-optical-drive.md).

# Virtual Optical Drive

### Adding an Optical Drive

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

**--device-add cdrom** \[**--image** <*name*>] \[**--iface** <**ide** | **scsi** | **sata**>] \[**--position** <*n*>]

\[**--subtype** <**buslogic** | **lsi-spi** | **lsi-sas**>]

### Modifying an Optical Drive

**--device-set** <*drive\_name*> \[**--image** <*name*>] \[**--iface** <**ide** | **scsi** | **sata**>]

\[**--position** <*n*>] \[**--subtype** <**buslogic** | **lsi-spi** | **lsi-sas**>]

#### Parameters

*drive\_name*: The name of the optical drive to modify (**--device-set** command onl&#x79;**)**. To obtain the list of the available drives, use the `prlctl list --info` command.

**--image**: connect the specified image file to the virtual machine. The following image file formats are supported: **iso**, **cue**, **ccd**, **dmg**.

**--iface**: virtual optical interface type: **ide**, **scsi**, **sata**.

**--position**: the SCSI / IDE / SATA device identifier to be used for the optical drive. Allowed ranges:

* 0-3 for IDE disk drives
* 0-6 for SCSI disk drives
* 0-5 for SATA disk drives

**--subtype**: virtual optical drive subtype: **buslogic**, **lsi-spi**, **lsi-sas**.


---

# 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-optical-drive.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.