# strange thing about vmware\_gueest module

**URL:** <https://forum.ansible.com/t/strange-thing-about-vmware-gueest-module/35330>\
**Category:** Ansible Project\
**Created:** [June 11, 2021, 7:18am UTC](https://forum.ansible.com/t/strange-thing-about-vmware-gueest-module/35330 "2021-06-11T07:18:37Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gregory\_Edigarov](https://avatars.discourse-cdn.com/v4/letter/g/71c47a/32.png) [@Gregory\_Edigarov](https://forum.ansible.com/u/Gregory_Edigarov)\
**Post date:** [June 11, 2021, 7:18am UTC](https://forum.ansible.com/t/strange-thing-about-vmware-gueest-module/35330/1 "2021-06-11T07:18:37Z")

</div>

hello, list!

ansible 2.9

I have this in my playbook:

- name: Create a virtual machine on given ESXi hostname  
vmware\_guest:  
hostname: “some”  
username: “someone”  
password: “somepass”  
template: “{{ vmtemplate }}”  
validate\_certs: false  
folder: “”  
datacenter: qarea  
name: “{{ tempname }}”  
state: poweredon  
guest\_id: ubuntu64Guest  
cluster: “DRS”  
disk:
- size\_gb: “{{ disksize }}”  
type: thin  
datastore: DSS  
hardware:  
memory\_mb: “{{ memsize }}”  
num\_cpus: “{{ ncpus }}”  
scsi: paravirtual  
networks:
- name: Localnet  
start\_connected: yes  
type: dhcp  
when: “{{ localnet | bool == true }}”
- name: AS  
start\_connected: yes  
when: “{{ asnet | bool == true }}”  
wait\_for\_ip\_address: true  
delegate\_to: localhost  
register: deploy\_vm

if I remove network section completely, then it successfully creates vm, connects it to the default network (Localnet in my case) and then everything works as expected.

if I add the networks section then:

1. in vm i see the corresponding to intefaces with no carrier state
2. in vsphere management interface I see the two networks bound to this vm, in not connected state. I am able set them to connected state then.

is this a bug? or am i missing something?

thank you