VMXNet3

Similar Questions

• Enabling Jumbo frames on VMXNET3 adapter in Windows Server 2012

  Hello everyone on the forums of wonderful Equallogic :)

  We have a PS4100X of the virtual computer running on vSphere 5.1 EQL. Everything works very well, and we are about to migrate a VM 2012 SQL our database. I did some research on the issue of whether we should allow the frames extended on the VMXNET3 adapter in the virtual machine.

  Reading this white paper, it seems there are large performance benefits to enable jumbo frames and a few other options in the NETWORK adapter settings:

  http://en.community.Dell.com/TechCenter/Extras/m/white_papers/20403565.aspx

  Just curious as to how other people and if they saw an improvement in performance. Someone at - he had experience with this?

  Thank you

  Lee

  Frames being good or bad, is highly dependent on the switching infrastructure.   If the switches do not manage flowcontrol and frames, then performance could be worse with frames enabled.

  If the switches are not on the list certified for EQL tables, I tend to start with the standard frames, get a baseline run, then try frames gradually and do things of course worsen.

  Extended frames may provide an advantage, he will never be a huge increase, but it improves the efficiency of the network and could reduce the overhead of the processor.    Which are not mandatory for EQL iSCSI environments.

  Please check best practices with document ESX.  That can really help to maximize your performance with storage EQL.

  http://en.community.Dell.com/TechCenter/Extras/m/white_papers/20434601.aspx

  Kind regards

• Unable to choose VMXNET3 adapter

  A small backstory - ESX 5.5, VM running is VyOS (which is running a Debian flavor).  We add a 10Gig NIC to the host and would like to take advantage of the faster speeds on virtual machines.  VyOS is currently using the E1000 adapter, and the drop-down list of adapter inside the map Add Wizard window lists only E1000 (with no VMXNET3).

  

  Strangely, create a new VM VyOS from scratch (using the same ISO installation), I am able to choose between E1000 or VMXNET3 initial VM Wizard, and this new virtual machine recognizes the VMXNET3 adapter (and 10Gig speeds).  I'd rather not have to migrate to this new virtual machine - how can I add the VMXNET3 adapter to the existing VM VyOS?

  Exactly as I thought:
  the new virtual machine has two PCI-express ports. The old man uses only PCI-ports.
  To reset the mainboard remove all lines that start with pci *, value of the a different option of 'other-64' guestOS and start the virtual machine once.
  After that, you should be able to use the graphical interface

• vmxnet3 adapter on windows server 2012 with problem of bottleneck for MSSQL Server

  Hello!

  We have a server windows 2012 R2 with MSSQL server 2014.

  The client software uses the jdbc for database connection. If customers make a query which collects a massive amount of data the whole thing slowed down after a while.

  Then, his need to wait 10-20 minutes to speed up again. I have tested and tried everything.

  -measure the ethernet parameters

  -replace the cables by cat7

  -installed a virtual machine with the windows client and the real customer use the virtual environment via rdp

  -activated the RSS in the vmxnet3 advanced settings and windows

  -the mode SplitRx in vcenter vm settings and disabled ethernet Coalescent too

  -set the VM to high latency

  -tried to migrate the virtual machine to another host

  Not for their help. If a massive sql query is run first its great, then the need for a second or more to check a single record.

  checked the vm cpu stress but its less than 5% all the time. Checked the network with wireshark, there are a lot of small packets but nothing big. The bandwidth used is still low.

  When its idle delay after two packets will increase from a few ms to 400-500 ms.

  Our most powerful server is an HP DL380 G9 with two octa core Xeon processor 384 GB of ram, full SSD datastore. Its a lightning fast host.

  The virtual machine have 8 core cpu and 64 GB of ram.

  No matter where am I up the virtual machine or how many resources provide the custom aisle question.

  The strange thing is when customers slowed down I can copy large files between the client and the server with fast speed, so the slow sql.

  I can solved this question if I use the ethernet E1000 instead of the VMXNET3 adapter, but E1000 have much more load and the server need to transfer big files too, not only the sql service.

  Vmxnet3 much faster and have less overhead, but this question of sql, I have a problem with that. So I go back to the E1000 for now. Its slower eat more cpu but the sql connections works very well without any problems.

  Can someone tell me what I can try harder to identify the vmxnet3 problem? I really need it to improve network performance and lower overhead, but the rapid sql is the top priority.

  Thank you!!!

  We had exactly the same problem on our SQL servers once upgraded to Vsphere6.This is due to Receive Segment coalescence feature in new VMXNET3-nics on Win 2012.

  More details here: http://nickmarshall.com.au/blog/2015/7/24/vsphere-6-hardware-version-11

  The best way to solve this problem is to turn it off completely in the server operating system (in the admin command prompt):

  netsh int tcp set global rsc = disabled

  
  

  Check with:

  
  

  netsh int tcp show global

  It's fast and easy without downtime or disruptions and involves no change types of nic.

  After doing this on all our SQL and application servers, everything was ok.

  
  

  
  

• machine 2 crashed after update network adapter type E1000 VMXNET3

  What is the reason why the machine is not booting with OS after update of E1000 VMXNET3 network adapter,

  update is done via scripts

  in this case, there is a solution that allows you

  1 remove the adapter NETWORK adapter or remove the connection

  2. adding another type of VMXNET3 adapter new

  3. start Machine... If boot machine... Stop the machine

  then. Remove the new card NETWORK adapter

  and fix the old on or connect an old

  hope it will work.

• CentOS 5.8 32 bit OS does not show the VMXNET3 nic card

  We have an activity reclassification e1000 nic to VMXNET3 on all servers in our environment. We have successfully upgraded to RedHat 5 32 bit to vmxnet3 e1000 nic cards, but we are unable to do so in CENTOS 5.8 32bits. Vmxnet3 is compatible bits centos 5.8 32.

  VMTools are up-to-date and H/W is 7.

  Let me know what should I check other than that and how do I solve the problem?

  Fixed the problem by selecting the correct name of the virtual machine.

  Here is the link

  Documentation for VMware for CentOS 5

• Maximum traffic for a vmxnet3

  Assuming that there are no bottlenecks elsewhere, what is maximum penetration network traffic that a unique vmxnet3 adapter on a virtual machine can receive network?  It is 10 Gbit/s (gigabytes per second) or 10 Gbps (GigaBITS per second)

  Thank you!

  In theory and in the physical world, the maximum data rate would be 10 Gigabit/s, since vmxnet3 emulates a 10GBASE-T physical link.

  This flow is governed by physical limitations and traffic on the wire of the standard, but these do not apply in a purely virtual configuration (vSwitch and port group 2 virtual on the same host and same computers).

  Invited on the same host and vSwitch and port group are able to exceed beyond 10 Gbit/s. I know, we could think that for example the e1000, which has a link from 1 Gbps to the guest, is limited to 1 GB/s maximum. or vmxnet3 is limited to a maximum of 10 Gbps. But this isn't the case. They can easily exceed their "speed of the virtual link. Test it with a tool of network throughput as iperf a see for yourself.

  This is because only the true physically imposed restrictions do not apply in a virtualized environment between two virtual machines on the same host/port signalling group. Operating systems don't artificially restrict traffic to match the speed of the agreed line unless it is physically required.

  To give you an example, I am able to reach 25 + Gbps between 2 virtual Linux machines with a single on the same host/network vmxnet3 vNIC

  For reference, I am able to get 25 + Gbps with the test tool of network throughput iperf between two virtual Linux machines with a vNIC vmxnet3 unique on the same host/port group. (Yes, 25Gbps. Even if a vmxnet3 emule link 10 Gbps, throughput is not artificially capped without physical limitation of signal).

  Once you get to the external communication outside a host then you are limited by your physical host of ESXi links limitations.

• Vmxnet3 disconnects abruptly from the vDS on a server running Windows R2 2012

  Vmxnet3 abruptly disconnects the vDS on a server running Windows 2012 R2. When this occurs, the affected server also loses its static IP address for a 169. address.

  Any ideas on what could cause this problem. It happens 2 Wk12 servers in a production environment of servers W2k12 100.

  Hello.

  Have you tried to re-install vmtools and restart on this vm?

• Replace e1000 vmxnet3

  I installed on vmware workstation to esxi, I want to change the change to vmxnet3 e1000 NICs

  someone has an idea?

  pls I want to change to ESXI not for the virtual machine.

  hussein_mohson wrote:

  I installed on vmware workstation to esxi, I want to change the change to vmxnet3 e1000 NICs

  someone has an idea?

  pls I want to change to ESXI not for the virtual machine.

  Edit the virtual machine configuration file and Add (or change) these settings:

  ethernet0.virtualDev = vmxnet3

  Ethernet1.virtualDev = vmxnet3

  ethernet2.virtualDev = vmxnet3

  ethernet3.virtualDev = vmxnet3

  ...

• How to get vsphere 5.5 vmxnet3 NETWORK adapter drivers without installing vsphere 5.5?

  We are on vSphere 5.0 indefinitely.

  I really need to get the 5.5 x 64 vmxnet3 vSphere interface drivers NETWORK to put in a picture of Windows startup.

  How can I do this without having to install vsphere 5.5 everywhere?

  I don't currently have the means to do a 5.5 install any...

  Maybe someone could PM me a zip file containing only the required files?

  Thank you, Tom

  Here's the latest version for Win 2012 R2 U1 on ESXi 5.5 u1

  9.4.5 Tools version build 1598834

• Change to VMXNET3 E1000 VMnic

  Hi all

  We have a requirement where we need to change the E1000 VMnic to VMXNET3. But the client VM implementation related to the Mac. Can we remove the E1000 and add new nic (VMXNET3) and always use the same Mac address (keeping the nic Mac manual type and deal with the same MAC address)?

  Kind regards

  Vikram.

  Hello

  Yes.

  Turning off the existing MAC address

  Remove the adapter

  Add the new VMXNET3 adapter

  Change MAC address manual and paste the copied in the first step MAC address.

  I've tested this and the MAC address is accepted by the new adapter.

  Assign points if you find the answer useful

• vmxnet3 causes panic of the kernel on CentOS 6.3

  Hello

  I'm running on ESX 5.1. The guest is CentOS 6.3 with vmxnet3 1.1.32.0.

  When under load the kernel is short of the skbs machine hangs with the following stack:

  [77782.262000]-[cut here].

  [77782.262000] kernel BUG at /tmp/build_rpm_sandbox.vy6fT4/BUILD/vmware-open-vm-tools-9.0.0/vmxnet3/vmxnet3_drv.c:1467!

  [77782.262000] invalid opcode: 0000 [#2] SMP

  [77782.262000] last sysfs file: / sys/module/ipv6/initstate

  [77782.262000] CPU 0

  [77782.262000] related modules to the: ip_vs libcrc32c u2p (P) (U) nls_cp950 netconsole hades (P) (U) (U) imp_iTCO_wdt, hades_wd (U) ip6table_filter ip6t_REJECT vmblock (U) (U) vsock configfs ip6_tables fuse vmware_balloon ipt_REJECT iptable_filter ip_tables ppdev parport_pc parport vmxnet3 (U) ipv6 sg i2c_piix4 i2c_core vmci (U) shpchp ext3 jbd mbcache crc_t10dif mptspi mptbase scsi_transport_spi pata_acpi ata_generic ata_piix mptscsih cdrom sr_mod sd_mod dm_mirror dm_region_hash dm_log dm_mod [last unloaded: netconsole]

  [77782.262000]

  [77782.262000] Pid: 14178, comm: gw.x Tainted: P - 2.6.32 - 279.el6.imp4.x86_64 #1 VMware, Inc. VMware Virtual Platform/440BX office reference platform

  [77782.262000] RIP: 0010: [< ffffffffa01b0a1f >] [< ffffffffa01b0a1f >] vmxnet3_rq_rx_complete + 0x9bf/0xbc0 [vmxnet3]

  [77782.262000] RSP: 0018:ffff8800282037c8 EFLAGS: 00010046

  [77782.262000] RAX: 0000000000000040 RBX: ffff880239dd0ee0 RCX: 0000000000001000

  [77782.262000] RDX: 0000000000000004 RSI: 00000000000006c 8 RDI: 0000000000000000

  [77782.262000] RBP: ffff880028203838 R08: R09 ffff880238629800: 00000000000006c 8

  [77782.262000] R10: 0000000000000001 R11: 0000000000000000 R12: ffff88023a94aea0

  [77782.262000] R13: ffff8802365a4c10 R14: ffff880239dd06e0 R15: ffff88023862aa18

  [77782.262000] FS: 00007f61f2aea700 (0000) GS:ffff880028200000 (0000) knlGS:0000000000000000

  [77782.262000] CS: 0010 DS: 0000: 0000 CR0: 0000000080050033

  [77782.262000] CR2: 0000000000a9f270 CR3: 000000008beaa000 CR4: 00000000000006f0

  [77782.262000] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000

  [77782.262000] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400

  [77782.262000] gw.x process (pid: task 14178, threadinfo ffff880080828000, ffff880080820970)

  [77782.262000] battery:

  [77782.262000] ffff88023b9c0c40 ffff88023b9c0c80 0000000000000001 ffff880239dd0ee8

  [77782.262000] < d > ffff880028203868 0000001081151947 0000000000000001 000000c 100000000

  [77782.262000] < d > ffff88023b9c0c80 ffff880239dd06e0 ffff880239dd0ee8 0000000000000010

  [77782.262000] call Trace:

  [77782.262000] < IRQ >

  [77782.262000] [< ffffffffa01b0da3 >] vmxnet3_poll_rx_only + 0 x 53 / 0 x 110 [vmxnet3]

  [77782.262000] [< ffffffff8143c835 >] netpoll_poll_dev + 0xd5 / 0 x 490

  [77782.262000] [< ffffffff8143cc9a >] find_skb + 0x8a / 0 x 90

  [77782.262000] [< ffffffff8143cf96 >] netpoll_send_udp + 0 x 36 / 0 x 230

  [77782.262000] [< ffffffffa001633b >] write_msg + 0xbb / 0 x 110 [netconsole]

  [77782.262000] [< ffffffff81064a65 >] __call_console_drivers + 0 x 75 / 0 x 90

  [77782.262000] [< ffffffff81064aca >] _call_console_drivers + 0x4a/0 x 80

  [77782.262000] [< ffffffff81064fde >] release_console_sem + 0x4e / 0 x 220

  [77782.262000] [< ffffffff81065797 >] vprintk + 0 x 247 / 0 x 560

  [77782.262000] [< ffffffff814e81ce >] printk + 0 x 41/0 x 43

  [77782.262000] [< ffffffff810a3ed7 >] print_modules + 0 x 97/0xf0

  [77782.262000] [< ffffffff8100e066 >] show_registers + 0 x 46 / 0 x 280

  [77782.262000] [< ffffffff814ee23a >]? atomic_notifier_call_chain + 0x1a/0 x 20

  [77782.262000] [< ffffffff814ec053 >] __die + 0xb3/0xf0

  [77782.262000] [< ffffffff8100f178 >] die + 0 48 x / 0 x 90

  [77782.262000] [< ffffffff814eba44 >] do_trap + 0xc4 / 0 x 160

  [77782.262000] [< ffffffff8100cd95 >] do_invalid_op + 0 x 95/0xb0

  [77782.262000] [< ffffffffa01b0a1f >]? vmxnet3_rq_rx_complete + 0x9bf/0xbc0 [vmxnet3]

  [77782.262000] [< ffffffff81151947 >]? cache_alloc_refill + 0x2f7 / 0 x 580

  [77782.262000] [< ffffffff8100be3b >] invalid_op + 0x1b/0 x 20

  [77782.262000] [< ffffffffa01b0a1f >]? vmxnet3_rq_rx_complete + 0x9bf/0xbc0 [vmxnet3]

  [77782.262000] [< ffffffffa01b01fe >]? vmxnet3_rq_rx_complete + 0x19e/0xbc0 [vmxnet3]

  [77782.262000] [< ffffffff81427c9c >]? dev_hard_start_xmit + 0x2bc/0x3f0

  [77782.262000] [< ffffffff81276950 >]? swiotlb_map_page + 0 x 0/0 x 100

  [77782.262000] [< ffffffffa01b0da3 >] vmxnet3_poll_rx_only + 0 x 53 / 0 x 110 [vmxnet3]

  [77782.262000] [< ffffffff8142bd62 >] net_rx_action + 0 x 102/0x2f0

  [77782.262000] [< ffffffff8106cde1 >] __do_softirq + 0xc1/0x1e0

  [77782.262000] [< ffffffff8100c1ac >] call_softirq + 0x1c/0 x 30

  [77782.262000] < EOI >

  [77782.262000] [< ffffffff8100ddb5 >]? do_softirq + 0xa0/65 x 0

  [77782.262000] [< ffffffff8106cc7a >] local_bh_enable + 0x9a/0xb0

  [77782.262000] [< ffffffff8142c0eb >] dev_queue_xmit + 0x19b/0x6f0

  [77782.262000] [< ffffffff814639b0 >]? ip_finish_output + 0 x 0 / 0 x 310

  [77782.262000] [< ffffffff81463aec >] ip_finish_output + 0x13c / 0 x 310

  [77782.262000] [< ffffffff81463d78 >] ip_output + 0xb8/0xc0

  [77782.262000] [< ffffffff8146303f >]? __ip_local_out + 0x9f/0xb0

  [77782.262000] [< ffffffff81463075 >] ip_local_out + 0 x 25/0 x 30

  [77782.262000] [< ffffffff81463550 >] ip_queue_xmit + 0 x 190 / 0 x 420

  [77782.262000] [< ffffffff8147821e >] tcp_transmit_skb + 0x3fe/0x7b0

  [77782.262000] [< ffffffff8147a5db >] tcp_write_xmit + 0x1fb/0xa20

  [77782.262000] [< ffffffff8147af90 >] __tcp_push_pending_frames + 0 x 30/0xe0

  [77782.262000] [< ffffffff8146a5de >] tcp_push + 0x6e / 0 x 90

  [77782.262000] [< ffffffff8146b5ba >] tcp_sendmsg + 0x64a/0xa20

  [77782.262000] [< ffffffff81417147 >] sock_aio_write + 0 x 167 / 0 x 180

  [77782.262000] [< ffffffffa020969d >]? hook_function + 0x1d/0 x 30 [hades_wd]

  [77782.262000] [< ffffffff81167a2a >] do_sync_write + 0xfa / 0 x 140

  [77782.262000] [< ffffffff8108aa50 >]? autoremove_wake_function + 0 x 0/0 40

  [77782.262000] [< ffffffff8105e1f0 >]? pick_next_task_fair + 0xd0 / 0 x 130

  [77782.262000] [< ffffffff811fe706 >]? security_file_permission + 0 x 16/0 20

  [77782.262000] [< ffffffff81167df4 >] vfs_write + 0 x 184/0x1a0

  [77782.262000] [< ffffffff81168711 >] sys_write + 0 x 51 / 0 x 90

  [77782.262000] [< ffffffff8100b072 >] system_call_fastpath + 0 x 16/0x1b

  [77782.262000] code: 00 00 00 c7 b4 83 00 00 00 00 00 00 00 31 c0 f1 83 01 88 8B b8 00 00 00 e9 1 c fb ff ff 48 83 bb c8 00 00 00 00 0f 85 5 has fb ff ff < 0f > 0 b eb fe 0f 0b eb fe 0f 0b 0f 1f 80 00 00 00 00 eb f7 b 8, 83

  [77782.262000] RIP [< ffffffffa01b0a1f >] vmxnet3_rq_rx_complete + 0x9bf/0xbc0 [vmxnet3]

  [77782.262000] RSP < ffff8800282037c8 >

  Crash-x86_64 > mod s vmxnet3 vmxnet.ko

  MOD: vmxnet3: could not find or load the file of the object: vmxnet.ko

  Crash-x86_64 > mod s vmxnet3 vmxnet3.ko

  MODULE SIZE OBJECT FILE NAME

  vmxnet3 60947 vmxnet3.ko ffffffffa01b7ac0

  Crash-x86_64 > gdb list * vmxnet3_rq_rx_complete + 0x9bf

  0xffffffffa01b0a1f is in vmxnet3_rq_rx_complete (/ tmp/build_rpm_sandbox.vy6fT4/BUILD/vmware-open-vm-tools-9.0.0/vmxnet3/vmxnet3_drv.c:1467).

  1462 PCI_DMA_FROMDEVICE);

  1463 rxd-> addr is cpu_to_le64 (rbi-> dma_addr);.

  1464 rxd-> len = rbi-> len;

  1465

  1466} else {}

  1467 BUG_ON (ctx-> skb == NULL & &! skip_page_frags);

  1468 / * buffer not SOP must be of type 1 in most cases * /.

  1469 BUG_ON (rbi-> buf_type! = VMXNET3_RX_BUF_PAGE);

  1470 BUG_ON (rxd-> CType! = VMXNET3_RXD_BTYPE_BODY);

  1471

  The line is added by the following validation https://github.com/torvalds/linux/commit/5318d809d7b4975ce5e5303e8508f89a5458c2b6.

  Any ideas?

  This seems more like problem open-vm-tools. Do you really need it? Vmxnet3 is supported by the kernel 2.6.32 for sources. And if you run versions incompatible kernel & open-vm-tools, you can get these problems...

  BTW, open-vm-tools is NOT the same as vmware-tools! In addition, your open-vm-tools are quite old (version 9.0.0). Branch current stable is 9.4.0, so maybe it's time to update (vmware-tools is still further, iirc in 9.6.x)...)

• vmxnet3 driver performance

  I'm looking to increase performance on our environment.

  We have 46 guests running a cluster consisting of 5 x version 5.1 esx host, DR.

  I plan the update to the hardware versions 7 to 9 of the guests for our database servers and know that this includes support for vmxnet3 driver with 10GB network connections.

  My question is, if the underlying hardware switch has only 1 GB of the physical switch ports. If the guests are on the same host they will communicate within the hypervisor at speeds of 10 GB or that it will always be limited to 1 GB.

  Any help would be appreciated.

  Thanks in advance

  Karl

  I plan the update to the hardware versions 7 to 9 of the guests for our database servers and know that this includes support for vmxnet3 driver with 10GB network connections.

  vmxnet3 is already supported since VM hardware version 7.

  My question is, if the underlying hardware switch has only 1 GB of the physical switch ports. If the guests are on the same host they will communicate within the hypervisor at speeds of 10 GB or that it will always be limited to 1 GB.

  Invited on the same host and vSwitch and port group are able to exceed any vNIC well beyond 1 Gbit/s you use. I know, we could think that for example the e1000, which has a link from 1 Gbps to the guest, is limited to 1 GB/s maximum. or vmxnet3 is limited to a maximum of 10 Gbps. But this isn't the case. They can easily exceed their "speed of the virtual link. Test it with a tool of network throughput as iperf a see for yourself.

  This is because only the true physically imposed restrictions do not apply in a virtualized environment between two virtual machines on the same host/port signalling group. Operating systems don't artificially restrict traffic to match agreed on the speed of the line, unless it is physically required.

  To give an example, I am able to reach 25 + Gbps between 2 Linux VM with vmxnet3 on the same host/network with iperf.

  The main advantage of the vmxnet3 vNIC is that it provides features of unloading and paravirtualization, which reduces the CPU load imposed by their high throughput. I'm under it years since 4.x on Windows and most Linux virtual machines as our standard vNIC.

• Better to use E1000 or VMXNET3

  I am trying to create the new virtual machine on ESXi 5.5 and I was curious to see what everyone recommends in what concerns network cards. I see vmxnet3 is the most recent one is reasonable to assume that I should use for all new virtual machines?

  Vmxnet3 is VMware's paravirtualized adapter, less overhead (so more speed) and 10 GbE connection. Only drawback, you have the VMware Tools installed in addition to all OS reviews ' her. So yes, I would go with that, but what guest operating system you try to virtualize?

• How can I specify the network adapter to be vmxnet3 molten?

  Hello

  I'm runnning a VM Cent-OS in Fusion that will not start if a vNIC is nothing else than vmxnet3.

  When I add an adapter through the merger user interface, it creates a type of e1000 and I can't find a way to change this option.

  Guessing that I need to probably change .vmx directly, but I would like to know exactly what I need to add.

  Thank you.

  You have now
  Ethernet*.virtualDev = "e1000".

  possible that the other settings are
  Ethernet*.virtualDev = "vlance" - it's the PCnet32
  Ethernet*.virtualDev = "vmxnet" - it's the old card vmxnet
  Ethernet*.virtualDev = "vmxnet3" - that's what you want
  Ethernet*.virtualDev = "e1000e" - a newer version of the E1000 using a PCI-express slot

  If you do not specify ethernet*.virtualDev you get the default "vlance.

• E1000 adapters cannot communicate on the network, but can't VMXNET3?

  I am trying to create a new environment vsphere with VCSA 5.5

  My VM VCSA (using a NIC VMXNET3) works very well and he communicates without problems.

  My 08r2 with a NETWORK E1000 card VM cannot. (is not DHCP, cant ping when the value static ip etc.). When I add a VMXNET3 NIC on the same machine, she immediately picks up DHCP and can ping etc.

  What continues? I can not just use the VMXNET3 NIC, as the 100 + VMs im going to migrate this environment are all set up with of the E1000 (ESXi 5.1)