Jump to content

VMWare - VM gives PAE error on grey apple, PAEVM="TRUE" is in config file though


16 posts in this topic

Recommended Posts

I am sorry I did not elaborate more. Here's a bit more details on what exactly is going on.

 

Dell Lattitude D505 (Pentium M @ 1.6 GHz)

Host OS: XP SP2 with all updates

 

I'm using the JAS 10.4.6 ISO, I am using Daemon Tools to mount it. I have set up VMWare 5.5 according to all the different tutorials say it should be.

 

VMWare boots fine, and finds the Mac OS X ISO fine as well. I press any key to begin installation, and it starts to load Darwin/x86, and when the grey Apple screen appears, VMWare's virtual machine stops,

 

Here's the error I get:

*** BVMware Workstation internal monitor error (bug 9297) ***

 

The guest operating system you are running is using the Physical Address Extension (PAE) processor option. For more information about running PAE-enabled guest operating systems, please consult http://www.vmware.com/info?id=28

 

I have enabled PAE in my config file, though.

 

Here are the first four lines of my config file for this virtual machine:

paevm = "TRUE"

config.version = "8"

virtualHW.version = "4"

scsi0.present = "TRUE"

Link to comment
Share on other sites

  • 4 weeks later...

i have the same problem on my centrino laptop.

 

BUT works fine on a p4 workstation.

 

so i upgraded to sp2 (because PAE is enabled by default on sp2, and mofying the kernel args of NT on sp1 didn't change the problem)

but same problem.

 

PAE is enabled on my processor, because i can run osX Native :

 

 

But for some reason i can't install natively, (waiting for root...)

 

now i need to run the disk utility on the install dvd, but can't do it natively (no root), and can't do it thru vmware (pae bug).

Link to comment
Share on other sites

I'm getting the same error... I have paevm = "true" in my vmx file and gives that :D error...

 

I have an IBM R51 laptop Intel Pentium® M processor.

Using service pack 2.

 

Even tried editing the boot.ini to enable PAE

 

boot.ini ex:

[boot loader]

timeout=30

/PAE

default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS

[operating systems]

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect /NoExecute=OptIn

 

Works on My AMD pc... I even tried copying the Virtual machine from there... and still no good.

Anyone have ideas?

:D

Link to comment
Share on other sites

From what I can ascertain, the 400mHz Pentium-M chips do not support PAE. Just about every other recent Intel CPU does. This means that you cannot run Tiger in VMWare. I have a 1.8 Pentium-M (Dothan) and I have the same issues as you. Desktop P4 (Northwood) is fine. I haven't found a work around yet.

 

I can't report on how the 400mHz Pentium-M goes as far as a native install - I haven't attempted.

 

Hope this helps.

 

Cheers

Link to comment
Share on other sites

I 'think' it's just the 400mhz based dothans that don't have pae...the 533mhz based dothans have nx control as well, and many more people seem to have had success installing on them over the 400mhz ones...really, i don't know though, I'm still fighting my 1.7m (400mhz)...i dont even get kernel panics though, it just stops booting after recognizing the firewire.

Link to comment
Share on other sites

  • 5 months later...

i had the same trouble - but it was only due to me installing macosx for the first time - the installation went well but after reboot came a message, that guest OS shutted down the processor.

 

for me it has been solved by a simple thing - during last step of the instalation (before copying all the files) i didn't chose the patches for my processor to install, so i solved it by installing it once again with these patches checked.

Link to comment
Share on other sites

I also encountered this problem after trying to boot directly from iso dvd. (I've had the well known AppleIntelPIIXATA error during loading the installer).

 

So I decided to try it working via vmware. but after i mounted the iso with daemontools and started the virtual machine this error comes up.

 

Searching the forum results in editing the virtual machines config file ".vmx" with an additional key (PAEVM="TRUE"). Unfortunatelly this does'nt work.

 

Adding /PAE to boot.ini for a force start of PAE doesn't work either.

 

Does someone know whats the next thing to check to get this baby OSX'ed??

 

matthew

Link to comment
Share on other sites

I downgraded to 5.0 but i still get the error. What build of 5.0 are you running?

 

 

EDIT

-------------------------------------------------------------------------------------------

 

Oops, i forgot to add paevm= "TRUE". that fixed the issue. I am running 5.0.132. Thanks for the help

Edited by n0pa
Link to comment
Share on other sites

 Share

×
×
  • Create New...