Vmware Fusion and Parallels Crash w/ 10.5.2 nvidia drivers

[soul1239]

Greetings,

 

I have a Kalyway 10.5.1 install (w/ only new 10.5.2 nvidia drivers) successfully working for almost all apps (ran into issues w/ 4gb of ram causing kernel panic but the maxmem kernel flag helped resolve that (per this post)).

 

Anyway, Parallels and Vmware Fusion are the only two applications that give me the grey screen of death. I'm guessing this could be because i'm running the new 10.5.2 nvidia display drivers for my 8600gt. Has anyone experienced something similar or am I looking in the wrong spot? I also tried using debug mode for Vmware but it didn't seem to make a difference. I get the grey screen of death at various spots in the install.

 

All I need is a windows VM for newsbin and some other key apps, thanks a ton.

 

My rig:

 

1.86ghz core2duo

asus p5b

4gb ddr800 (maxmem=3456)

8600gt

[Kilopopo]

me too can someone help!

[magomerlino]

Greetings,

 

I have a Kalyway 10.5.1 install (w/ only new 10.5.2 nvidia drivers) successfully working for almost all apps (ran into issues w/ 4gb of ram causing kernel panic but the maxmem kernel flag helped resolve that (per this post)).

 

Anyway, Parallels and Vmware Fusion are the only two applications that give me the grey screen of death. I'm guessing this could be because i'm running the new 10.5.2 nvidia display drivers for my 8600gt. Has anyone experienced something similar or am I looking in the wrong spot? I also tried using debug mode for Vmware but it didn't seem to make a difference. I get the grey screen of death at various spots in the install.

 

All I need is a windows VM for newsbin and some other key apps, thanks a ton.

 

My rig:

 

1.86ghz core2duo

asus p5b

4gb ddr800 (maxmem=3456)

8600gt

 

I have the same problem with vmware and parallels. As you can see in my signature, I have an 8600 gt 256 mb, I'm using the video driver based on 9c23 beta release but the problem still remain.

I read the system logs and I found an error related to the NTFS volume. I do not know if it really matters but this kind of error should be fixed wit the 10.5.2 relase. My opinion is that the drivers based on the new framework does not work well because the complete new framework is missing.

 

Lot of people have the same our problem as you can see in the virtualization forum. I could not find any solution to this yet.

 

keep in touch and please post news in the official vmware thread.

bye

[lord_muad_dib]

everyone has this problem, wait for 10.5.2 or a fix from vmware

[magomerlino]

I have the same problem with vmware and parallels. As you can see in my signature, I have an 8600 gt 256 mb, I'm using the video driver based on 9c23 beta release but the problem still remain.I read the system logs and I found an error related to the NTFS volume. I do not know if it really matters but this kind of error should be fixed wit the 10.5.2 relase. My opinion is that the drivers based on the new framework does not work well because the complete new framework is missing.Lot of people have the same our problem as you can see in the virtualization forum. I could not find any solution to this yet.This evening I'll try the maxmem option and let you know the result.keep in touch and (if you find a definitive solution) please post news in the official vmware thread. We can help others to solve the problem.bye

PS: have you tried to allocate less memory in the maxmem statement? Lots of people solved their problem using different amount of memory

everyone has this problem, wait for 10.5.2 or a fix from vmware

the problem is not related to vmware only. The kernel panic also happens using parallels. I can't wait to upgrade to 10.5.2!!!

[muitommy]

i think the problems are not relate to leopard, becasue my toh install work for vmware and parallels flawlessly,

that's something relate to Kalway's install ...

[spanakorizo]

problem: kalyway 10.5.1 dvd+10.5.2 kexts

many things crash ,it's not only paralers and vmware

we need to find out why

but 1st let's wait for the final 10.5.2 update from apple those days

the crash will be 80% just a hang screen with nothing moves ,and sometimes the grey screen kernel panic (you need to shutdown your computer etc etc...)

 

 

also please look at this thread i started from the 1st days that 10.5.2 beta files leaked

http://forum.insanelymac.com/index.php?sho...c=78155&hl=

[magomerlino]

problem: kalyway 10.5.1 dvd+10.5.2 kexts

many things crash ,it's not only paralers and vmware

we need to find out why

but 1st let's wait for the final 10.5.2 update from apple those days

the crash will be 80% just a hang screen with nothing moves ,and sometimes the grey screen kernel panic (you need to shutdown your computer etc etc...)

 

 

also please look at this thread i started from the 1st days that 10.5.2 beta files leaked

http://forum.insanelymac.com/index.php?sho...c=78155&hl=

 

how many gigs of system memory do you have? have you tried the maxmem option when booting the system?

My opinion is that not all of the crashes depend on kalyway 10.5.1 dvd+10.5.2 kexts.

Some of them are related to the system memory management others are related to the new framework that is unstable.

But it is just my point of view.

bye

[spanakorizo]

i have 4 gig of ram

what do you mean by maxmem?

i have 4,it use 4

[mac_cute]

Well guys,I only can say that is not a RAM problem.I have my Fusion on 10.5.1 and it work very fine. As spanakorizo posted,may be the kalyway 10.5.1 dvd + 10.5.2 kext combination that is causing all these hangs...

[magomerlino]

Well guys,I only can say that is not a RAM problem.I have my Fusion on 10.5.1 and it work very fine. As spanakorizo posted,may be the kalyway 10.5.1 dvd + 10.5.2 kext combination that is causing all these hangs...

 

sorry guys by I can confirm that in my case the problem was related to the memory management.

As you can see in this post lots of people solved the problem of the memory beyond 2 gigs.

The problem for me and others 'WAS' the management of the system memory.

Some of them just insert the maxmem flag in the boot.plist in order to reduce the use of the RAM memory.

Someone phisically removed the sim from the mother board.

Other people suggested to add the maxmem=xxxx flag (where xxxx is the limit of memory that the system can use) For futher information please read the post above.

I tried using two different amounts of memory without any success

 

Then I disabled the 'memory remapping' feature in the bios setting as suggested by another person. In my ASUS p5b-vm mainboard I can find this option under 'Advanced -> chipset -> memory remapping'

 

The result is that vmware fusion works well!!! I started vista 64bit in bootcamp mode and it started without any problem (I could not even complete the boot process before changing the bios setting).

I also installed and run Photoshop CS3 without any problem (bofore the changes it did freeze the system few minutes after I started it)

 

In my opinion (and a least in my case) the problem was related to the system management of memory. Next test I'll do this evening is burning a DVD using TOAST (it also panic the system)

Please try to use the same setting in order to fix the issue and let me know if it work.

thanks and bye

 

PS the only problem is that winzozz vista 64 can only recognize 2 gigs of memory (without enabling the memory remapping option in the bios).

Who cares!!!! I'm going to move to Leopard if everything works fine!!!!

[cyclonefr]

I use VMWare a lot (and using 10.5.2 kexts obviously since I have a G92) and I didn't notice any hang (while I had a lot with 10.5 / 10.5.1 kexts with my old G80).

 

I'm using 2GB BTW and I suggest you check that RAM thing, it seems people are having lots of problems with more than 2GB on a P35 chip.

[Bobur]

Have you tried the newest drivers?

[magomerlino]

I installed and used Toast 8 titanium to burn a DVD. It work great!!

No more kernel panic since I changed the memory settings.

[Bobur]

<SNIP>Then I disabled the 'memory remapping' feature in the bios setting as suggested by another person. In my ASUS p5b-vm mainboard I can find this option under 'Advanced -> chipset -> memory remapping'

 

<SNIP>

PS the only problem is that winzozz vista 64 can only recognize 2 gigs of memory (without enabling the memory remapping option in the bios).

Who cares!!!! I'm going to move to Leopard if everything works fine!!!!

 

 

Hopefully the reason Vista only see's 2GB with this option off is because it was installed with the option on. It would be interesting for someone to try a reinstall and see if it will see all 4GB with this option off.

[magomerlino]

Hopefully the reason Vista only see's 2GB with this option off is because it was installed with the option on. It would be interesting for someone to try a reinstall and see if it will see all 4GB with this option off.

 

unfortunately it does not work this way. When I first installed vista 64bit, my PC had already 4 gigs of RAM. After the installation I soon relalized the the OS was unable to recognize all of the amount of RAM. So I begun looking for a solution.

That's why I know that the 'memory remapping option' must be enabled in the bios.

You can also google 'memory remapping' and find microsoft explanation about this issue.

 

When I boot the system I can see 2 gigs of RAM recognized by the BIOS (if remapping is disabled) and the Microsoft OS is not able to understand that the real amount is 4 gigs.

To recognize the exact amount you need:

1) a 64 bit OS

2) the remapping enabled

 

Leopard does much better: even if the bios just sees 2 gigs, the Apple OS sees 4 gigs correctly!! That's great!!!

[Bobur]

Leopard does much better: even if the bios just sees 2 gigs, the Apple OS sees 4 gigs correctly!! That's great!!!

 

I wouldn't consider Leopard better when the way it is supposed to work causes Leopard to have kernel panics!

 

At least windows works fine with only 2GB and doesn't crash

[magomerlino]

I wouldn't consider Leopard better when they way it is supposed to work causes Leopard to have kernel panics!

 

At least windows works fine with only 2GB and doesn't crash

 

yes but LEopard is designed to work with the original Apple hardware. We cannot run leopard on an x86 hardware and complain because it is not stable.

 

Actually leopard works fine (on my pc) with 4gb without enabling any special feature in the bios.

[soul1239]

I turned off the memory-remap and was able to install an XP VM in VMware successfully. Thanks for the heads up on that BIOS flag, hopefully the 10.5.2 update will fix this as it sucks to switch it to use all 4 gb in Vista.

[magomerlino]

I turned off the memory-remap and was able to install an XP VM in VMware successfully. Thanks for the heads up on that BIOS flag, hopefully the 10.5.2 update will fix this as it sucks to switch it to use all 4 gb in Vista.

 

I'm glad you solved that problem.

next target is to use the memory remap and have a stable leopard environment.

Hope it will be with the next 10.5.2 release!! I can't wait!!!

[gkrangers]

I have the same VMware Fusion problem on a Kalway 10.5.1 upgrade to 10.5.2, and on iATKOS 2.0 (10.5.2).

 

VMware Fusion 1.1 and Beta 2 have the issue.

 

If I start up VMware right after I boot up OS X, it'll run fine. However, if I start up VMware some time later (I'm not sure how long, or if it has to do with other programs starting/running), I get the grey screen hard lock up.

 

I do have a 8800GT (G92), a P35 board, and 4GB of RAM.

 

I haven't tried Parallels yet.

[rtomek]

I upgraded to 4GB and would have never thought that it was the memory remap feature causing all of my problems! Thanks for the help, VMWare fusion works great again.

 

edit: My motherboard finds 3200MB of RAM now instead of the full 4GB, but OSX finds it. The other computer, the BIOS only finds 1GB of RAM but OSX finds the full 2GB. I guess that the memory remap feature needs to be turned off for all hackintoshes.