Identify the guest release and current adapter model. Keep console access, a backup and the assigned IP, prefix, gateway and DNS settings. In current SolusVM 2, device selection may be administrator-managed rather than a customer dropdown.

1. Confirm the reason for the change with the operating-system or driver documentation. A slow application does not by itself justify switching from one emulated adapter to another.
2. Install or prepare the supported target driver inside the guest before changing the device, particularly for Windows guests using VirtIO.
3. Ask support to confirm the supported adapter choices and application procedure for your service. On a legacy panel that exposes Network Card, use that control only for the intended VPS and approved model.
4. Perform a clean shutdown and the required stop/start after the change. Observe boot through the console because SSH or Remote Desktop may initially fail.
5. Check the new interface name, driver and network configuration. Reapply only the addresses assigned to the VPS, using the guest operating system supported network configuration tool.

Test gateway reachability, DNS resolution, outbound connectivity and inbound application access. Confirm the settings survive a planned restart before closing the maintenance window.

If the new adapter does not appear or the driver fails, restore the previous model through support or the available panel control. Avoid guessing interface names or flushing all firewall rules. A container does not necessarily expose replaceable virtual hardware, so this procedure must not be applied blindly to every SolusVM service.

• Using the SolusVM browser console for VPS recovery
• Installing a VPS operating system from ISO in SolusVM 2
• Checking VPS resources and IP addresses in SolusVM
• Understanding APIC, ACPI, PAE and console options in SolusVM

• SolusVM: ISO Images
• SolusVM: Operating Systems