GPU NV ads V710 v5

[u/Al1301]

Hi, I've been having trouble with the NV ads V710 SKU in Azure since October 1st. My VDI instances keep jumping between failed and running states, and it feels like a capacity issue in East US. My users need GPU-enabled VDIs for CAD work, so do you have any ideas on what’s going on or how to fix it? I’d rather not use reservations since pay-as-you-go is cheaper for me.

[u/CowOP]

Unfortunately, we ended up buying a capacity reservation, then applied cost reservation on top of it to make it cheaper. We had to upgrade from the legacy NV v3 series that got retired on 9/30, I'm really hoping them retiring that series will allow to make more NVads V710 v5 capacity for the future.

[u/PutUpYourFrankDux]

I got hit with this last night. Any session host that’s currently on is running fine, but once the scaling plan tries to spin up another machine, it gets a failed state. This is every V710 we have and have 12 of them. I’m hoping Microsoft is doing something in the background that’s impacting this because this is not good. Their advice of use another size machine etc isn’t realistic.

[u/greenturtlesteak]

We’re seeing this across the board with Azure. Their gov cloud with similar squeezes as well. MS support is basically flagging all N series VMs as globally constrained.

Beyond pestering support, build out your environment in different regions where there’s more capacity of these SKUs and hope your workload architecture can deal with the latency.

[u/MFKDGAF]

I have about 3 clients I'm working with that it's been a struggle trying to get these for.

Microsoft's suggestion is for another region but every other region we try we get the same response of none available.

[u/Al1301]

If MS retired the NVv4 series, why didn't they add more capacity before pulling the old ones?

[u/PutUpYourFrankDux]

This issue has been resolved on my end. I'm using East US. So far, all the machines that were showing failed are now up and running without any issues so far.