To resolve this issue, you must investigate the reason why the host issued the Virtual Device Reset.
Typically, there are SCSI or other storage related errors before the virt-reset error message. These errors indicate the reason why the host needed to stop the I/O.
Here is an example of the errors that may precede a virt-reset condition:
2010-03-19T05:11:36.873Z cpu8:4104)ScsiDeviceIO: 2316:Cmd(0x412401bede80) 0x2a, CmdSN 0x17af1 to dev "naa.6006016036002e00e2d4aef30248e111" failed H:0x8 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.
2010-03-19T05:11:38.943Z cpu12:4108)ScsiDeviceIO: 2288:Cmd(0x412440f9b240) 0x8a, CmdSN 0x17af2 to dev "naa.6006016036002e00e2d4aef30248e111" failed H:0x8 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.
2010-03-19T05:11:38.943Z cpu20:19244)WARNING: J3: 2644: Error committing txn callerID: 0xc1d00006 to slot 0: IO was aborted by VMFS via a virt-reset on the device
In the above example, the I/O is being aborted as there is no response from the fabric or storage array to I/O requests (likely an underlying storage issue). This results in the virt-reset as I/O needs to be stopped on the VMFS file system.