Resource Changes That Require Reboots
Some requests for resource changes may require an automatic reboot during change request fulfillment.
The following table lists whether a reboot will be performed for resource changes.
Not Supported indicates that this type of resource change is supported by the cloud platform, but not supported by Commander.
| Resource Change | Power down required? | 
|---|
| vCenter | SCVMM | AWS | Azure | GCP | 
|---|
| Modify CPU / memory resources OR change instance type | The CPU Hot Plug and Memory Hot Plug properties must be set for the VM in vCenter to enable this feature. | Yes | Yes | Yes | Yes | 
| Add network adapters | No | Yes | Not supported | Not supported | Not supported | 
| Delete network adapters | Yes | Yes | Not supported | Not supported | Not supported | 
| Modify network adapters | No | No | Not supported | Change subnet: Yes Other changes: Not supported | Not supported | 
| Add storage | No | No | No | No | Not supported | 
| Delete storage | No | No | No (base disk can't be deleted) | No (base disk can't be deleted) | Not supported | 
| Modify existing storage | No | Yes | Not supported | Yes | Not supported |