Choosing and changing a VPS disk driver in SolusVM

Have an independent backup and console access. Identify the guest operating system, current controller, boot mode and driver support. For an existing production server, plan a tested migration or administrator-assisted change rather than assuming a dropdown is harmless.

1. For new or rebuilt SolusVM 2 servers, the administrator can set the disk-driver default for the operating-system version under Images > Operating Systems. Available choices depend on the platform and image.
2. Understand the scope: changing an image default applies to new deployments or reinstalls using that image, not automatically to existing VMs.
3. For an existing server, ask support to confirm the supported controller-change procedure. Prepare the target storage driver in the guest and ensure its boot environment can load it.
4. If maintaining a legacy panel with a Disk Driver field, record its original value and do not switch a live boot disk without the same compatibility checks.
5. After the approved change and required clean stop/start, observe boot through the console and verify the expected disk and filesystem are present.

Confirm the guest boots without an inaccessible-boot-device error and that mounted filesystems and applications work. Check persistent mounts and boot references because device names can change when a controller changes.

If the system cannot see its boot disk, restore the prior controller configuration and investigate the missing driver. Do not initialize or format the apparently missing disk. For a clean deployment, select a supported image and controller combination instead of reviving an obsolete operating system to match an old tutorial.

• Installing a VPS operating system from ISO in SolusVM 2
• Using the SolusVM browser console for VPS recovery
• Changing or troubleshooting a SolusVM virtual network adapter
• Reinstalling a VPS from an operating-system image in SolusVM

• SolusVM: Operating Systems