Guest tools provide supported communication between a SolusVM KVM server and the virtualization platform. A custom ISO installation may need drivers, guest-agent installation and network configuration that a prepared image already supplies. Install tools inside the correct guest, not on an unrelated host.
IN THIS ARTICLE
Check access and requirements
Confirm the guest OS and version are supported, keep a recent backup and arrange console access. Identify whether the issue is missing disk/network drivers, an absent agent, or a stopped service. These components serve different purposes and may have different installation methods.
01 Install and check guest tools for a SolusVM 2 server
- Open the server details and inspect the reported guest-agent or tools status where available. For an ISO installation, review the current SolusVM instructions displayed when returning to disk boot.
- Use the OS-specific package or signed driver source documented for the installed platform. On Linux this commonly includes the distribution QEMU guest-agent package; Windows may need compatible VirtIO drivers and the agent installer.
- Install the required components and start the appropriate service. Follow any planned restart requirement, keeping the console available until network and disk access are confirmed.
- Verify that the host exposes the expected guest-agent channel. A running service without its virtual communication device cannot communicate with the management platform.
- Refresh the SolusVM status and test a harmless supported information query or controlled shutdown during a maintenance window. Keep application-level monitoring separate.
Will the agent repair my application automatically?
No. It supports specific guest-management operations. Application health, backups and troubleshooting still require their own checks and an authorized operational workflow.
Confirm the expected result
Confirm agent status is healthy after a guest restart and that the intended virtual disk and network devices use supported drivers. Review the guest service log for repeated connection or permission errors. Verify normal application access before closing the change.
Resolve setup problems
If the service cannot open its channel, ask the infrastructure administrator to inspect the managed VM configuration. Avoid hand-editing generated libvirt XML unless the vendor-supported customization workflow calls for it. For a boot failure after a driver change, recover through the console or backup with the previously working virtual hardware configuration.