> 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/release-notes/zh/2025-nian-huo-geng-zao.md).

# 2025 年或更早

- [4.13](https://docs.verge.io/release-notes/zh/2025-nian-huo-geng-zao/4-13-release-notes.md): VergeOS 4.13 系列的发行说明：硬件直通（USB/PCI/SRIOV）、实验性 vGPU 热迁移、带有脑裂检测的增强绑定、多路径 vSAN，以及 HA 改进。
- [4.12](https://docs.verge.io/release-notes/zh/2025-nian-huo-geng-zao/4-12-release-notes.md): VergeOS 4.12 系列的发行说明：深色模式 UI、TOTP 双因素身份验证、支持热迁移的嵌套虚拟化、离线许可、更快的网络迁移，以及 vSAN 元缓存。
- [4.11](https://docs.verge.io/release-notes/zh/2025-nian-huo-geng-zao/4-11-release-notes.md): VergeOS 4.11 系列的发行说明：用于全局管理的站点管理器、配方市场、OIDC 身份验证、虚拟机导出、TPM 支持，以及网络和 vSAN 性能改进。
- [4.10](https://docs.verge.io/release-notes/zh/2025-nian-huo-geng-zao/4-10-release-notes.md): VergeOS 4.10 系列的发行说明：NVIDIA vGPU 支持、CPU C-States 管理、增强的 vSAN 性能、CPU 绑定，以及改进的 GPU 直通和热迁移。
- [4.9](https://docs.verge.io/release-notes/zh/2025-nian-huo-geng-zao/4-9-release-notes.md): VergeOS 4.9 系列的发行说明，包含全面的 UI 改版、基于电子邮件的双因素身份验证、GPU 直通、端口镜像，以及增强的快照和 NAS 管理。


---

# 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/release-notes/zh/2025-nian-huo-geng-zao.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.