I have installed 10.9.3, all work perfectly, nice tut
Posted 11 July 2014 - 02:38 AM
Posted 12 July 2014 - 01:08 PM
Hoping for some help...I was having some weird issues with my 10.9 install on ESX 5.5...it was going to the dreaded gray screen on logout and nothing could be done but reboot.
I updated my ESXi 5.5 with all latest patches and updated the unlocker to 1.3.
Then, I did a fresh install of 10.9 from the .dmg and everything looked fine.
Installed VMWare Tools, rebooted...fine
Installed guestd_patches.pkg, rebooted....fine
Installed VMsvga2_v1.2.5_OS_10.9.pkg, rebooted...and now instead of a login screen I just have a black screen with a pointer.
I restored a snapshot and I'm ok...but I'd like to have the VMsvga2_v1.2.5_OS_10.9.pkg installed if possible.
UPDATE: I reapplied both patches to my reverted snapshot and the same thing occurs. Then, I tried to install just VMsvga2_v1.2.5_OS_10.9.pkg without guestd_patches.pkg. That resulted upon the grey apple screen on reboot with a stuck spinner...even after another cold boot.
UPDATE2: Cold rebooted again from a stuck black screen and now it's stuck on the grey screen... so not sure if the guestd_patches.pkg had any real impact to the change in issues I'm seeing.
UPDATE3: Safe mode boot (shift) works.. so likely a kext?
Ok..no more updates until someone can offer me some advice. TIA!
Ok...so I went ahead and applied the following to my .VMX file (from front page):
svga.autodetect = "FALSE"
svga.vramSize = "16384000"
Now it doesn't really seem to say anywhere that applying these settings are mandatory, but rather an option. However I am sure that this is the difference between me having the issue and not.
So...can someone confirm if these are supposed to be *required* for this to work and what exactly they are doing that would make the difference?
While I'm still awaiting the answer on the above, I have another (possibly related) issue?
As I mention I'm running this on ESXi 5.5 and I continuously am getting the following errors in my system log:
2013-11-23 18:37:06 -0600 WindowServer: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fcf60518790) - disabling OpenGL
I've looked around and it seems like this is a common enough problem with no real solutions. I did however find this page:
The poster there states this:
"Ok, I have eliminated the _CGXGLDisplayContextForDisplayDevice error by removing the 10.7.2 GMA950 kexts, and entering 0x27A28086 into AppleIntelHD3000Graphics.kext/Contents/Info.plist, thus linking the 10.8.4 WindowServer & CGX library into a modern Mavericks native driver/kext."
Now he is installing on actual older Mac hardware, not a VM...but I'm wondering if he is onto anything re: a solution. I'm still a bit of a neophyte when it comes to hardware on Macs, so just asking someone for input in translating this and if it might be applicable to VM as well to eliminate the error.
Posted 06 September 2014 - 03:00 PM
Update for VMware Tools attached to VMware Fusion 7.0.0
- VMwareGfx.kext now supports all 2D-acceleration features found in VMsvga2 with OS 10.9.x. VMsvga2 is no longer in development. Therefore, I suggest using VMwareGfx.kext in the future - as it's maintained by VMware.
- guestd_patches no longer work if installed on top (as a patch to) VMware Tools 7.x - the patch crashes vmware-tools-daemon. Therefore, if you want to continue using the patch, need to do it on earlier VMware Tools.
- It is possible to inject an EDID with VMwareGfx.kext as follows
- Edit VMwareGfx.kext/Contents/Info.plist and add the EDID as in following example (added VMW,EDID key)
<key>VMware SVGA II as a PCI device</key> <dict> <key>CFBundleIdentifier</key> <string>com.vmware.kext.VMwareGfx</string> <key>IOClass</key> <string>VMwareGfx</string> <key>IOUserClientClass</key> <string>VMwareGfxUserClient</string> <!-- Personality "1" of IONDRVSupport.kext (Apple's default framebuffer driver) matches the device with: IOProviderClass: IOPCIDevice IOMatchCategory: IOFramebuffer IOProbeScore : 20000 To make this driver start instead of Apple's driver, we must win the matching process by using the same IOProviderClass and IOMatchCategory values, and a higher IOProbeScore value. --> <key>IOProviderClass</key> <string>IOPCIDevice</string> <key>IOPCIPrimaryMatch</key> <string>0x040515AD</string> <key>IOMatchCategory</key> <string>IOFramebuffer</string> <key>IOProbeScore</key> <integer>30001</integer> <key>VMW,EDID</key> <data>[Insert base64 encoded EDID here]</data> </dict>
- Unfortunately, modifying Info.plist in VMwareGfx.kext renders its code signature invalid. So it needs to be added as an exception to /S/L/E/AppleKextExcludeList.kext/Contents/Info.plist as follows
[Near end] <key>com.vmware.kext.VMwareGfx</key> <string>1111.0</string> <key>com.apple.driver.KextExcludeList</key> <string>1111.0</string> </dict> </dict> </plist>
- non@me likes this
2 user(s) are reading this topic
0 members, 2 guests, 0 anonymous users