# VMXNET3 NIC in vSphere

**URL:** <https://forum.opennebula.io/t/vmxnet3-nic-in-vsphere/2702>\
**Category:** Product Support\
**Created:** [August 2, 2016, 7:33pm UTC](https://forum.opennebula.io/t/vmxnet3-nic-in-vsphere/2702 "2016-08-02T19:33:51Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![edcar13](https://avatars.discourse-cdn.com/v4/letter/e/3da27b/32.png) [@edcar13](https://forum.opennebula.io/u/edcar13)\
**Post date:** [August 2, 2016, 7:33pm UTC](https://forum.opennebula.io/t/vmxnet3-nic-in-vsphere/2702/1 "2016-08-02T19:33:51Z")

</div>

Whenever I attach a new NIC to a guest, it is always an e1000 which I don’t want. What I want is the vmxnet3 adaptor to be applied. I have amended vmm\_exec\_vcenter.conf so it it states “NIC=[MODEL=“VirtualVmxnet3”]  
” and restarted the system but it makes no difference. Any idea where I’m going wrong…? Thanks

---

<div class="post-metadata">

**Author:** ![ruben](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/ruben/32/19_2.png) [@ruben](https://forum.opennebula.io/u/ruben)\
**Post date:** [August 3, 2016, 9:21am UTC](https://forum.opennebula.io/t/vmxnet3-nic-in-vsphere/2702/2 "2016-08-03T09:21:13Z")

</div>

It seems that the driver is not reading the file. Please add the model to the NIC manually and we’ll fill an issue to double check this.

Cheers

---

<div class="post-metadata">

**Author:** ![edcar13](https://avatars.discourse-cdn.com/v4/letter/e/3da27b/32.png) [@edcar13](https://forum.opennebula.io/u/edcar13)\
**Post date:** [August 3, 2016, 9:53am UTC](https://forum.opennebula.io/t/vmxnet3-nic-in-vsphere/2702/3 "2016-08-03T09:53:13Z")

</div>

Thanks Rueben. I worked around the issue by changing the e1000 “catch all” to vmxnet3 (as that the only adaptor I want to use currently) in lib/one/ruby/vcenter\_driver.rb. This has resolved the issue and now whenever I add a new nic it is a vmxnet3 in vSphere.

File now reads like:  
else # If none matches, use VirtualVmxnet3  
RbVmomi::VIM::VirtualVmxnet3  
Thanks!

---

<div class="post-metadata">

**Author:** ![tinova](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/tinova/32/25_2.png) [@tinova](https://forum.opennebula.io/u/tinova)\
**Post date:** [August 29, 2016, 7:54pm UTC](https://forum.opennebula.io/t/vmxnet3-nic-in-vsphere/2702/4 "2016-08-29T19:54:36Z")

</div>

Issue is opened and we will fix it for OpenNebula 5.2:

[http://dev.opennebula.org/issues/4699](http://dev.opennebula.org/issues/4699)

---

<div class="post-metadata">

**Author:** ![nicpon](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/nicpon/32/4942_2.png) [@nicpon](https://forum.opennebula.io/u/nicpon)\
**Post date:** [November 22, 2016, 7:39pm UTC](https://forum.opennebula.io/t/vmxnet3-nic-in-vsphere/2702/5 "2016-11-22T19:39:02Z")

</div>

I just used the default config file and it is still not setting the correct driver in vsphere.

My /etc/one/vmm\_exec/vmm\_exec\_vcenter.conf is set to:

`NIC=[MODEL="VirtualVmxnet3"]`

Changing he vcenter driver default works like a charm though…

---

<div class="post-metadata">

**Author:** ![tinova](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/tinova/32/25_2.png) [@tinova](https://forum.opennebula.io/u/tinova)\
**Post date:** [November 23, 2016, 11:25am UTC](https://forum.opennebula.io/t/vmxnet3-nic-in-vsphere/2702/6 "2016-11-23T11:25:45Z")

</div>

The issue didn’t make it in 5.2.0 in the end, we had to retarget it for OpenNebula 5.4, apologies for that.