# Ansible ending support for Vsphere ESXI free hypervisor with deprecation of vsphere\_guest ?

**URL:** <https://forum.ansible.com/t/ansible-ending-support-for-vsphere-esxi-free-hypervisor-with-deprecation-of-vsphere-guest/26802>\
**Category:** Ansible Project\
**Tags:** vmware\
**Created:** [February 20, 2018, 4:21pm UTC](https://forum.ansible.com/t/ansible-ending-support-for-vsphere-esxi-free-hypervisor-with-deprecation-of-vsphere-guest/26802 "2018-02-20T16:21:53Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mgdavis967](https://avatars.discourse-cdn.com/v4/letter/m/db5fbb/32.png) [@mgdavis967](https://forum.ansible.com/u/mgdavis967)\
**Post date:** [February 20, 2018, 4:21pm UTC](https://forum.ansible.com/t/ansible-ending-support-for-vsphere-esxi-free-hypervisor-with-deprecation-of-vsphere-guest/26802/1 "2018-02-20T16:21:53Z")

</div>

Hello,

I’ve noticed that the **vsphere\_guest** modules that provides the ability to create/delete/manage a a guest VM through VMWARE vSphere is now deprecated.  
The module advised for use current/future use is the **vmware\_guest** module.

The vsphere\_guest modules enables VMs to be created and managed with ansible on **standalone ESXI servers** that use the **free hypervisor licence** without vCenter - as used in many home/learning labs.

However, the vmware\_guest module does not appear to allow VMs to be created (or indeed any write operations) on ESXI standalone server which only have the free licence and is, i believe, only really intended for use with vCentre  
Therefore with deprecation of vsphere guest it would appear won’t be possible in the future to use ansible for home lab automation on a standalone esxi server without vCentre.

Note - I’ve tried migrating working vsphere\_guest playbooks for creating and configuring VMs on ESXI standalone to the vmware\_guest model and it does fail with the message  
“Failed to create virtual machine due to product versioning restrictions: Current license or ESXi version prohibits execution of the requested operation.”

I am assuming that this is due to the underlying VMWare API used by vmware\_guest that does not allow any write actions unless via vCenter.

Is anyone able to confirm the above is a correct understanding ?

Thanks,  
Mike.

---

<div class="post-metadata">

**Author:** ![Dave](https://avatars.discourse-cdn.com/v4/letter/d/ee7513/32.png) [@Dave](https://forum.ansible.com/u/Dave)\
**Post date:** [April 26, 2018, 3:44pm UTC](https://forum.ansible.com/t/ansible-ending-support-for-vsphere-esxi-free-hypervisor-with-deprecation-of-vsphere-guest/26802/2 "2018-04-26T15:44:21Z")

</div>

I’m getting the same message. From all the YouTube videos, it appears the speakers are using the web interface for VMWare 6.0, not 5.5 or lower. What version of ESXi are you running?

---

<div class="post-metadata">

**Author:** ![James\_Tutton](https://avatars.discourse-cdn.com/v4/letter/j/f9ae1b/32.png) [@James\_Tutton](https://forum.ansible.com/u/James_Tutton)\
**Post date:** [September 12, 2018, 9:21am UTC](https://forum.ansible.com/t/ansible-ending-support-for-vsphere-esxi-free-hypervisor-with-deprecation-of-vsphere-guest/26802/3 "2018-09-12T09:21:33Z")

</div>

Did anyone get any clarity on this as i to am in the same boat and have a number of scripts that want to move over from vsphere\_guest to vmware\_guest but hitting the same issue. I’m using Standalone ESXi 6.0 with Free licences in home lab. But have access to a number of Free Hosts and can confirm that get same error on these builds:

VMware ESXi 6.5.0 build-5146846  
VMware ESXi 6.0.0 build-2494585

If the 2 method us different API’s can we at least keep vsphere\_guest as an alternative as due to licence limitations it appears that vmware\_guest isnt a direct replacement in a number of lab enviroments where full ESXi licences are not used at all times. Worse case maybe rename it to standalone\_esxi\_guest but at least keep it as a core module.