You can edit resources for all VSs. Depending on the template it is built on, some VSs can have their CPU or RAM or both resized without needing to be powered off ("resize without reboot"). If the VS template allows resize of the required resource without reboot, the resize should be completed automatically: you will be returned to the VS details screen and see a message indicating the resize was successful. If the template does not allow this, you will be asked to confirm that the VS will need rebooting so that the resize can take place. On how to determine whether the template you are interested in supports resize without reboot of RAM or CPU, refer to the Hot resize document.
- Windows virtual servers cannot be resized without reboot.
- It is not possible to increase the VSs RAM beyond its max_memory value without rebooting the server. For more information refer to Hot resize.
- If the template on which the VS is built on has the value 'YES' for the resize without reboot option, it might denote that either CPU or RAM can be changed without rebooting the server. Some templates support the resize without reboot only for either CPU or RAM while in other templates both CPU and RAM can be changed without rebooting the server. The virtualization type also influences the resize without reboot option. For more information refer to Hot resize.
The Edit Virtual Server screen will differ depending the way the VS resources were selected: either manually or using an instance package. To adjust VS resources:
- Go to your Control Panel's Virtual Servers menu.
- Click the label of the server you want to resize, to show its details screen.
- Click the Tools button and select the Edit Virtual Server link.
For virtual servers built by selecting resources manually:
- Change CPU cores, CPU priority/units and RAM values.
For virtual servers built using instance packages:
Choose the new instance package for your virtual server. Click the instance package to select it. After that, the instance package you have chosen will be highlighted in green.
Those instance packages that have resources incompatible with the compute zone, on which the VS is built, will be greyed out. Greyed out instance packages cannot be selected.
You can only choose from those instance packages that offer more disk size than the VS currently uses.
You can also edit the Time Zone parameter for all Windows KVM and Xen virtual servers. After you edit the server's time zone, you need to stop and then start up the VS. Currently, the time zone is set at the Compute resource side only. Therefore, users need to set the target time zone inside a Windows VS manually. Setting correct time zone at the Compute resource side helps to keep correct time inside a VS after starting it if time synchronization is not completed for some reason.
After changing VS resources you can see two prices per this VS per hour, depending on VS power status (on/off).
Please pay attention that when you resize a VS, the price is changed, and the new price is not applied immediately. It takes about 5 minutes to take effect.
- Click the Save button.