> 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/general-virtual-machine-management/clone-a-virtual-machine.md).

# Clone a Virtual Machine

**prlctl clone** <*vm\_id* | *vm\_name*> **--name** <*new\_name*>

Clones (makes an exact copy of) a specified virtual machine. The **-name** <*new\_name*> parameter specifies a name to give to the new virtual machine.

#### Optional Parameters

**--template**

Make the new virtual machine a template.

**--dst**

Set the path to the directory where the virtual machine files will be stored. If omitted, the default location will be used.

**--regenerate-src-uuid**

Regenerate the virtual machine source ID (the SMBIOS product ID will also be changed).

**--linked**

Create a linked clone.

**-i**, **--id** <*snapid*>

Create a linked clone based on a snapshot with a given *snapid*.

To check a virtual machine for linked clones, use the **prlctl list -i** command and look under the **Linked Clones** section.&#x20;

**--detach-external-hdd** <**yes** | **no**>

Specifies what to do with hard disks located outside the source virtual machine file. If you specify **yes**, outside hard disks will be removed from the destination VM. If you specify **no**, outside hard disks will remain in the new VM. Please note that in either case, the outside hard disks will NOT be copied to the destination.


---

# 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/general-virtual-machine-management/clone-a-virtual-machine.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.