# vmware\_guest create from template very slow to start

**URL:** <https://forum.ansible.com/t/vmware-guest-create-from-template-very-slow-to-start/34617>\
**Category:** Ansible Project\
**Tags:** vmware\
**Created:** [February 12, 2021, 5:21pm UTC](https://forum.ansible.com/t/vmware-guest-create-from-template-very-slow-to-start/34617 "2021-02-12T17:21:11Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Joacim\_Martensson](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/joacim_martensson/32/4026_2.png) [@Joacim\_Martensson](https://forum.ansible.com/u/Joacim_Martensson)\
**Post date:** [February 12, 2021, 5:21pm UTC](https://forum.ansible.com/t/vmware-guest-create-from-template-very-slow-to-start/34617/1 "2021-02-12T17:21:11Z")

</div>

Hi,

We are using the vmware\_guest module to provisioning servers and have noticed its takes up to 1-2 minutes before the task show up and is executed in VMWare.  
We have tried it both from a standalone Ansible host and from Ansible Tower with the same result.

We have not seen similar issues with other VMWare modules. Its fast when we using for example vmware\_guest\_disk/vmware\_guest\_network adding more disks/networks.

Have anyone else had similar issues with this module and know where to start looking?

---

<div class="post-metadata">

**Author:** ![Dick\_Visser](https://avatars.discourse-cdn.com/v4/letter/d/d9b06d/32.png) [@Dick\_Visser](https://forum.ansible.com/u/Dick_Visser)\
**Post date:** [February 12, 2021, 6:03pm UTC](https://forum.ansible.com/t/vmware-guest-create-from-template-very-slow-to-start/34617/2 "2021-02-12T18:03:28Z")

</div>

Could be DNS issue causing lookup timeouts or something

---

<div class="post-metadata">

**Author:** ![Akasurde](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/akasurde/32/230_2.png) [@Akasurde](https://forum.ansible.com/u/Akasurde)\
**Post date:** [February 13, 2021, 3:13am UTC](https://forum.ansible.com/t/vmware-guest-create-from-template-very-slow-to-start/34617/3 "2021-02-13T03:13:54Z")

</div>

vmware\_guest waits for tasks to get triggered and uses [Exponential backoff](https://en.wikipedia.org/wiki/Exponential_backoff) So it does not get successful status it waits for next request.

You can check the code here - [https://github.com/ansible-collections/community.vmware/blob/44ac140e30ff0212470b47a29b105d0cdede4df4/plugins/module\_utils/vmware.py#L54](https://github.com/ansible-collections/community.vmware/blob/44ac140e30ff0212470b47a29b105d0cdede4df4/plugins/module_utils/vmware.py#L54)

I can imagine one improvement as configurable max\_backoff time.

---

<div class="post-metadata">

**Author:** ![Joacim\_Martensson](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/joacim_martensson/32/4026_2.png) [@Joacim\_Martensson](https://forum.ansible.com/u/Joacim_Martensson)\
**Post date:** [February 13, 2021, 5:23pm UTC](https://forum.ansible.com/t/vmware-guest-create-from-template-very-slow-to-start/34617/4 "2021-02-13T17:23:00Z")

</div>

So if our task is hitting some kind of internal VMWare que it can have to wait a minimum of 64 seconds.

lördag 13 februari 2021 kl. 04:14:27 UTC+1 skrev Abhijeet Kasurde:
