TSEvans
Contributor
Contributor

Cannot add network adapter to ESXi 6.5 VM?

Jump to solution

I have a fresh install of ESXi 6.5 on a very vanilla Dell server, default Broadcom networking, etc.  In VMware Network config, I have a very ordinary networking setup - one management network, one data network for VMs, both on working network connections.

When trying to edit an ESXi 6.5 VM, and choosing the option to "Add network adapter", the console crashes with the following error:

Unfortunately, we hit an error that we weren't expecting.

The client may continue working, but at this point, we recommend refreshing your browser and submitting a bug report.

Press the Esc key to hide this dialog and continue without refreshing.

When trying to look at the details of crash, I see:

Cause: <div ng-show="wizardOptions.data.networks[_index].AdapterType === 'VirtualSriovEthernetCard'" vui-stack-block="" data-tree-depth="1">

Version: 1.18.0

Build: 5270848

ESXi: 6.5.0

Browser: Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; Touch; .NET4.0C; .NET4.0E; .NET CLR 2.0.50727; .NET CLR 3.0.30729; .NET CLR 3.5.30729; Tablet PC 2.0; InfoPath.3; rv:11.0) like Gecko

Exception stack:

TypeError: Unable to get property 'enabled' of undefined or null reference

   at Anonymous function (https://xxcorpvmw1/ui/scripts/main.js:460:9439)

   at e (https://xxcorpvmw1/ui/scripts/main.js:319:3850)

   at Anonymous function (https://xxcorpvmw1/ui/scripts/main.js:319:23876)

   at Anonymous function (https://xxcorpvmw1/ui/scripts/main.js:319:15273)

   at r (https://xxcorpvmw1/ui/scripts/main.js:318:21124)

   at I (https://xxcorpvmw1/ui/scripts/main.js:319:15257)

   at g (https://xxcorpvmw1/ui/scripts/main.js:319:11540)

   at I (https://xxcorpvmw1/ui/scripts/main.js:319:15454)

   at g (https://xxcorpvmw1/ui/scripts/main.js:319:11540)

   at g (https://xxcorpvmw1/ui/scripts/main.js:319:11557)

There doesn't seem to be anything obvious I can edit in the VMX.  What other options can I try, short of having to re-install ESXi 6.5?

0 Kudos
1 Solution

Accepted Solutions
TSEvans
Contributor
Contributor

I did, and the outcome was the same.  It turns out this VM was an OVF import from 5.5.  It seems that 5.5 exports just don't work as a 6.5 import as this and other errors occur.  I would say if you're using an older OVF template, 6.5 is to be avoided.  The host was downgraded to ESXi 5.5 and now everything is working perfectly -- no problems in adding network cards, changing configs, etc.

Based on my experience with ESXi 6.5 and seeing all the other associated problems with it (especially all the unexplainable errors and a general lack of documentation), I would venture to say that 6.5 simply isn't ready for prime time yet.  Deficiencies in the web-based UI and the associated errors *definitely* make this product feel like step down from 5.5.

I won't evaluate 6.0 or higher for production use for at least another year -- it seems there are a *lot* of kinks that need to be worked out in this product.  Thanks for the help!

View solution in original post

0 Kudos
12 Replies
msripada
Virtuoso
Virtuoso

Hello TSEvans,

Its an interesting one. I have seen this when deploying OVF from 6.5. Are you seeing the same behavior on multiple browsers?

What is the ESXi host build number?

Thanks,

MS

0 Kudos
TSEvans
Contributor
Contributor

Yes, this happens regardless of the browser I am using.  Firefox, Chrome, IE 11 -- all crash in the same fashion.

Client version: 1.21.0

Client build number: 5744014

ESXi version: 6.5.0

ESXi build number: 5310538

Thanks,

TSE

0 Kudos
msripada
Virtuoso
Virtuoso

same error multiple scenarios

Unhandled Exception loading OVA

vsphere 6.5 resizing disk doesn't stick and crashing w 0x0000004e error

host client console error

One thing I wanted to check in the security settings of IE, check the setting for "Initialize and script activex controls not marked as safe for scripting" is allow or disabled?

Thanks,

MS

0 Kudos
TSEvans
Contributor
Contributor

That setting is set to the Disabled (Recommended) setting.

0 Kudos
msripada
Virtuoso
Virtuoso

For.testing, Can u enable and try the same step. If problem persists disable it again.

Thanks,

MS

0 Kudos
TSEvans
Contributor
Contributor

I did, and the outcome was the same.  It turns out this VM was an OVF import from 5.5.  It seems that 5.5 exports just don't work as a 6.5 import as this and other errors occur.  I would say if you're using an older OVF template, 6.5 is to be avoided.  The host was downgraded to ESXi 5.5 and now everything is working perfectly -- no problems in adding network cards, changing configs, etc.

Based on my experience with ESXi 6.5 and seeing all the other associated problems with it (especially all the unexplainable errors and a general lack of documentation), I would venture to say that 6.5 simply isn't ready for prime time yet.  Deficiencies in the web-based UI and the associated errors *definitely* make this product feel like step down from 5.5.

I won't evaluate 6.0 or higher for production use for at least another year -- it seems there are a *lot* of kinks that need to be worked out in this product.  Thanks for the help!

0 Kudos
PtrO2
Contributor
Contributor

I've got the same on a brand new 32GB/I7/SSD/Realtek adapters

Initially things went OK but after installing vCSA/Vcenter and fiddling with dual (redundant uplink) nic vSwitches things didn't function anymore after reboot.

One way or the other, vCenter has lost its focus to the existing VM Network, which cannot be changed and adding an adapter leads to the error.

It seems that all VM's have lost their connectivity to the vSwitch. Trying to correct and re-adding this through the WebClient leads to the failure.

(Still wondering why we have/must do flash on en sluggish Browser)

I had to reset the VM network Management on the Console and re-assign the (in my case) fixed UPv4 addresses.

Thereafter, the vSwtich was again connect-able for VM. Of course this behavior is unacceptable for production.

Note my VM now received the improbably message: "The portgroup for Network adapter 1, VM Network, could not be found. It has been assigned to VM Network."

So either VM network could not be found but still be connected........ strange worlds.... Smiley Wink

0 Kudos
itkaas
Contributor
Contributor

I have the same problem, I cannot add a network adapter to a VM without the interface crashing and asking to reload.

This is the SECOND install of VMWare ESxi 6.5 in the last week.

  6.5.0       5310538

I was unable to resolve the issue on the first host, so I decided to add another host instead of trying to fix VMware's problem.

I have used multiple browsers, Firefox, IE, even Opera, no change, they all crash.

This is for a development system so it is critical this works.

I have submitted a bug report for the crash, but I am still searching for a way to get past this.

Here is the error:

Cause: <div ng-show="wizardOptions.data.networks[_index].AdapterType === 'VirtualSriovEthernetCard'" vui-stack-block="" data-tree-depth="1">

Version: 1.18.0

Build: 5270848

ESXi: 6.5.0

Browser: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:54.0) Gecko/20100101 Firefox/54.0

Exception stack:

.controller<@https://192.168.125.203/ui/scripts/main.js:460:9439

e@https://192.168.125.203/ui/scripts/main.js:319:3872

Fe/this.$get</</<@https://192.168.125.203/ui/scripts/main.js:319:23883

I/<@https://192.168.125.203/ui/scripts/main.js:319:15273

r@https://192.168.125.203/ui/scripts/main.js:318:21124

I@https://192.168.125.203/ui/scripts/main.js:319:15257

g@https://192.168.125.203/ui/scripts/main.js:319:11540

I@https://192.168.125.203/ui/scripts/main.js:319:15454

g@https://192.168.125.203/ui/scripts/main.js:319:11540

g@https://192.168.125.203/ui/scripts/main.js:319:11557

G/<@https://192.168.125.203/ui/scripts/main.js:319:11155

Q/<@https://192.168.125.203/ui/scripts/main.js:319:12029

h@https://192.168.125.203/ui/scripts/main.js:319:14061

compile/<@https://192.168.125.203/ui/scripts/main.js:460:31080

Y/<@https://192.168.125.203/ui/scripts/main.js:319:20980

Z@https://192.168.125.203/ui/scripts/main.js:319:21038

I@https://192.168.125.203/ui/scripts/main.js:319:15506

g@https://192.168.125.203/ui/scripts/main.js:319:11540

G/<@https://192.168.125.203/ui/scripts/main.js:319:11155

Q/<@https://192.168.125.203/ui/scripts/main.js:319:12029

h@https://192.168.125.203/ui/scripts/main.js:319:14061

compile/<@https://192.168.125.203/ui/scripts/main.js:460:31080

Y/<@https://192.168.125.203/ui/scripts/main.js:319:20980

Z@https://192.168.125.203/ui/scripts/main.js:319:21038

I@https://192.168.125.203/ui/scripts/main.js:319:15506

g@https://192.168.125.203/ui/scripts/main.js:319:11540

G/<@https://192.168.125.203/ui/scripts/main.js:319:11155

Q/<@https://192.168.125.203/ui/scripts/main.js:319:12029

h@https://192.168.125.203/ui/scripts/main.js:319:14061

compile/</<@https://192.168.125.203/ui/scripts/main.js:322:9274

$watchCollection/<@https://192.168.125.203/ui/scripts/main.js:320:15736

$digest@https://192.168.125.203/ui/scripts/main.js:320:16343

$apply@https://192.168.125.203/ui/scripts/main.js:320:17773

@https://192.168.125.203/ui/scripts/main.js:428:269

dispatch@https://192.168.125.203/ui/scripts/main.js:317:14412

add/r.handle@https://192.168.125.203/ui/scripts/main.js:317:11234

0 Kudos
elektryczny
Contributor
Contributor

I have the same error. I can not do anything. This is ridiculous. What about VMware?

0 Kudos
Paulbuie
Contributor
Contributor

I couldn't agree more.  I'm did a clean install of 6.50d, and can't create even a single VM due to this issue.  I'm going back to 5.5 or 6 at this point.   Are you aware that you cannot upload folders from the file system?  Absolutely ridiculous. Nor can you download folders.  So if you want to copy a VM to your local drive, you have to do it one file at a time. 

AVOID 6.5

0 Kudos
dovi5988
Contributor
Contributor

We have the exact same issue on a fresh install. I assume this is a bug in ESXI. Where can I submit this as a bug?

0 Kudos
Eastadmin
Contributor
Contributor

Has anyone found away around this.

I have used 5.5 and 6.0 for a few years. I've just setup an new system at me new job installed 6.5 and went to create a new VM 2008R2 and I can't create anything with a Network adpter, I can create the VM without one but when I go to ADD one it crashes.

0 Kudos