[an error occurred while processing this directive] Memory Issues No resource found

No resource found

RequestURI=/support/inc/support_header.html

Servlet= /apps/sling/servlet/errorhandler/404.jsp


ApacheSling/2.4 (jetty/9.2.9.v20150224, Java HotSpot(TM) 64-Bit Server VM 1.8.0_74, Linux 3.10.0-327.10.1.el7.x86_64 amd64)
No resource found

No resource found

RequestURI=/support/inc/support_nav.html

Servlet= /apps/sling/servlet/errorhandler/404.jsp


ApacheSling/2.4 (jetty/9.2.9.v20150224, Java HotSpot(TM) 64-Bit Server VM 1.8.0_74, Linux 3.10.0-327.10.1.el7.x86_64 amd64)
 
VMware ESX Server 1.5 Troubleshooting
  [an error occurred while processing this directive]Knowledge Base Troubleshooting

previous Prev   Contents   Last   Next next

Memory Issues

Memory Issues

The following sections will help you diagnose and correct problems you may encounter when using memory.

When I try to start a new virtual machine, ESX Server says I don't have enough memory.

When I try to start a new virtual machine, ESX Server says I don't have enough memory.

See How the System Uses Memory in the ESX Server manual for more information on how ESX provides memory to a virtual machine when you start it.

I used vmkfstools to add a second swap file to my ESX Server system, but the system is not taking advantage of the extra swap space.

I used vmkfstools to add a second swap file to my ESX Server system, but the system is not taking advantage of the extra swap space.

ESX Server 1.5 uses only one swap file - the first swap created on the computer. Although you can create additional swap files, ESX Server 1.5 does not use them. You may safely delete the extra swap file to free the disk space.

previous Prev   Contents   Last   Next next

No resource found

No resource found

RequestURI=/support/inc/footer.html

Servlet= /apps/sling/servlet/errorhandler/404.jsp


ApacheSling/2.4 (jetty/9.2.9.v20150224, Java HotSpot(TM) 64-Bit Server VM 1.8.0_74, Linux 3.10.0-327.10.1.el7.x86_64 amd64)