We recently announced general availability of InceptionSX which lets you run the nested ESXi hypervisor on AWS or Google Cloud. But for the last two years we have had customers running their enterprise application environments with VMware VMs and complex networking on Ravello using just HVX.
The setup, install and performance is entirely different for the two So here is a quick cheat sheet explaining the differences.
|HVX: Running VMware VMs or virtual appliances on Ravello||InceptionSX: Running nested ESXi hypervisor on Ravello|
You can run all your virtualized enterprise workloads with existing VMware VMs and existing VMware virtual appliances on Ravello HVX, without any VM conversions required.
Ravello has developed a nested hypervisor with software-defined networking, called HVX, that runs in cloud VMs instead of running on bare metal servers. It runs on AWS/Google and exposes the same VMware interfaces, drivers, networking that the application expects. This mode is called HVX.
Without Ravello, it is not possible to run ESXi on AWS/Google Cloud. This is because the ESXi hypervisor, at boot time, looks for hardware extensions and instead discovers that AWS is running Xen and Google is running KVM. However, Ravello HVX exposes hardware extensions like IntelVT and AMD SVM in the public cloud so that you can run the ESXi hypervisor on it if required. This is for use cases where you need to test ESXi hypervisor features and this mode is called InceptionSX.
|Typical use cases||
|Performance||HVX is very lightweight and hardly adds any performance overhead. Expect to see the same overhead as going from physical to virtual when going from virtual to Ravello.||InceptionSX is running ESXi on HVX on either Xen (AWS) or KVM (Google). The performance is still very good but slightly lower than just HVX due to the extra layer of nesting|
|Installation & licensing||No ESXi install or licensing required||Install your own vSphere ISO and use your own vSphere license|