VMware Cloud Community
brainslice
Enthusiast
Enthusiast

network performance stats not working with vmxnet3

It looks like my w2k8 VMs using vmxnet3 will not report network performance stats. When logged into vcenter on vsphere client "Network Rate" and "Network Packets" under the Performance tab show as "No data available" The other VMs (w2k8 included) using E1000 or Flexible nic will show the network performance stats just fine.

0 Kudos
6 Replies
NicholasFarmer
Enthusiast
Enthusiast

any update for this?

We are having the same issue.

Im sure the fix is to downgrade to vmxnet2 or lower

0 Kudos
Saadat
Enthusiast
Enthusiast

Hi,

I had the same problem and contacted VMware. The last word was they have included the fix in update 1.

He said Probably end of Oct or Nov.

http://www.linkedin.com/in/ernestsaadat
0 Kudos
Mxx
Contributor
Contributor

I had the same problem and contacted VMware. The last word was they have included the fix in update 1.

same problem here..

update 1 of what? esx(i), vcenter, tools, etc?

0 Kudos
Saadat
Enthusiast
Enthusiast

vSphere 4 update 1 (I believe VMware will syncronise the updates vCenter, ESX, ....). They want to avoid the problem that we had in ESX 3.x

when the update comes it will be for both ESX Server and vCenter Server. (I assume this)

Can Some one from VMware confirm it? That was the whole Point of matching the version numbers for vSphere. All start with 4 (even SRM which in reallity is version 1.5 - I think)

Now that VMware released VMware workstation 7 and VMware Player 3, I think next step will be update 1 on vSphere.

Thanks,

http://www.linkedin.com/in/ernestsaadat
0 Kudos
Mxx
Contributor
Contributor

well, i meant which specific component i'd have to update to fix this problem

(if it's a vcenter, i'd have to contact our parent organization, if it's just esx(i) or even vmware tools, i can do it on my own)

i'm surprised that people don't report this issue more commonly and that it wasn't fixed from the start..seems like such an obvious thing.

0 Kudos
LucasAlbers
Expert
Expert

This will be fixed in update1 which comes out in december.

The issue is not specific to vcenter, as you can see the same issue on a standalone machine.

0 Kudos