• admin
• Jul 3,2008
• In: Software & Tools

VMWare Internal Monitor Error bug 9297

For those having problem like this

“While I was trying to install a guest operating system, or upgrade an existing legacy virtual machine, my VMware product displayed a message that said the guest operating system was trying to use PAE. How can I correct the problem?”

or

***VMware Workstation internal monitor error (bug 9297)***
The guest operating system you are running is using the Physical Address Extension
(PAE) processor option.

Below are two situations in which this error message appears:

• The host computer has a processor that includes NX (no execute) or XD (execute disable) technology, the host operating does not support the NX or XD bit, and the guest operating system makes use of the NX or XD bit.Affected guest operating systems include Windows XP SP2, Windows Server 2003, Red Hat Enterprise Linux 4, Red Hat Enterprise Linux 3 Update 3, and Solaris 10.

  The NX technology is present in AMD processors including Athlon64, Opteron, and Sempron. The XD technology is present in Intel EMT64-capable processors.

• You start a virtual machine created by VMware ESX Server, VMware GSX Server 2.0.1 or earlier, or VMware Workstation 3.x or earlier.

To resolve the issue:

• If you have a NX technology-enabled system, change or upgrade the host operating system to one that supports the NX or XD bit.
• If your host operating system is not PAE-enabled, but the guest is, power off the virtual machine and use a text editor to edit  the VMX file (.vmx) for the affected virtual machine.

  Search for a line beginning with:
  paevm =
  
  If the line appears, change it to:
  paevm = “TRUE”

  If the line does not exist, add it with the value of true as shown in the above example.

You can then power on the virtual machine and run a PAE enabled guest operating system in it.

For more information about editing the virtual machine’s configuration file, see http://kb.vmware.com/kb/1714.

Note: If you run the Microsoft Application Compatibility Toolkit on a Windows XP Service Pack 1 system that has VMware Workstation 5 installed, the Application Compatibility Toolkit identifies Workstation as a program that has problems on Windows XP Service Pack 2. It identifies Workstation because of the issue described in this article. The workarounds described in this article resolve the issue.

Related Article

• January 7, 2010 -- VMware ESX Error Init 461 The Execute Disable No Execute CPU (0)
• December 2, 2008 -- How to load a Ghost (gho) images in VMware (0)
• October 20, 2008 -- VMware-authd.exe slowing down my system (0)