VM fails to start with available Capacity Reservation

Ben-8350 26

I have VMs of size E4adsv5 deployed in South Central assigned to a Capacity Reservation. Last week I went to restart one of these VMs from the Windows O.S. and when it failed to come back up, I checked status in Azure Portal and it was in a Stopped (de allocated) state which should not happen when restarting at the guest OS level.

When I went to start it from Azure Portal, it fails with an internal error. I then attempted to spin up a new VM of the same series against an available capacity reservation and get, “failed to start vm, allocation failed, we don’t have sufficient capacity for VM size in this region”.

I purchased "Capacity Reservations" to guarantee resource availability for my VMs after learning the hard way a "Reserved Instance" isn't really a reserved instance.

If anyone can help me resolve this, I'd appreciate it. Microsoft?

Sai Krishna Katakam 690 Reputation points Microsoft Vendor

2024-10-16T03:28:51.2066667+00:00
Hi Ben-8350,

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

It seems the issue you're encountering is related to how Capacity Reservations function during a VM restart. Even with Capacity Reservations, there can be instances where the specific VM size you need isn’t available in the region due to high demand. This can result in allocation failures when trying to start or restart VMs. Make sure that your subscription has the necessary quota for the VM size and region. Sometimes, quota limitations can prevent VMs from starting, even if capacity reservations are in place.

Here are some steps you can take to troubleshoot to resolve the issue:

Verify that your subscription has sufficient quota for the VM size in the South-Central region. You can request a quota increase if needed.

Sometimes, retrying the operation after a few minutes can resolve transient issues.

For more detailed information, please refer to the following documentation:
Troubleshooting Capacity Reservation Issues
On-demand Capacity Reservation Overview
Troubleshooting Azure VM Allocation Failures

If you have any further queries, do let us know. If the comment is helpful, please click "Upvote".
Ben-8350 26 Reputation points

2024-10-16T20:50:17.1966667+00:00
Thanks for your response.

Verify that your subscription has sufficient quota for the VM size in the South-Central region. You can request a quota increase if needed.

Quota is not an issue. I'm only using 12 of 50.

Sometimes, retrying the operation after a few minutes can resolve transient issues.

This issue started 7 days ago on 10/9/2024. Have tried several times daily since then without success.

Can you explain to me what the point of a capacity reservation is? Reading this document, it states, "capacity is reserved for your use and is ALWAYS available within the scope of applicable service-level agreements (SLAs)"

https://learn.microsoft.com/en-us/azure/virtual-machines/capacity-reservation-overview#benefits-of-capacity-reservation

1 answer

TP 97,996 Reputation points

2024-10-17T22:20:21.43+00:00

Hi Ben,

You need to open a support case to get this resolved. Since you have capacity reservation it should not be failing due to lack of capacity. That's the whole point of capacity reservation. You are entitled to SLA credits based on your description.

Unfortunately, you need to have at minimum Developer level support ($29/month) in order to open technical support case, and Developer only allows Severity C cases via email. Standard level ($100/month) is recommended minimum for Production since it allows Severity A/B/C via phone/email.

Whether you choose Developer or Standard you could cancel it later so that you only pay for one month. You can use below link if you need to upgrade your support plan:

https://portal.azure.com/#view/Microsoft_Azure_Support/SupportPlansBlade/subscriptionId/

It can be tricky to open a support case so please add a comment below if run into a problem.

Please click Accept Answer and upvote if the above was helpful.

Thanks.

-TP
Please sign in to rate this answer.
Ben-8350 26 Reputation points

2024-10-17T23:35:31.7333333+00:00

Thanks for the reply. I’ve actually had a case open for nine days now with Microsoft Support and still unresolved. I posed the question here out of desperation hoping Microsoft would get it escalated and to try another support channel.

TP 97,996 Reputation points

2024-10-18T00:18:22.21+00:00

Thanks for the reply. I’ve actually had a case open for nine days now with Microsoft Support and still unresolved. I posed the question here out of desperation hoping Microsoft would get it escalated and to try another support channel.

Wow, okay. Have you tried deploying into different zones, one at a time? I just did test and I was able to deploy E4adsv5 in South Central US Zone 1 and Zone 3, but not in Zone 2. Tried multiple times in Zone 2 and it failed every time, whereas it succeeded first try for Zones 1/3.NOTE: The above are logical zones and will most likely not match your zones. For example, my "Zone 2" might actually be "Zone 3" for your subscription.

If you can get it to succeed in one of the zones with a "vanilla" test VM then you could work on making a copy of your failed VM's disks and create VM in that zone.

Ben-8350 26 Reputation points

2024-10-18T00:37:08.2+00:00

Thank you for your response. I have not targeted different zones. I did attempt reapply and redeploy several times without success. Adding to this mess, earlier today for the first time in eight days or so, I was able to start that series Vm with a test one, but not when it was assigned to my available capacity reservation. If it was applied to the reservation and I tried to start it would fail with “internal error”.

TP 97,996 Reputation points

2024-10-18T00:48:56.56+00:00

You are welcome. I was hoping to get your VM up and running using whatever method and then perhaps you could "fight" them for SLA credits/refund of your capacity reservation. Not the best solution but at least your VM would be running.

Ultimately support needs to fix this for you or at a bare minimum, acknowledge that your capacity reservation is failed at this point due to some issue or extreme lack of availability for that size.

Sai Krishna Katakam 690 Reputation points Microsoft Vendor

2024-11-07T09:25:47.66+00:00

Hi Ben-8350

Could you please confirm whether this issue is resolved? If you found the information useful, please click "Accept Answer" and "Upvote" on the post to let us know.

Thank you.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

VM fails to start with available Capacity Reservation

1 answer

Your answer