A compute resource is a host that supplies CPU, memory and storage for virtual servers managed by SolusVM 2. This is the current architecture corresponding to much of what older SolusVM 1 guides called a slave node.
IN THIS ARTICLE
Check access and requirements
Use an authorized infrastructure-administrator account and an already functioning SolusVM 2 management node. Prepare a clean supported compute-host OS with the required virtualization capability, network design and storage layout. Confirm current requirements for the intended hypervisor. A standard VPS does not automatically permit nested virtualization, bridge changes or provider address routing, so obtain explicit platform support before designing around them.
01 Add a compute resource to SolusVM 2
- Check hardware virtualization availability and the supported host configuration. Record physical or virtual NIC names, management addresses, gateway and storage devices. Keep out-of-band console access because network reconfiguration can interrupt SSH.
- Plan the compute-resource networking and storage using the current vendor guidance. Confirm which addresses are routed to the host and whether a bridge or routed setup is appropriate. Never attach an unassigned subnet simply because a tutorial uses it.
- In the management interface, open Compute Resources > Add Compute Resource. Enter a descriptive name and the verified host address.
- Select the documented SSH authentication method and provide the authorized credentials or key needed for initial connection. Treat any private key as sensitive and keep it out of screenshots and support transcripts.
- Save and let SolusVM validate the host and install the required integration. Review validation errors instead of bypassing missing virtualization or unsupported-OS checks.
- Complete the storage, IP-block, location and plan associations required by your deployment. Set sensible capacity limits and monitoring before allowing customer provisioning.
- Create a disposable test VM with an assigned address and supported image, then exercise normal power, console and backup workflows.
Common questions
Can I use a server with existing production workloads?
Plan a supported migration and maintenance window. Hypervisor, bridge and storage changes can affect existing workloads, so a clean dedicated resource is easier to validate and recover.
Is successful SSH access enough?
No. Compute support also depends on virtualization, storage, routing, firewall paths and the chosen operating system. Validate a complete disposable VM lifecycle before assigning production customers.
Confirm the expected result
Confirm the compute resource remains connected, the VM boots, guest networking works in both directions and storage reports the correct capacity. Test migration or backup features only when configured and within their documented requirements. Monitor host resource use before increasing customer density.
Resolve setup problems
If onboarding fails, inspect SSH reachability, permissions, host virtualization support and the exact task error. If networking becomes inaccessible, use the provider console to restore the recorded configuration. Do not install the legacy master/slave script or repeatedly wipe storage as a response to an unexplained onboarding failure.