A "sleep" state of VM which is cost wise similar to stop state. The VM wakes up and continues the previous session without rebooting OS.
It is a great feature of Azure to stop costs if the VM is stopped. But shutdown the VM needs close all the running programs and applications in the current session. It will be great if the VM can have a sleep mode which can stop all the costs (or partially). So users can quickly resume the work in the new session without restarting the VM.
Anonymous
shared this idea
Great feature request. Let us go take a look at what this would take to build.
18 comments
-
Rajesh Mag
commented
Any way to persist and restore to same memory state is fine, like Hibernate/Sleep.
-
Kuntal Mehta
commented
Please include that ASAP. It is must have and highly recommended feature and would make many developer's life easy who uses Azure as dev environment.
-
Kalman
commented
-
Kalman
commented
Azure, where is this feature? I have seen this request since 2013 and there are no good answers. Meanwhile, AWS and GCP offer this feature.
-
Eric van der Voort
commented
Just wondering if this feature request is still under review....
-
Andrei Lefter
commented
That will happen like never. Next thing lets do it for free :))
-
Mike PB
commented
Is this a duplicate of https://feedback.azure.com/forums/216843-virtual-machines/suggestions/13914840-ability-to-hibernate-vms-to-support-devtest-workfl#comments ? I have voted and commented there, but this feature is essential for migrating a developer machine to Azure.
-
Anonymous
commented
This would be beneficial for our Dev team, as we currently stop VM's on weekends when they are not in use, but it does require 15-45 minutes to get all our tools up running and open to where we were again on Monday morning.
Would be massively helpful to just come in with everything where it was pre-sleep.
-
André Melancia [MCT] commented
All you need to do is allow hibernation in the system firmware for the VM, which should never have been disallowed in the first place.
-
Bill
commented
This is the only reason all of my development machines are still at Cloudshare. If Azure would put this feature in then we would switch.
-
Paul
commented
"Hibernate and deallocate" - I like the idea! In fact, I think resource allocation to stopped and hibernated servers should be optional on a per-VM basis, not mandatory. I've been burned by stopped/allocated machines, thinking I was not being charged, and it leaves a sour taste in the mouth...
-
Anonymous
commented
without that feature, how should a SharePoint developer work? Restart the machine every morning, then starting Visual Studio? It takes 10 minutes.
-
Amethyste
commented
Why not an integrated shutdown feature as well?
I would like to be able to flag a VM to a scheduler with a build-in task that shutdown/startup automatically the VMThis is a very common and generic task and so it's a shame to have to write a specific task just for that
-
R. Lawson
commented
Agree with this feature 1000% I want to get all developers on VMs in Azure. If they are billing clients, the cost is worth it. But if the VM is idle over half the time after hours - which it will be - we are paying twice the cost.
There are what I consider hacks to shut down on idle, but the hacks are intrusive, difficult for an administrator to setup, and not always reliable.
Please make this simple!
-
che
commented
For me the main issue is the speed at which I can take a sleeping or stopped VM and have it up and running and taking requests. If sleep lets me cut that time down to just a few seconds then it would be extremely valuable.
-
Akash
commented
Essentially Hibernate and deallocate
-
Daniel Z
commented
-
Sean Feldman
commented
We already do something similar with Azure automation, having a schedule to shut VM down and bring it up. Having a Sleep feature would make it much simpler (and better).