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

jmd 1 Reputation point
2021-04-02T14:44:06.073+00:00

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:

84066-screenshot-2021-04-02-at-151445.png

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.

Azure Virtual Machines
Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
9,083 questions
{count} votes

4 answers

Sort by: Most helpful
  1. shiva patpi 13,366 Reputation points Microsoft Employee Moderator
    2021-04-02T16:40:02.257+00:00

    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 :

    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"


  2. Olga Os - MSFT 5,956 Reputation points Microsoft Employee
    2021-04-02T17:28:12.82+00:00

    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.


  3. Olga Os - MSFT 5,956 Reputation points Microsoft Employee
    2021-04-02T18:17:20.06+00:00

    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

    0 comments No comments

  4. jmd 1 Reputation point
    2021-04-06T09:58:14.043+00:00

    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.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.