Vms hang for up to a minute when these errors occured

[mechlord]

At first I had the VMs were on a SAN but now moved to local storage. The hanging happens to only the VMs that were P2V'd the "from scratch" ones don't have this issue.

The VMs hang or suspend for upto a minute..no issues on the guest...except for any network apps that require a steady connection drop when it hangs.

We've eliminated all network possiblities to I was sent to storage support and they got stumpped too so i'm reaching out to you guys to help me decipher this one.

vmkwarnings:

Sep 3 15:28:52 ESX2 vmkernel: 1:02:11:58.330 cpu3:4111)WARNING: SCSILinuxAbortCommand - The driver failed to call scsi_done f

rom itsabort handler and yet it returned SUCCESS

Sep 3 15:28:52 ESX2 vmkernel: 1:02:11:58.330 cpu3:4111)WARNING: SCSILinuxAbortCommands Failed, Driver ata_piix, for vmhba1

Sep 3 15:28:52 ESX2 vmkernel: 1:02:11:58.330 cpu3:4111)WARNING: ScsiHost: 813: Abort/Reset failed on handle 1185: Failure

Sep 3 15:29:02 ESX2 vmkernel: 1:02:12:08.388 cpu1:4110)WARNING: SCSILinuxAbortCommands Failed, Driver ata_piix, for vmhba1

Sep 3 15:29:02 ESX2 vmkernel: 1:02:12:08.388 cpu1:4110)WARNING: ScsiHost: 813: Abort/Reset failed on handle 1185: Failure

Sep 3 15:29:21 ESX2 vmkernel: 1:02:12:27.812 cpu6:4102)WARNING: ScsiCore: 1119: Invalid sense buffer: error=0x72, valid=0x0,

segment=0xb, key=0x0

(END)

vmk

Sep 3 15:28:51 ESX2 vmkernel: 1:02:11:57.318 cpu3:4111)ata_scsi_abort: ap 0x41000983d3e8, qc 0x41000983deb8, cmd 0x41000c0161

c0, tag 0, flags 10001, waiting for completion

Sep 3 15:28:51 ESX2 vmkernel: 1:02:11:57.318 cpu3:4111)ata_scsi_abort: ap 0x41000983d3e8, cmd 0x41000c0161c0 completed in 0 s

econds

Sep 3 15:28:51 ESX2 vmkernel: 1:02:11:57.324 cpu6:4208)<4>ata1.00: qc timeout (cmd 0xa0)

Sep 3 15:28:51 ESX2 vmkernel: 1:02:11:57.324 cpu6:4208)<3>ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen

Sep 3 15:28:51 ESX2 vmkernel: 1:02:11:57.324 cpu6:4208)<3>ata1.00: tag 0 cmd 0xa0 Emask 0x5 stat 0x51 err 0x20 (timeout)

Sep 3 15:28:52 ESX2 vmkernel: 1:02:11:58.330 cpu3:4111)ata_scsi_abort: ap 0x41000983d3e8, cmd 0x41000c0161c0, SUCCEEDED

Sep 3 15:28:52 ESX2 vmkernel: 1:02:11:58.330 cpu3:4111)WARNING: SCSILinuxAbortCommand - The driver failed to call scsi_done f

rom itsabort handler and yet it returned SUCCESS

Sep 3 15:28:52 ESX2 vmkernel: 1:02:11:58.330 cpu3:4111)WARNING: SCSILinuxAbortCommands Failed, Driver ata_piix, for vmhba1

Sep 3 15:28:52 ESX2 vmkernel: 1:02:11:58.330 cpu3:4111)WARNING: ScsiHost: 813: Abort/Reset failed on handle 1185: Failure

Sep 3 15:28:52 ESX2 vmkernel: 1:02:11:58.330 cpu0:4096)VMNIX: VmkDev: 2918: abort sn=9345, vmkret=bad0001.

Sep 3 15:28:57 ESX2 vmkernel: 1:02:12:03.328 cpu0:4096)VMNIX: VmkDev: 2966: abort failed.

Sep 3 15:28:57 ESX2 vmkernel: 1:02:12:03.328 cpu0:4096)VMNIX: VmkDev: 2873: a/r=4 cmd=0x0 sn=9345 dsk=vml0:0:0 reqbuf=0000000

000000000 (sg=0)

Sep 3 15:28:57 ESX2 vmkernel: 1:02:12:03.328 cpu1:4110)ata_scsi_abort: ap 0x41000983d3e8, qc 0x41000983deb8, cmd 0x41000c0161

c0, tag 0, flags 10001, waiting for completion

Sep 3 15:28:58 ESX2 vmkernel: 1:02:12:04.330 cpu6:4208)<4>ata1: port is slow to respond, please be patient (Status 0xd0)

Sep 3 15:29:02 ESX2 vmkernel: 1:02:12:08.388 cpu1:4110)ata_scsi_abort: ap 0x41000983d3e8, cmd 0x41000c0161c0, FAILED

Sep 3 15:29:02 ESX2 vmkernel: 1:02:12:08.388 cpu1:4110)WARNING: SCSILinuxAbortCommands Failed, Driver ata_piix, for vmhba1

Sep 3 15:29:02 ESX2 vmkernel: 1:02:12:08.388 cpu1:4110)WARNING: ScsiHost: 813: Abort/Reset failed on handle 1185: Failure

Sep 3 15:29:02 ESX2 vmkernel: 1:02:12:08.388 cpu0:4096)VMNIX: VmkDev: 2918: reset sn=9345, vmkret=bad0001.

Sep 3 15:29:21 ESX2 vmkernel: 1:02:12:27.320 cpu1:4487)UserProxy: 2098: Hit timeout (60000 ms) waiting for reply from proxy (

pid=16715).

[J1mbo]

Have any hardware specific components been removed from the P2V'd VMs, i.e. Insight or OpenManage Agents etc.?

[Joshua_Mally]

Try the steps listed here

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!

-Josh

Trying to learn

[mechlord]

nah, the servers are as generic as Dell servers can get, no open manage software either.

[mechlord]

Tried the commands (i' just learning this linux thing) and found my proc to be 4618 but when i ran the

1. less -S /proc/vmware/vm/4618/cpu/status the directory wasn't there....i browsed and the i had a 4619 and a bunch of other ones but not this one.

[admin]

For TEAC DV-28E-V DVD-ROM, there have been several issues. I suspect the VMs hanging are those which connect to the Physical Host CD-ROM device (check in Edit Settings). The hang occurs in the CD-ROM abort handler. The solution is to upgrade the firmware of this DVD-ROM.

You noted this was a Dell machine; take a look at http://support.dell.com/support/downloads/download.aspx?c=us&l=en&s=gen&releaseid=R184527&SystemID=P...

[hakou03]

Hello, I have the same problem with an exchange VM that i am debuging for the last 2 weeks

I finnaly find that the CD was pointing to "Host Device" :/vmfs/devices/genscsi/mpx:vmhba0:C0:T0:L0 that was bugging every hour.

the solution (for me) is to change the cd-rom device to client or DS iso fil.

[franko68]

Hi,

I also had this same problem with a Dell PowerEdge 2950 and can confirm that the solution was to unclick the connected option for the CD/DVD.

Slight ressurection, but wanted to add a few key words

Cheers guys