Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hugo docs: Fix {{site.baseurl}} links to use relative internal links instead #6255

Merged
merged 1 commit into from
Jan 28, 2025
Merged

Hugo docs: Fix {{site.baseurl}} links to use relative internal links instead #6255

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion doc/content/design/integrated-gpu-passthrough/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ Introduction
------------

Passthrough of discrete GPUs has been
[available since XenServer 6.0]({{site.baseurl}}/xapi/design/gpu-passthrough.html).
[available since XenServer 6.0](../gpu-passthrough.md).
With some extensions, we will also be able to support passthrough of integrated
GPUs.

Expand Down
8 changes: 4 additions & 4 deletions doc/content/toolstack/features/VGPU/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -89,7 +89,7 @@ hardware and config files present in dom0. They exist in the pool database, and
a primary key is used to avoid duplication. In XenServer 6.x the tuple of
`(vendor_name, model_name)` was used as the primary key, however this was not
ideal as these values are subject to change. XenServer 7.0 switched to a
[new primary key]({{site.baseurl}}/xapi/futures/vgpu-type-identifiers.html)
[new primary key](../../../design/vgpu-type-identifiers)
generated from static metadata, falling back to the old method for backwards
compatibility.

Expand All @@ -109,12 +109,12 @@ on PGPUs.

In XenServer 6.x, all VGPU config was added to the VM's `platform` field at
startup, and this information was used by xenopsd to start the display emulator.
See the relevant code [here][5].
See the relevant code in [ocaml/xapi/vgpuops.ml][5].

In XenServer 7.0, to facilitate support of VGPU on Intel hardware in parallel
with the existing NVIDIA support, VGPUs were made first-class objects in the
xapi-xenopsd interface. The interface is described
[here]({{site.baseurl}}/features/futures/gpu-support-evolution.html).
xapi-xenopsd interface. The interface is described in the design document on
the [GPU support evolution](../../../design/gpu-support-evolution).

## VM startup

Expand Down
Loading