Unable to connect to the MKS: The operation is not allowed in the current state

[aakalan]

Hi All,

After upgrading vmware tools we have a problem while backing up a vm guest with avamar. VM freezes and it says; "Unable to connect to the MKS: The operation is not allowed in the current state".  it can be only stopped by killing the task on the service console on the esx host.

VMware vCenter Server 5.1 -  5.1.U1b-1235232

2013-12-19T00:49:15.146Z| vcpu-1| W110: MONITOR PANIC: vcpu-0:NOT_IMPLEMENTED devices/vide/iovmk/videVMK-vmkio.c:1492

2013-12-19T00:49:15.156Z| vcpu-1| I120: Core dump with build build-1065491

2013-12-19T00:49:15.156Z| vcpu-0| I120: Exiting vcpu-0

2013-12-19T00:49:15.156Z| vcpu-1| W110: Writing monitor corefile "/vmfs/volumes/4ff12f8d-9d4d7a89-9341-e4135bb796b4/TEADEV/vmmcores.gz"

2013-12-19T00:49:15.202Z| vcpu-1| I120: Saving anonymous memory

2013-12-19T00:49:15.209Z| vcpu-1| W110: Dumping core for vcpu-0

2013-12-19T00:49:15.209Z| vcpu-1| I120: CoreDump: dumping core with superuser privileges

2013-12-19T00:49:15.209Z| vcpu-1| I120: VMK Stack for vcpu 0 is at 0x412248155000

2013-12-19T00:49:15.209Z| vcpu-1| I120: Beginning monitor coredump

2013-12-19T00:49:16.454Z| vcpu-1| I120: End monitor coredump

2013-12-19T00:49:16.455Z| vcpu-1| W110: Dumping core for vcpu-1

2013-12-19T00:49:16.455Z| vcpu-1| I120: CoreDump: dumping core with superuser privileges

2013-12-19T00:49:16.455Z| vcpu-1| I120: VMK Stack for vcpu 1 is at 0x4122481d5000

2013-12-19T00:49:16.455Z| vcpu-1| I120: Beginning monitor coredump

2013-12-19T00:49:17.420Z| vcpu-1| I120: End monitor coredump

2013-12-19T00:49:17.421Z| vcpu-1| W110: Dumping extended monitor data

2013-12-19T00:49:31.966Z| vcpu-1| W110: A core file is available in "/vmfs/volumes/4ff12f8d-9d4d7a89-9341-e4135bb796b4/TEADEV/vmx-zdump.000"

2013-12-19T00:49:31.966Z| vcpu-1| I120: Msg_Post: Error

2013-12-19T00:49:31.966Z| vcpu-1| I120: [msg.log.error.unrecoverable] VMware ESX unrecoverable error: (vcpu-1)

2013-12-19T00:49:31.966Z| vcpu-1| I120+ vcpu-0:NOT_IMPLEMENTED devices/vide/iovmk/videVMK-vmkio.c:1492

2013-12-19T00:49:31.966Z| vcpu-1| I120: [msg.panic.haveLog] A log file is available in "/vmfs/volumes/4ff12f8d-9d4d7a89-9341-e4135bb796b4/TEADEV/vmware.log".

2013-12-19T00:49:31.966Z| vcpu-1| I120: [msg.panic.requestSupport.withoutLog] You can request support.

2013-12-19T00:49:31.966Z| vcpu-1| I120: [msg.panic.requestSupport.vmSupport.vmx86]

2013-12-19T00:49:31.966Z| vcpu-1| I120+ To collect data to submit to VMware technical support, run "vm-support".

2013-12-19T00:49:31.966Z| vcpu-1| I120: [msg.panic.response] We will respond on the basis of your support entitlement.

[john23]

Check this kb...

kb.vmware.com/kb/749640‎

I have tried to check, its not working for me....

[aakalan]

Hi @john23 thanks for reply.

I've also checked this kb, i think this is not my problem. its not working for me.

Thanks,

[dhanarajramesh]

somehow, some times the UDP 902 connection was not establishing properly between vcenter to esxi. so what I have done, I have restarted the management services and it was successful. try this and it will not affect any thing.

[aakalan]

Hi dhanarajramesh thanks for reply.

We try to restart management services but the problem still here. I think this is a bug.

[dhanarajramesh]

so is this for only particular vm guest or for all  VMs? if it is for particular VM could you please check the hardware version and if it is old please upgrade to the latest.

[aakalan]

we have 1500 vm guest. we upgrade vmware tools severally. now 700 machine's upgrade complete and we have 3 guest have this problem

[dhanarajramesh]

in these 3 guest what kind of OS been installed and is there any graphical drivers are installed?

[aakalan]

No graphical drivers installed. but the 3 guest is converted from physical machine. i try to delete all the useless drivers. And try to clone machine. but the problem still occured.

[King_Robert]

The operation is not allowed in the current connection state of the host.”

The workaround is to restart the vCenter Server services. Here’s how:

1)  login to the vCenter appliance administrative interface
From your browser, replace vcenter with the name or IP address of your vCenter appliance:
http://vcenter:5480

2)  restart the vCenter service
a) First, click Stop (which will kick off any active vSphere Client sessions)

b) and when it’s done stopping, click Start, wait for it to finish starting

3)  login
Login in to vCenter again, with your vSphere client

4)  try to power up your VM again, it should work fine this time

I’d rather have a proper, permanent fix to this intermittent issue. If you’ve located a fix, please let us know by commenting below. But for now, at least I have a non-disruptive workaround. Well, the hosts and VMs stay up, but the sysadmin(s) may be a bit annoyed when you bump them.

[aakalan · Accepted solution]

We realized that the problem is our firewall checkpoints url filtering service. when we disabled it everything starts to working fine.