Update SolusVM 2 management and compute-agent components through the supported update controls. Review release-specific notices first, because a platform update can change task processing or require follow-up actions even when guest operating systems continue running.
IN THIS ARTICLE
Prepare for the change
Back up the management node using its documented procedure and verify guest recovery coverage. Record installed versions, selected update channel and pending tasks. Confirm the host operating systems remain supported; a SolusVM application update is separate from an operating-system release upgrade.
01 Update SolusVM 2 management and compute components
- Read release notes between the current and target version. Pay particular attention to queue handling, compatibility changes and required retries rather than scanning only feature descriptions.
- In Settings > System Updates, review the supported channel and schedule. Choose a maintenance window appropriate to the control-plane interruption and customer activity.
- Allow critical provisioning, migration and backup tasks to complete where the release guidance requires it. Avoid starting new bulk operations immediately before the update.
- Start or schedule the update through the interface and monitor its progress. Do not launch a second updater while the first is still active.
- Afterward, compare management and compute-agent versions and inspect failed or interrupted tasks. Retry only the specific operation after confirming it did not already complete.
Does updating SolusVM patch every guest?
No. Guest applications and operating systems need their own update policy. The host OS also has a separate maintenance lifecycle, particularly for changes that require a reboot or affect networking.
Confirm the expected result
Check administrator and customer login, compute-resource connections, one safe console operation and normal task processing. Confirm guest applications remain reachable. Record the final versions and any follow-up tasks so another administrator knows the update state.
If the change does not work
If an agent remains on an older version, inspect its update task and connectivity. Use the current documented retry or CLI procedure for that release instead of an old copied installer command. Preserve logs before recovery. Host kernel, network stack and OS updates require their own testing and reboot plan.