Desired state configuration for virtual machines
Systems and methods for setting virtual machines (“VMs”) to desired configurations while the virtual machines are running. In some systems, a user can select a VM and a desired configuration. An agent can then set an attribute of the virtual machine to indicate that on guest operation system (“OS”) reboot of the VM, the VM will enter BIOS mode. The agent can also store the desired configuration in the database based on authenticating the user. When the VM reboots at a future time, the attribute can cause the VM to enter BIOS setup. The agent can be notified and can retrieve the desired configuration from a database using an identifier for the VM. Then the agent can apply the desired configuration to the VM during BIOS setup with a system process that does not require further user authentication.
1. A method for virtual machine state configuration, comprising:
receiving a desired configuration for future application to a virtual machine (“VM);
setting a flag of the VM to indicate the VM should enter BIOS setup on next boot, wherein an agent responsible for applying the desired configuration subscribes for notification of the VM entering BIOS mode;
based on a determination that the agent has not applied the desired configuration to the VM after the VM has entered the BIOS setup on the next boot, reapplying the flag setting of the VM; and
based on the agent receiving a notification that the VM has entered the BIOS setup on a subsequent boot, applying the desired configuration to the VM.
2. The method of claim 1 , wherein applying the desired configuration includes powering off the VM, modifying a definition file for the VM, and powering on the VM.
3. The method of claim 1 , wherein the agent fails to apply the desired configuration based on missing the notification as part of scheduled downtime to a desired state change service that utilizes the agent.
4. The method of claim 1 , wherein the agent fails to apply the desired configuration based on the agent crashing, and wherein the agent executes again prior to receiving the notification on the subsequent boot.
5. The method of claim 1 , wherein the agent fails to apply the desired configuration based on trigger criteria for the desired configuration being unmet.
6. The method of claim 5 , wherein the trigger criteria includes a date requirement for when the desired configuration can be applied.
7. The method of claim 1 , wherein the desired configuration includes changes to amounts of computer processing units and memory utilized by the VM.
8. A non-transitory, computer-readable medium including instructions for virtual machine state configuration, wherein the instructions are executed by a processor, causing the processor to perform stages comprising:
receiving a desired configuration for future application to a virtual machine (“VM”);
setting a flag of the VM to indicate the VM should enter BIOS setup on next boot, wherein an agent responsible for applying the desired configuration subscribes for notification of the VM entering BIOS mode;
based on a time expiring for the agent to apply the desired configuration, resetting the flag of the VM to cause the VM to enter the BIOS setup on a subsequent boot; and
when the VM enters the BIOS setup on the subsequent boot, powering off the VM, applying the desired configuration, and powering on the VM.
9. The non-transitory, computer-readable medium of claim 8 , wherein the agent is paused for a scheduled period, during which the time expires.
10. The non-transitory, computer-readable medium of claim 8 , the stages further comprising deleting the desired configuration after an expiration period.
11. The non-transitory, computer-readable medium of claim 8 , the stages further comprising rolling back the VM from the desired configuration to a prior configuration based on the time expiring.
12. The non-transitory, computer-readable medium of claim 8 , wherein the agent fails to apply the desired configuration based on trigger criteria for the desired configuration being unmet.
13. The non-transitory, computer-readable medium of claim 12 , wherein the trigger criteria includes a date requirement for when the desired configuration can be applied.
14. The non-transitory, computer-readable medium of claim 8 , wherein the desired configuration includes changing a number of computer processing units and memory size for the VM.
15. A system for virtual machine state configuration, comprising:
a non-transitory, computer-readable medium containing instructions; and
a processor that executes the instructions to perform stages comprising:
receiving a desired configuration for future application to a virtual machine (“VM”);
setting a flag of the VM to indicate the VM should enter BIOS setup on next boot, wherein an agent responsible for applying the desired configuration subscribes for notification of the VM entering BIOS mode;
when the agent fails to apply the desired configuration after the next boot, resetting the flag of the VM to cause the VM to enter the BIOS setup on a subsequent boot; and
when the VM enters the BIOS setup on the subsequent boot, powering off the VM, applying the desired configuration, and powering on the VM.
16. The system of claim 15 , wherein the agent is paused when the next boot occurs.
17. The system of claim 15 , the stages further comprising deleting the desired configuration after an expiration period.
18. The system of claim 15 , the stages further comprising rolling back the VM from the desired configuration to a prior configuration based on the time expiring.
19. The system of claim 15 , wherein the agent fails to apply the desired configuration based on trigger criteria for the desired configuration being unmet.
20. The system of claim 15 , wherein the desired configuration includes changing a number of computer processing units and memory size for the VM.