Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

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

Posted on 2009-04-06
3
Medium Priority
?
5,471 Views
Last Modified: 2012-08-13
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
Comment
Question by:smeek
3 Comments
 
LVL 21

Expert Comment

by:za_mkh
ID: 24082258
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
 
LVL 8

Accepted Solution

by:
smeek earned 0 total points
ID: 24187225
Found out that a stoarge array on which data was stored was having disk issues impacting the VMs.
Steve
 
0
 

Expert Comment

by:dwkrueger
ID: 27602143
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

NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
It’s time for spooky stories and consuming way too much sugar, including the many treats we’ve whipped for you in the world of tech. Check it out!
Teach the user how to rename, unmount, delete and upgrade VMFS datastores. Open vSphere Web Client: Rename VMFS and NFS datastores: Upgrade VMFS-3 volume to VMFS-5: Unmount VMFS datastore: Delete a VMFS datastore:
This Micro Tutorial steps you through the configuration steps to configure your ESXi host Management Network settings and test the management network, ensure the host is recognized by the DNS Server, configure a new password, and the troubleshooting…

972 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question