- 论坛徽章:
- 0
|
Error Message Says Guest Trying to Use PAE
Details
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?
Solution
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://ww.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.
Product Versions
VMware Workstation 5.5.x (Windows hosts)
VMware Workstation 5.0.x (Windows hosts)
VMware Workstation 5.5.x (Linux hosts)
VMware Workstation 4.x (Windows hosts)
VMware GSX Server 2.0.x (Windows hosts)
VMware Workstation 5.0.x (Linux hosts)
VMware GSX Server 2.0.x (Linux hosts)
VMware Workstation 4.x (Linux hosts)
VMware GSX Server 2.5.x (Linux hosts)
VMware Server 1.0.x (Windows Hosts)
VMware Server 1.0.x (Linux Hosts)
VMware VMware ACE 1.0.x
Keywords
1539; WS500; vsbetad; urlz
看了,没看明白具体怎么解决 |
|