This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(185.6, 39%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I want to assign GPUs to VMs created with Hyper-V in my Windows Server 2022 using GPU pool .
I have NVIDIA GPU Tesla M60 plugged into Windows Server 2022, and create GPU Pool .
After I selected a pool from the GPU pool and assigned it to a highly available virtual machine, the virtual machine failed to start, with a prompt indicating that multiple devices had been allocated to the virtual machine.
However, if I assigned this pool to a non-highly available virtual machine on the host, it could start normally. May I ask if there are any special settings for highly available allocation?
Thank you.
Could it be a bug in Windows Admin Center 2311 ?
Are there any other ways or instructions for configuring high-availability GPUs?
This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(92.8, 73%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAL%3C/text%3E%3C/svg%3E)
Hi,
The issue may be caused by a GPU allocation conflict between highly available (HA) virtual machines. You can check the exclusive GPU allocation, HA compatibility or otherwise event logs.
You can check this link too :
Sincerely,
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(313.6, 55.00000000000001%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHL%3C/text%3E%3C/svg%3E)
Hello,
When assigning GPUs to a highly available VM, there are some additional considerations and configurations that need to be addressed to ensure that the HA feature does not interfere with the GPU allocation.
Here are a few things you might consider:
1、Ensure that the HA configuration allows for the specific allocation of hardware resources like GPUs. Sometimes, HA settings may prevent certain types of resource allocations to maintain failover readiness.
2、Make sure that the NVIDIA drivers and software components installed on the host server are compatible with the version of Windows Server 2022 you’re using and support the specific GPU model (Tesla M60). Additionally, check if there are any specific requirements or recommendations by NVIDIA for setting up GPU passthrough in a highly available environment.
3、Verify that the GPU passthrough settings are correctly configured both on the host and within the VM. This includes ensuring that the correct devices are being passed through and that the VM is configured to use these devices properly.
4、Review the VM’s settings to confirm that it is set up to receive and utilize the GPU resources. This includes checking the device assignment settings and ensuring that the VM is not configured in a way that conflicts with the HA requirements.
Best Regards,
Hania Lian
============================================
If the Answer is helpful, please click "Accept Answer" and upvote it.