• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 5506
  • Last Modified:

ESX Error: A General System error occurred: Communication with the virtual machine may have been interrupted

I am new to Vmware and inherited a ESXi installation.

Everything has ran OK past 2 weeks.  Today a host was down and I tried to poer on.  I get error now on trying to Power On any machine.  Here is the error I get.

A General System error occurred: The System Returned an Error. Communication with the virtual machine may have been interrupted

I saw an article that suggested cleaning out \VAR folder cause of Dell OpenManage errors and box is running on a Dell PE2950.  Can anyone tell me best way to clear logs or help resolve this issue.
I also see an article about too much network load, but box was running on 2 10/100 NICs and I plugged them over to a gigabit switch a week ago.  Thanks for any help.
0
smeek
Asked:
smeek
1 Solution
 
za_mkhCommented:
I thought I posted a comment on this earlier, (three hours ago) but it didn't get posted! :(
I think you have a Service Console memory shortage issue. By default the memory assigned to the SC is 272Mb. When you add things like management agents, etc the SC runs out of memory and hence appears to stop responding. The way to fix this is to assign at least 512Mb to your SC at setup with your swap partition being double the size. Default swap size is 544Mb. 800Mb is the maximum you can assign to your SC
Look at this link on how to increase your SC memory. (increasing your swap partition could be very difficult, but I have not seen an issue when you increase SC to 512Mb).
http://www.experts-exchange.com/Software/VMWare/Q_24244826.html
This is for more background: http://communities.vmware.com/thread/153623
 
0
 
smeekAuthor Commented:
Found out that a stoarge array on which data was stored was having disk issues impacting the VMs.
Steve
 
0
 
dwkruegerCommented:
I got the same issue and resolved it by following the advice below.
For the first vm, I'd remove it from inventory, and add it back in using the datastore browser. If that still does not work, remove the drive from the vm settings, but do not delete it. After that is done, add the existing drive back into the settings. You should be able to boot back up.
Open datastore browser--> right click on *.vmx file-> click on "Add to inventory"

 
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now