The SolusVM server overview helps you confirm allocated CPU, memory, disk and network resources. Those allocations do not always equal current usage or the filesystem space visible inside the guest.
IN THIS ARTICLE
What you need before you begin
Have the active plan details and any recent upgrade confirmation available. Identify the intended VPS by project, server ID and IP address. Some live statistics depend on guest tools and can be absent even while the server is running.
01 Check VPS resources and IP addresses in SolusVM
- Open the server overview in the correct project. Review its plan resources and current power state.
- Check the primary disk and any additional disks separately. Do not assume a larger virtual disk has already expanded the partition or filesystem inside the guest.
- Open the networking details and record the assigned IPv4 and IPv6 information. Use only addresses allocated to your service.
- Compare allocation with guest readings. On Linux,
free -h,lsblkanddf -hprovide different views of memory, block devices and mounted filesystems. - Review usage graphs with their time interval. Distinguish cached memory, swap and a short workload spike from a sustained resource limit.
02 Example: why an upgraded disk can still look full
After a plan change, the panel might show a 100 GB virtual disk while the mounted root filesystem still has its earlier capacity. Compare the virtual disk, partition and filesystem as three separate objects.
On Linux, lsblk can show that the disk is larger than the root partition, while df -h reports only the mounted filesystem. LVM or another storage layer can introduce an additional step between those objects. Capacity units and reserved space can also make the displayed numbers differ.
Send support the panel allocation and the guest readings if they do not match the expected upgrade. Expansion must follow the actual partition, volume and filesystem layout; do not format the existing disk or copy a resize command for another storage design.
How do I verify the displayed VPS resources?
Confirm that the allocated resources match the current order and that the guest recognizes the expected disks and interfaces. After an upgrade, plan any supported filesystem expansion before expecting more usable storage.
Troubleshoot unexpected results
For a discrepancy, include both panel and guest values plus the VPS ID in a support request. Do not format an existing disk or add a guessed IP address. If metrics are unavailable, check guest integration and collection delays before concluding that the resource is unused or missing.