This is an issue in the vmxnet3 device emulation (ESX 6.5) and will be
fixed in the next update.
In the meantime, suggested workaround:
- disable rx data ring: ethtool -G eth? rx-mini 0
The issue should not be hit if using HW version 12 or older (with any
kernel) or with kernel older than 4.8 (a
My VMs are running hwversion 13 on 6.5 (for several days now), but
haven't hit this issue yet.
Thanks for the vmss, cryptz.
To analyze this, also need access to ex.vmem, could you please provide
that? It should have been created in the same directory as vmss when you
suspended the VM.
Do you how
I could not repro this issue locally despite running traffic for several
hours.
If you hit the issue again, could you please generate vmss file when the
VM is in the panic state? It can be obtained by suspending the VM in the
panic state and then locating the vmss file in the director of the
virtu
3 matches
Mail list logo
