Trying to launch a Spot NV12s_v3 in US East but not allowed even though I have enough quota

Question

Trying to launch a Spot NV12s_v3 in US East but not allowed even though I have enough quota

jmd 1

I'm a new customer and I'm trying to launch a win10 spot instance in US East but I'm unable to select the image I want (NV12_v3) - I get the following issue:

As you can see I've increased the quota to cope with the 12vCPUs required.

I'm not using any resources at all so I can't understand why I am unable to get the VM working. It would be great if you could help me understand what I'm doing wrong so that I can fix it myself in future.

Olga Os - MSFT 5,956 Reputation points Microsoft Employee

2021-04-20T01:13:55.2+00:00

Hello @jmd ,

I am following up with you regarding this incident and my escalation to the Product Group.

We apologize for the difficulties in deploying the Spot VM. It appears that the Azure portal has a defect that incorrectly applies a second quota limit to Spot deployments in some situations. We appreciate you bringing this to our attention.

While the repair is being made and rolled out, we suggest using the Spot VM API directly or generating an Azure Template and deploying that via the portal. Both methods should avoid the defect.

Your time and patience are greatly appreciated and again apologies on the inconvenience.

Sincerely,
Olga

4 answers

Your answer

Olga Os - MSFT 5,956 Reputation points Microsoft Employee

2021-04-20T01:13:55.2+00:00

Hello @jmd ,

I am following up with you regarding this incident and my escalation to the Product Group.

We apologize for the difficulties in deploying the Spot VM. It appears that the Azure portal has a defect that incorrectly applies a second quota limit to Spot deployments in some situations. We appreciate you bringing this to our attention.

While the repair is being made and rolled out, we suggest using the Spot VM API directly or generating an Azure Template and deploying that via the portal. Both methods should avoid the defect.

Your time and patience are greatly appreciated and again apologies on the inconvenience.

Sincerely,
Olga

Answer 1

shiva patpi 13,366 Microsoft Employee Moderator

Hello @jmd ,
Welcome to Azure . Basically SPOT instances requires an explicit quota request process where in the portal you have to choose SPOT option while submitting the request for quota increase , it's called as Low Priority Quota request.

Please see the steps mentioned here :

https://learn.microsoft.com/en-us/azure/azure-portal/supportability/low-priority-quota

Let us know if you have additional questions. If the above steps help you out in understanding , please make sure to "upvote and accept the answer"

jmd 1 Reputation point

2021-04-02T16:52:30.833+00:00

Thanks Shiva. I noticed that there are 2 types of vCPU quota so I made sure I requested an increase in Spot. This seems to be reflected in the notice I see in the screen grab I shared (24). What I don't understand is why would it say I have 10 vCPUs available when I am using no resources at all. How can I get the VM running...I believe I have the correct quota (for Spot instances) and yet it still isn't allowing me what do I need to check/do?
shiva patpi 13,366 Reputation points Microsoft Employee Moderator

2021-04-02T16:57:55.897+00:00

Hello @jmd ,
Can you quickly share me the subscriptionID , so that we can validate from our end ?
jmd 1 Reputation point

2021-04-02T17:46:17.79+00:00

xxxdf03c-xxxx-xxxx-xxxx-5c9516c0xxxx
Olga Os - MSFT 5,956 Reputation points Microsoft Employee

2021-04-02T18:31:44.02+00:00

Yes, I was right below about the Regional Core Limit for East US.
You have 10 there.

Resource Manager vCPU quotas for virtual machines and virtual machine scale sets are enforced at two tiers for each subscription, in each region.

The first tier is the Total Regional vCPUs limit (across all VM Series), and the second tier is the per VM Series vCPUs limit (such as the D-series vCPUs).
Steps to increase: https://learn.microsoft.com/en-us/azure/azure-portal/supportability/regional-quota-requests

You should also find the same information in the Azure Portal under the Usage +Quota => Total Regional vCPUs.
Example below:
jmd 1 Reputation point

2021-04-02T21:33:31.987+00:00

Thanks - I'm glad you were right. Sadly, trying to find the right line item to increase this quota is an absolute nightmare. It would have been helpful if while you were looking at my account (to prove you were right) that you also changed the quota so I could get on with some work. I've submitted another request hoping that I've selected the right quota type and I'll keep stumbling around until either I finally get lucky with this bizarre system that allocates quota without increasing the parent's quota so it's unusable or I give up and do something more productive, I realise it's complicated but the UX is incredibly painful for new Azure users like me.
Olga Os - MSFT 5,956 Reputation points Microsoft Employee

2021-04-02T22:15:34.073+00:00

I am really sorry about your experience there. I feel your pain. If I only could, I'd definitely increased the regional quota on your account :(

I am going to provide your valuable feedback internally to the Product Group.

PS: found your ticket and raised severity on it. Hope it will help to resolve the issue faster.
Olga Os - MSFT 5,956 Reputation points Microsoft Employee

2021-04-05T18:14:22.54+00:00

Hey @jmd . Sorry again for your experience there. I could see your request was approved and you have 24 regional cores available. Would you like to test the deployment one more time?

Answer 2

Most likely you have the core quota to deploy, however your subscription offer type is not currently supported.

Do you have any running Spot VM in your subscription? What is your offer type? What size are you trying to deploy?

If I am correct about the offer type limitation, the only real mitigation for this issue is to work with Azure Subscription Management (ASMS) team (cut ticket to the subscription management team) in an effort to get your subscription upgraded to the correct type.

The following VM sizes are not supported for Azure Spot Virtual Machines:

B-series
Promo versions of any size (like Dv2, NV, NC, H promo sizes)
Azure Spot Virtual Machines can be deployed to any region, except Microsoft Azure China 21Vianet.

The following offer types are currently supported:

Enterprise Agreement
Pay-as-you-go offer code (003P)
Sponsored (0036P and 0136P)
For Cloud Service Provider (CSP), contact your partner

Offers that are available for Spot:

Any offers with billingType == Modern
Azure_MS-AZR-0017P
Azure_MS-AZR-0148P
Azure_MS-AZR-0017G
Azure_MS-AZR-0148G
Azure_MS-AZR-0015P
Azure_MS-AZR-0016P
Azure_MS-AZR-USGOV-0015P
Azure_MS-AZR-USGOV-0017P
Azure_MS-AZR-USGOV-0017G
Azure_MS-AZR-0003P
Azure_MS-AZR-USGOV-0003P

Waiting for your response.

jmd 1 Reputation point

2021-04-02T18:02:43.01+00:00

Hi Olga,

I replied to the other answer you wrote and then deleted so I'll try again:

Do you have any running Spot VM in your subscription?

No

What is your offer type?

003P - Pay as you go

What size are you trying to deploy?

NV12s_v3

If you are correct that its a limitation of the offer wouldn't it say that somewhere rather than just say I haven't got enough spot quota?

Answer 3

Azure_MS-AZR-0003P is eligible for the Spot.

If you are correct wouldn't it say something somewhere about my offer type rather than simply stating that I don't have enough quota?

It should.

How much available Regional vCPUs cores do you have there? It might happen what your Total Regional limit is 10 cores.

Resource Manager vCPU quotas for virtual machines and virtual machine scale sets are enforced at two tiers for each subscription, in each region.

The first tier is the Total Regional vCPUs limit (across all VM Series), and the second tier is the per VM Series vCPUs limit (such as the D-series vCPUs). Any time a new VM is to be deployed, the sum of new and existing vCPUs usage for that VM Series must not exceed the vCPU quota approved for that particular VM Series. Further, the total new and existing vCPU count deployed across all VM Series should not exceed the Total Regional vCPUs quota approved for the subscription. If either of those quotas are exceeded, the VM deployment will not be allowed. You can request an increase of the vCPUs quota limit for the VM series from Azure portal. An increase in the VM Series quota automatically increases the Total Regional vCPUs limit by the same amount.

There is steps to request a quota increase by region:
https://learn.microsoft.com/en-us/azure/azure-portal/supportability/regional-quota-requests

Answer 4

In case anyone happens to be finding this page looking for a solution. Here's what happened to me:
Quotas do not bubble up so although I had been a given enough cpu quota for the image type I wanted to use, there were two more levels of quota that also needed to be in sync. To my extreme frustration Azure staff didn't seem to be able to fix this without multiple (6?) back and forths over email (including the gem of the support engineer "increasing the number of cpus to a total less than the amount of the increase). In my case the hierarchy of quotas was this:

total regional vcpu > total regional spot vcpu > image type vcpu

To add to the complexity there is some inconsistency in image and region naming.

When you try to launch an image that hits a quota issue the error isn't clear which of the links in the above chain is the problem (new users don't even know the chain exists!).

So, if like me you're looking for a way to do some 3D development in the cloud with an NVIDIA card (e.g. Unreal Engine) then I suggest you save yourself a lot of hassle and look elsewhere. In the end I got a custom Paperspace workstation up and running in roughly the same amount of time it took me to write the various emails and posts interacting with MS Azure.

Olga Os - MSFT 5,956 Reputation points Microsoft Employee

2021-04-06T23:55:20.12+00:00

Thank you again @jmd for sharing your feedback there.
I would feel the same in your situation and understand how it may upset. I assure you, this feedback already taken to the product group and in the triage state.
Please let me know how else I can help you.

Share via

Trying to launch a Spot NV12s_v3 in US East but not allowed even though I have enough quota

4 answers

Your answer