deployed VM from template but NIC is disconnected

[tdubb123]

I deployed a Vm from template using a customization template. I made sure the Vm deployed had NIC connected when i selected finished. But after the clone, the VM came up with nic disconnected

any idea?

[virtualg_uk · Accepted solution]

Possibly a bug but to confirm, can you check the contents of the VMX file?

It should have something on the lines of:

ethernet0.startConnected = "TRUE"

[RajeevVCP4]

what is NIC type in your template , is it vmxnet3 or e1000

[tdubb123]

did not see that in the vmx file

ethernet0.startConnected = "TRUE"

even tjhough connect at power on is checked

[tdubb123]

vmxnet3

[tdubb123]

I am on vm hardware 13 on esxi 6.5

[tdubb123]

added ethernet0.startConnected = "TRUE"

and seems to work.

so is it a bug with vcenter?

[virtualg_uk]

Quite possibly. I've noticed a few bugs in the newer HTML5 client. Worth reporting those if you can.

Glad it's fixed!

[tdubb123]

not good. if I customize my virtual hardware. the network adapter connect check box goes back to off

[virtualg_uk]

Might be worth re-creating the template and attaching the original disks?

[tyron_scholem]

Can you add that to VMTX instead of VMX, to have all new machines already deployed with this parameter?

I'm on HW 13 on ESXi 6.5 also, so this is probably a bug indeed. HTML5 client.

[ianfuller]

Do you mean the VMX of the deployed VM? Or the VMXT of the template? Or perhaps to convert the template back to VM, edit the VMX, then convert back to template?

The first won't solve the issue for future deployments and the latter two were not successful for me. I can confirm the check boxes for "Connected" and "connect at power on" are both enabled and ethernet0.startConnected = "TRUE" is present as a VM and VM template before deployment but during the deployment process they become unchecked.

vSphere 6.7.0.46000, ESXi 6.7.0 b17167734, VM version 14

[athelas]

Hello, i have the same problem. After customization process ends, check box connected disappear. Did you find any solution of this problem?

[TomKalabis]

same problem here ! 

vSphere 7.0u2 

[Mattythefatty]

I also have the same problem.  

vCenter is at 7.0.3.00100

ESXi hosts are 7.0.2, 18538813

Adding the line to the vmx file did not solve it for me.   I've tried deploying to a VSS and VDS port group.   No luck.

[samgdsc]

I'm having the same problem when cloning a template with Packer. Haven't found a solution yet. How this is still an ongoing issue is crazy. Someone in another forum suggested it could be an issue with VMware Tools. I haven'ttested without.

[KharkivIT]

Good day, Guys!

Hope, my situation will help.

I had the next problem:
1. Deployed Linux VM from template with a customization.

2. Had the same problem with the network.

3. On VM checked the next log-files: /var/log/vmware-vmsvc-root.log and found that my customization failed:
    "DeployPkgInGuest failed, error=5"

4. To solve the problem I've added the next option:
    /etc/vmware-tools/tools.conf
    [deployPkg] enable-custom-scripts = true

5. The next time VM deployed from template with a customization went thru two reboots (automaticaly):
    - during 1st reboot network was disconnected, but changes to the network (at least hostname) changed;
    - during 2nd reboot network became connected and VM worked well with new hostname and other settings.

The easiest way to check if the problem with vCenter:
1. Deploy VM from template without any customization => check network;
2. Deploy VM from same template with OS customization => check network.

BR 🙂

[Tymarand]

Could you please explain where you made these changes to get it to work properly?  Was it in the VMX or in the template?  Thank you!

[navina]

Convert the Template back to VM
Make sure the "Connect at Power On" option is selected. Change it back to Template and give a try