> For the complete documentation index, see [llms.txt](https://docs.verge.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verge.io/knowledge-base/zh/storage-vsan/preferred-tier-usage.md).

# 首选层使用

解释当虚拟机磁盘的首选层设置为不存在的层时，VergeOS 如何确定使用哪个 vSAN 存储层，包括回退行为。

在 VergeOS 中创建或修改虚拟机（VM）磁盘驱动器时，用户可以设置一个 **首选层级**。在大多数情况下，这会保持为 **默认**，可在以下位置配置 **系统 > 系统设置 > 默认 VM 驱动器层级**。不过，当指定的层级不存在时，系统的行为可能出乎意料。以下是 VergeOS 在这种情况下如何确定使用哪个层级：

* **将首选层级设置为不存在的更高层级**:
  * 例如：如果用户选择 **第 3 层** ，而系统只有 **第 1 层** 以及 **第 4 层** 可用存储，系统将尝试选择下一个更高（更慢）的层级。在这种情况下，系统将默认使用 **第 4 层**.
* **将首选层级设置为不存在的更低层级**:
  * 例如：如果用户选择 **第 3 层** ，而系统只有 **第 1 层** 以及 **第 2 层** 存储，系统将选择下一个更低（更快）的层级。在这种情况下，系统将默认使用 **第 2 层**.

在这两种情况下，VergeOS 都会根据用户的偏好选择最接近的可用层级。

***

{% hint style="info" %}
**文档信息**

* 最后更新：2024-08-29
* vergeOS 版本：4.12.6
  {% 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.verge.io/knowledge-base/zh/storage-vsan/preferred-tier-usage.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.