-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for DiskRP 2020-12-01 changes #17656
Labels
Comments
ghost
added
the
needs-triage
This is a new issue that needs to be triaged to the appropriate team.
label
Apr 12, 2021
yungezz
added
Compute
az vm/vmss/image/disk/snapshot
feature-request
Service Team Support Request
labels
Apr 14, 2021
ghost
removed
the
needs-triage
This is a new issue that needs to be triaged to the appropriate team.
label
Apr 14, 2021
We are planning it. |
this feature is not yet enabled for preview, so will need to remove this issue. Will create the issue again when the preview is announced. |
please disregard the above comment |
@meet1993shah
Is this feature available now? |
yes, it's available. |
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Resource Provider
Microsoft.Compute/DiskRP
Description of Feature or Work Requested
Feature - Support for Hibernating VMs (Persist supportsHibernation flag on managed disks)
IAAS VMs in Azure will support a new state: hibernation. From the fabric/CRP point of view, a hibernating VM is deallocated; however, before deallocation, the VM saves the memory state to the disk, thus allowing a fast restore to the initial state when the VM is restarted. To support this managed disks will persist a new boolean property called supportsHibernation which CRP can use to determine if the underlying disk has capability to support hibernation. This flag can be turned on / off by the customer.
We need the following changes:
Minimum API Version Required
2020-12-01
Swagger Link
Azure/azure-rest-api-specs#12796
Target Date
asap
The text was updated successfully, but these errors were encountered: