Newly Created VM Without Network Adapter "Connect at Power on"

[yuleisjtu]

Hi there,

The problem we encountered was that, the newly created VM sometimes did not have its net adapter "Connect at Power on". We did not expect this, since we've placed some more configuration to be done via its network interface. And I wonder whether anybody knows the reason, and how to prevent it.

Those VMs are cloned against VM templates. The basic scenario of VM creation was, that we took a VM template, adjust some of its hardware settings -- such as CPU, memory, but the network interface remains intact during this step -- and customize its IP addresses, and then go.

Sincerely,

Lei

[idle-jam]

hmm does the sometimes be:

only happens on different template? cause it may be due to the original template being that connect at power on is not tick

any more info so that can isolate and find the root cause for you. ..

iDLE-jAM | VCP 2, VCP 3 & VCP 4

If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points

[yuleisjtu]

Hi,

The term sometmes means that for one particular template, with the steps almost the same -- as they were triggered by code -- it sometimes brings out the connected adapter, or sometimes the not-connected adapter. And the timing, rather than the configuration, seems to be the major variant, since once a VM with non-connected adapter was created, it was very likely to have another VM also without the adapter connected, if it was also created right afterward.

Sincerely,

Lei

2010/11/27 idle-jam <communities-emailer@vmware.com<mailto:communities-emailer@vmware.com>>

,

A new message was posted in the thread "Newly Created VM Without Network Adapter "Connect at Power on"":

http://communities.vmware.com/message/1653689#1653689

Author : idle-jam

Profile : http://communities.vmware.com/people/idle-jam

Message:

[idle-jam]

For your case, i felt that this previously thread would be useful for you: http://communities.vmware.com/thread/202199

iDLE-jAM | VCP 2, VCP 3 & VCP 4

If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points

[yuleisjtu]

Again, thank you idle-jam,

The case I have seems to be in the pending thread of that post. First, I did NOT use any DVS, but just normal virtual switches, on every ESX server. Then, what I was trying to create were all of Linux OS, and with VMWare tools installed within the template. But one thing important is that, I was using Flexible as their default -- and since our program does not change it, it was also the actual -- adapter type.

Would this be gone if I just change the default adapter type. The OS(es) I was working includes CentOS 5.5, RedHat 5.4 and SuSE11, so would VMXNet3 be a good alternative?

Sincerely,

Lei

2010/11/27 idle-jam <communities-emailer@vmware.com<mailto:communities-emailer@vmware.com>>

,

A new message was posted in the thread "Newly Created VM Without Network Adapter "Connect at Power on"":

http://communities.vmware.com/message/1653708#1653708

Author : idle-jam

Profile : http://communities.vmware.com/people/idle-jam

Message:

[golddiggie]

With the operating systems you've listed, I think you'd have better luck using the e1000 adapter type... VMXNET3 would only give you more throughput if the VM's had access to a 10Gb LAN, or were all on the same hosts and datastores... Otherwise, you're still only going to be communicating at the fastest speed the slowest segment of the network can handle (hope it's 1Gb for you, at least)... If you wanted to create a private network, with no pNIC's on it, then the VMXNET3 adapter would provide you with an advantage, even without a 10Gb infrastructure...

I've had less problems using the e1000 adapter on CentOS 5.5 (same things as RHEL 5.x)...

VMware VCP4

Home Brewer... Brewing beer, making Mead, life's looking better... :smileygrin:

Consider awarding points for "helpful" and/or "correct" answers.

[yuleisjtu]

Thank you, golddiggie

Here is what I am going to do, I will modify all my templates, delete the old flexible adapter and add the new E1000 adapters. And then I will see whether there is improvement. Will let you all know if there really is, via my post.

Sincerely,

Lei

2010/11/27 golddiggie <communities-emailer@vmware.com<mailto:communities-emailer@vmware.com>>

,

A new message was posted in the thread "Newly Created VM Without Network Adapter "Connect at Power on"":

http://communities.vmware.com/message/1653737#1653737

Author : golddiggie

Profile : http://communities.vmware.com/people/golddiggie

Message:

[yuleisjtu]

Well, first thing I wanna tell you all is that, it did NOT work. I change the network adapter type to E1000, and got everything just the same. And since this happens occasionally, that makes our life more painful.

Anyway, if I make a conclusion of my issue, the thing we have is that, when a VM is duplicated and booted with IP customized, in the vmx file, there maybe a line that

ethernet0.startConnected="TRUE"

and it also maybe a line that

ethernet0.startConnected="FALSE"

in the latter case, after a couple of minutes, the line might or might not change to the former case.