You've missed the point a bit, and for the record I prefer to deploy Proxmox/KVM over VMware most of the time, I'm not a VMware cheerleader.
There are plenty of features Proxmox doesn't have that VMware does have. I've ran into a few of them
1. No ability to pin vCPUs to physical CPUs from within Proxmox. You have to drop to bash and set affinity for each vCPU's PID by hand if you want that.
2. You can't provision a VM with more vCPUs than physical CPUs. For example if I have a host with 8 cores, the max vCPU I can allocate to a VM is 8. And yes, I did have a use case for this.
3. You can't configure networked serial ports from within Proxmox. You have to drop to bash and edit the vm configuration file by hand if you want that.
4. Lack of serial port concentrator, which means you can't really use networked serial ports reliably when migrating VMs across hosts in a Proxmox cluster. In the NFV world this can be pretty important.
5. You can't manage multiple Proxmox VM hosts from a single UI unless they're clustered, which in many cases isn't practical to do. vSphere will let you manage multiple independent hosts from a single pane of glass.
6. (at least historically) lack of RSS/multiqueue in virtio networking. vmxnet3 on VMware supports this and allows you to scale better. But I will admit it's been several years since I've had a look at this area.
Again I'm not a VMware cheerleader. I'm sure I could generate a list like this for what Proxmox has that VMware lacks. But it's incorrect to state that it includes every single feature of ESX.
There are plenty of features Proxmox doesn't have that VMware does have. I've ran into a few of them
1. No ability to pin vCPUs to physical CPUs from within Proxmox. You have to drop to bash and set affinity for each vCPU's PID by hand if you want that.
2. You can't provision a VM with more vCPUs than physical CPUs. For example if I have a host with 8 cores, the max vCPU I can allocate to a VM is 8. And yes, I did have a use case for this.
3. You can't configure networked serial ports from within Proxmox. You have to drop to bash and edit the vm configuration file by hand if you want that.
4. Lack of serial port concentrator, which means you can't really use networked serial ports reliably when migrating VMs across hosts in a Proxmox cluster. In the NFV world this can be pretty important.
5. You can't manage multiple Proxmox VM hosts from a single UI unless they're clustered, which in many cases isn't practical to do. vSphere will let you manage multiple independent hosts from a single pane of glass.
6. (at least historically) lack of RSS/multiqueue in virtio networking. vmxnet3 on VMware supports this and allows you to scale better. But I will admit it's been several years since I've had a look at this area.
Again I'm not a VMware cheerleader. I'm sure I could generate a list like this for what Proxmox has that VMware lacks. But it's incorrect to state that it includes every single feature of ESX.