Unable to connect to the MKS: Error connecting to /bin/vmx process

So I rebuilt my lab a couple months back due to the prevalence of this error. Would prefer to not have to do that again. My best guess is the HDDs are overtaxed and can't service the VM. I have two WD Green 2TB drives configured as a single data store that are connected directly to the MB. Also have 2 or 3 server OSs on an SSD. I've tried powering off the VM but it is stuck at 95%. In the past hard resetting the host has resolved the issue but I dont view this as an acceptable solution would like to determine the root cause so as to remedy it rather than bandaid it. Not educated on which logs to look at.Online resources haven't been super helpful. I've also heard the Green drives can be problematic. Any advice?

Screenshot:

Sorry if it's too small.

I suppose if I can't resolve the problem I'll chalk it up to a storage error and shell out for this Whitebox SAN

Capture.jpg

Find more posts tagged with

Comments

tomtom1

You could kill the VMX process:

VMware KB: Powering off an unresponsive virtual machine on an ESX host

tstrip007

Don't know what version ESXi you have installed but have you tried the suggested patch? VMware KB: After reloading a virtual machine console access fails with the error: Unable to connect to the MKS: The operation is not allowed in the current state

tprice5

tomtom1 wrote: »

You could kill the VMX process:

VMware KB: Powering off an unresponsive virtual machine on an ESX host

I do not have vCenter installed as I have not been able to get my hands on 5.1 and 5.5 is giving me grief on the install. Everything is A-Okay when I am stepping through the installation. Once it finishes I plug the IP of the vcenter server into the browser and I get the vSphere web UI. The vCenter servers tab has a 0 next to it insinuating it doesn't see it. When I try and use vSphere to login to the vCenter server using the same credentials as the WebUI it denies connection. I've successfully installed vCenter 5.0. Not sure what step I am missing.

tstrip007 wrote: »

Don't know what version ESXi you have installed but have you tried the suggested patch? VMware KB: After reloading a virtual machine console access fails with the error: Unable to connect to the MKS: The operation is not allowed in the current state

I meant to double back and provide more info. I am running ESXi 5.1 So I need to upgrade to 5.5? Fun.

bensen

This is usually DNS.. Check your DNS configuration especially on the computer that has the vmware client you are running to connect to the vcenter

tprice5

bensen wrote: »

This is usually DNS.. Check your DNS configuration especially on the computer that has the vmware client you are running to connect to the vcenter

I am connecting by putting the IP of the ESXi host into vSphere on the client machine. No name resolution should be taking place so I don't see how it could be DNS.

Asif Dasl

This kb article suggests it's a corrupt VMX file - are you sure the hard drive the VM sits on is 100% ?

It suggests re-creating the VM configuration and re-using the VMDK files from the corrupt VM.

tprice5

Yeah I saw that one when I was initially troublshooting this. If the VMX was corrupt then why does it return to a normal state after a reboot? I am not positive the HDD is 100% but I have no reason to believe otherwise. I have blown away and recreated multiple VMs numerous times. This problem still seems to creep in. I am hoping an upgrade to 5.5 resolves everything.
Funny story, I went to upgrade on Sunday night and when I walked to my server I noticed the key was missing out of the front of the panel. My 2 year old had ran off with it and lost it! No way to open the front panel. I contacted Rosewill hoping for a replacement but my wife had found them sitting ontop of a heater behind our bedroom door. And I was || close to getting a new chasis!
Hopefully will get to upgrading tonight. I started last night but the Rufus Bootable USB creator site was down so that brought things to a halt.
We'll see if I get it right!