If you scroll down in the message box you will see which features are expected but missing on the target host. Often such issues are caused by different host BIOS versions and/or settings. Please double check "VT-x" as well as "Execute Disable" are both enabled in the host's BIOS (assuming it's an Intel CPU). Ensure you power cycle the host after changing any of these settings, a simple reboot might no be sufficient!
The reason you are able to vMotion the VM when started on one host but not on the other is that the features exposed to the VM are determined at the time the VM is powered on. If the target host meets the VM's feature set vMotion is possible.
André