We will be happy to enable CPU host-passthrough mode on your KVM VPS upon request.
CPU passthrough, also known as host-passthrough mode, allows your VPS to see and use the actual CPU model and features of the physical host server, rather than a generic virtualized CPU model.
Running VMs inside your VPS (Docker, KVM, VirtualBox)
Access to AES-NI, AVX, AVX2, and other CPU extensions
Apps that check for specific CPU models or features
Testing software on specific CPU architectures
While Docker itself doesn't require CPU passthrough, nested virtualization (running Docker inside a VM) does. If you're running Docker directly on your VPS, passthrough is not needed.
Running VirtualBox, KVM, VMware, or other hypervisors inside your VPS requires CPU passthrough to access hardware virtualization extensions (Intel VT-x or AMD-V).
Applications using hardware-accelerated encryption (AES-NI) benefit from CPU passthrough to access these instructions directly.
CPU passthrough is enabled at no additional charge. Simply request it via support ticket.
# Check CPU model
cat /proc/cpuinfo | grep "model name"
# Check for virtualization support
egrep -c '(vmx|svm)' /proc/cpuinfo
# If the output is greater than 0, nested virtualization is availableOpen System Information (msinfo32) and check the Processor description. With passthrough enabled, you should see the actual host CPU model.
VPS cannot be easily live-migrated between different CPU models
VPS becomes dependent on specific CPU features of the host
Doesn't necessarily mean better performance for all workloads
Most applications and workloads don't need CPU passthrough. Only request it if you have a specific requirement like nested virtualization or applications that need particular CPU features.
To request CPU passthrough or if you have questions about whether you need it, open a support ticket. Include your VPS IP address and describe your use case so we can provide the best guidance.