> 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/pdfm-ug/v20-zh-tw/parallels-desktop-for-mac-20-shi-yong-zhi-nan/jin-jie-zhu-ti/shi-yong-xu-ni-ji-qi/fu-zhi-xu-ni-ji-qi.md).
# 複製虛擬機器
如果您需要與虛擬機器完全相同的副本，可選擇複製方式。複製的虛擬機器是與原虛擬機器完全相同的獨立的實體。要複製虛擬機器：
1. 啟動 Parallels Desktop。
2. 在「**控制中心**」中，選擇您想要複製的虛擬機器 (必須關閉該虛擬機器) 並選擇「**檔案**」>「**複製**」。
3. 選擇您想要儲存複製的虛擬機器的位置。
預設情況下，Parallels Desktop 將複製的虛擬機器儲存在 `~/Parallels` 資料夾中。
4. 按一下「**儲存**」以開始複製虛擬機器。
### **建立虛擬機器的連結複製**
{% hint style="info" %}
**附註：**該功能僅可用於 Parallels Desktop for Mac Pro/Business 版。
{% endhint %}
連結複製是與父虛擬機器共用虛擬硬碟的虛擬機器。該技術能夠允許多個虛擬機器共用安裝在父虛擬機器硬碟上的軟體。這樣，使用者則可節省 Mac 硬碟上的空間。要建立連結複製：
1. 啟動 Parallels Desktop。
2. 在「**控制中心**」中，選擇您想要複製的虛擬機器 (必須關閉該虛擬機器) 並選擇「**檔案**」>「**新的連結複製**」。
3. 選擇您想要儲存複製的虛擬機器的位置。依預設，Parallels Desktop 會將連結複製儲存到原始虛擬機器所在的資料夾中。
4. 按一下「**儲存**」以開始複製虛擬機器。
### **取消虛擬機器的連結複製**
如果要將連結的複製轉移到其他地方，首先需要將其轉換為獨立電腦。若要執行這項作業，請前往 Parallels Desktop 控制中心，以滑鼠右鍵按一下連結的複製，並選取「**取消連結複製」選項。**
這會將連結的複製轉換為原始電腦的獨立且未連結的複製。
{% hint style="warning" %}
**附註**：與連結的複製不同，這個新的未連結複製會佔用自己的磁碟空間，佔用的空間與原始虛擬機器的大小大致相當。在進行此操作之前，請確保您擁有足夠的磁碟空間。
{% endhint %}
---
# 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/pdfm-ug/v20-zh-tw/parallels-desktop-for-mac-20-shi-yong-zhi-nan/jin-jie-zhu-ti/shi-yong-xu-ni-ji-qi/fu-zhi-xu-ni-ji-qi.md?ask=&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.
