> 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/es/2025-o-anterior.md).

# 2025 o anterior

- [4.13](https://docs.verge.io/release-notes/es/2025-o-anterior/4-13-release-notes.md): Notas de la versión de la serie VergeOS 4.13: paso directo de hardware (USB/PCI/SRIOV), migración en vivo experimental de vGPU, bonding mejorado con detección de split brain, vSAN multipath y mejoras de HA.
- [4.12](https://docs.verge.io/release-notes/es/2025-o-anterior/4-12-release-notes.md): Notas de la versión de la serie VergeOS 4.12: interfaz de usuario en modo oscuro, autenticación de dos factores TOTP, virtualización anidada con migración en vivo, licencias sin conexión, migraciones de red más rápidas y caché meta de vSAN.
- [4.11](https://docs.verge.io/release-notes/es/2025-o-anterior/4-11-release-notes.md): Notas de la versión de la serie VergeOS 4.11: Site Manager para administración global, Recipe Marketplace, autenticación OIDC, exportación de VM, compatibilidad con TPM y mejoras de rendimiento en red y vSAN.
- [4.10](https://docs.verge.io/release-notes/es/2025-o-anterior/4-10-release-notes.md): Notas de la versión de la serie VergeOS 4.10: compatibilidad con NVIDIA vGPU, gestión de estados C de la CPU, rendimiento mejorado de vSAN, fijación de CPU y mejor paso directo y migración en vivo de GPU.
- [4.9](https://docs.verge.io/release-notes/es/2025-o-anterior/4-9-release-notes.md): Notas de la versión de la serie VergeOS 4.9, con una revisión completa de la interfaz de usuario, autenticación de dos factores basada en correo electrónico, paso directo de GPU, mirroring de puertos y mejoras en la gestión de instantáneas y 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/es/2025-o-anterior.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.