Clarity on the GPU parameters

[cadop]

There is a list of attributes that basically restate what the name of the variable is when explaining it, but there is no info on what the values mean. For example -MaxPartitionDecode takes UInt64.

Using Get-VMGpuPartitionAdapter -VMName am-vgpu-03 the output is:

CurrentPartitionVRAM    : 1000000000
MinPartitionVRAM        : 1000
MaxPartitionVRAM        : 1100
OptimalPartitionVRAM    : 1000
CurrentPartitionEncode  : 1000000000
MinPartitionEncode      : 1000
MaxPartitionEncode      : 1100
OptimalPartitionEncode  : 1000
CurrentPartitionDecode  : 1000000000
MinPartitionDecode      : 1000
MaxPartitionDecode      : 1100
OptimalPartitionDecode  : 1000
CurrentPartitionCompute : 0
MinPartitionCompute     : 1000
MaxPartitionCompute     : 1100
OptimalPartitionCompute : 1000

But with a 24gb GPU, these values don't make sense. So does This is defined by the manufacturer's driver. mean "these values don't matter and will be overwritten by the driver anyway"?

I think it would be helpful to expand on the description, which just mentions that this sets things, but no notes about why the values wouldn't match expected values.

The 'Set-VMGpuPartitionAdapter' cmdlet assigns a partition of a GPU to a virtual machine. Running the command against a virtual machine assigns a full partition. Additional parameters exist to assign more specific options to a VM.

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: cf20deef-f3e5-89f9-7bc5-be643322df94
• Version Independent ID: 449f3adc-0b46-dfb3-40ff-408c9d569700
• Content: Set-VMGpuPartitionAdapter (Hyper-V)
• Content Source: docset/winserver2022-ps/hyper-v/Set-VMGpuPartitionAdapter.md
• Product: w10
• Technology: windows
• GitHub Login: @JasonGerend
• Microsoft Alias: jgerend

[officedocspr5]

To make it easier for you to submit feedback on articles on learn.microsoft.com, we're transitioning our feedback system from GitHub Issues to a new experience.

As part of the transition, this GitHub Issue will be moved to a private repository. We're moving Issues to another repository so we can continue working on Issues that were open at the time of the transition. When this Issue is moved, you'll no longer be able to access it.

If you want to provide additional information before this Issue is moved, please update this Issue before December 15th, 2023.

With the new experience, you no longer need to sign in to GitHub to enter and submit your feedback. Instead, you can choose directly on each article's page whether the article was helpful. Then you can then choose one or more reasons for your feedback and optionally provide additional context before you select Submit.

Here's what the new experience looks like.

Note: The new experience is being rolled out across learn.microsoft.com in phases. If you don't see the new experience on an article, please check back later.

First, select whether the article was helpful:

Then, choose at least one reason for your feedback and optionally provide additional details about your feedback:

Article was helpful	Article was unhelpful

Finally, select Submit and you're done!