Comments on: ESXi 5.1 U1 Purple Screen of Death

By: magander3

magander3 — Thu, 08 May 2014 05:47:36 +0000

In reply to Paul. Totally agree that all templates should be configured with VMXNET3 and if not using templates the automated and/or manual process of creating VMs should say VMXNET3 if possible. //Magnus

By: Paul

Paul — Wed, 07 May 2014 15:40:26 +0000

Thank you for this article. IMO VMWare should set default vNIC (while creating VM) to VMXNET3 instead of e1000.

By: magander3

magander3 — Tue, 06 May 2014 05:41:38 +0000

In reply to Tim. Thanks Tim, glad you liked it. Yes there are still quite a lot of vendors shipping their appliances without the VMXNET3 vNIC driver. //Magnus

By: Tim

Tim — Mon, 05 May 2014 22:16:57 +0000

It’s troubling that so many OVA’s from the likes of Firemon and Cisco are still shipped with E1000 NICs. In fact, some if these (e.g. Cisco ISE) won’t work with anything else. Makes it hard to get rid of E1000’s when vendors keep using them! Great article.

By: Newsletter: May 4, 2014 | Notes from MWhite

Newsletter: May 4, 2014 | Notes from MWhite — Mon, 05 May 2014 21:28:11 +0000

[…] and yet it isn’t enough. So I share things out too. But in any-case here is a good article about what happens if you are using the Intel E1000 with servers using various versions of […]

By: magander3

magander3 — Fri, 02 May 2014 06:44:00 +0000

In reply to khjerpe. Thanks Kenth

By: magander3

magander3 — Fri, 02 May 2014 06:43:42 +0000

In reply to wojcieh. Totally agree (as long as supported by guest OS)

By: khjerpe

khjerpe — Fri, 02 May 2014 06:16:43 +0000

Oneliner to find those bad bad E1000 VMs .. :
Get-vm | ?{Get-networkadapter $_ | where-object {$_.type -like “*e1000*” }}

By: wojcieh

wojcieh — Tue, 29 Apr 2014 20:43:50 +0000

Long live VMware best practices to always use vmxnet3.