Determine the installed panel version, guest operating system and virtualization type. Record the current configuration and keep a working console and backup before changing virtual hardware. Never treat these switches as a general performance recipe.

1. Identify the actual requirement: ACPI relates to power-management signaling; APIC concerns interrupts; PAE is relevant to certain 32-bit guest memory arrangements; VNC supplies console access.
2. For SolusVM 2, review the server settings available to your role and ask support which compatibility controls are supported for that image. Do not look for a guaranteed copy of the old Settings tab.
3. If you are maintaining a legacy service that explicitly exposes these controls, change only the option required by the guest documentation. Preserve a record of its prior value.
4. Save and follow the platform instructions for applying virtual hardware changes. Arrange a graceful shutdown before a required stop/start.
5. Watch the next boot through the console and test the specific behavior you intended to correct.

Check normal boot and application operation. For power-management changes, verify a graceful shutdown request succeeds. If disabling console access was intentional, confirm another tested recovery path exists.

If startup breaks, restore the recorded option before making unrelated changes. Ask support to review unsupported or hidden controls. PAE is not a substitute for using a supported 64-bit operating system, and disabling ACPI can interfere with orderly shutdown. Avoid provider-side XML edits from an unverified old tutorial.

• Shutting down a SolusVM VPS without unnecessary data loss
• Using the SolusVM browser console for VPS recovery
• Changing or troubleshooting a SolusVM virtual network adapter
• Choosing and changing a VPS disk driver in SolusVM

• SolusVM: Operating Systems
• SolusVM: How To Configure Guest VM Shutdown Behavior