Jump to content

Workstation 11/12, Player 7/12, Fusion 7/8 and ESXi 6 Mac OS X Unlocker 2


Donk
 Share

688 posts in this topic

Recommended Posts

I'm on win7 x64, i have UAC disabled.

 

used unlocker202, removed lines 8-11 from win-install.cmd to make it run.

upgraded the 10.9 virtual machine, i added smc.version = 0 in the mavericks .vmx

 

all good, thanks!

Link to comment
Share on other sites

With hardware compatible mode for workstation11, I added vmx smc.version = "0" in .vmx.

Mavericks and Yosemite work good.

But, Snow Leopard (not Server) occurred boot time error "The guest operating system is not MAC OS X Server" and turn off.

Anyone have a good idea?

 

Workstation11, patched unlocker 2.0.2.

  • Like 1
Link to comment
Share on other sites

With hardware compatible mode for workstation11, I added vmx smc.version = "0" in .vmx.

Mavericks and Yosemite work good.

But, Snow Leopard (not Server) occurred boot time error "The guest operating system is not MAC OS X Server" and turn off.

Anyone have a good idea?

 

Workstation11, patched unlocker 2.0.2.

 

As per the readme file, I haven't found how to bypass the OS X Server check..

Link to comment
Share on other sites

Hello,

 

I previously had VMware Workstation 10 on a Ubuntu Linux 12.04 LTS and upgraded (by uninstalling the reinstalling everything from scratch) to VMware Workstation 11 with Unlocker 2.0.2 yesterday. However, I can't properly use my OSX virtual machine from now on. Indeed, the VM crashes every 5 or 10 minutes and the following error message appears:

 
VMware Workstation unrecoverable error: (vcpu-0)
Unexpected signal: 11.
A log file is available in /home/...

post-1362041-0-04118400-1419270019_thumb.png

 

Do you have any idea about this kind of bug ? I attached here the error message and some logs.

 

Kind regards,

 

Extracted from vmware.log:

2014-12-22T18:06:51+01:00[+0.010]| vcpu-0| W110: Caught signal 11 -- tid 9424 (addr 0)
2014-12-22T18:06:51+01:00[+0.010]| vcpu-0| I120: SIGNAL: rip 0x0 rsp 0x7fbb3c44abc8 rbp 0x4
2014-12-22T18:06:51+01:00[+0.010]| vcpu-0| I120: SIGNAL: rax 0x0 rbx 0x1edef58 rcx 0x18 rdx 0xc9b860 rsi 0x7fbb3c44ac70 rdi 0x7fbae0021210
2014-12-22T18:06:51+01:00[+0.010]| vcpu-0| I120:         r8 0x1ec4398 r9 0x24d0 r10 0x0 r11 0x3246 r12 0x164 r13 0x7fbb4365eec0 r14 0x1a76e50 r15 0x7fbb4365eec0
2014-12-22T18:06:51+01:00[+0.010]| vcpu-0| I120: SIGNAL: stack 7FBB3C44ABC8 : 0x0000000000738a2d 0x0000000000000000
2014-12-22T18:06:51+01:00[+0.010]| vcpu-0| I120: SIGNAL: stack 7FBB3C44ABD8 : 0x0000000000000000 0x000000044361df00
2014-12-22T18:06:51+01:00[+0.011]| vcpu-0| I120: SIGNAL: stack 7FBB3C44ABE8 : 0x0000000001edaa00 0x0000000001edaa00
2014-12-22T18:06:51+01:00[+0.011]| vcpu-0| I120: SIGNAL: stack 7FBB3C44ABF8 : 0x00007fbb4362f3c0 0x0000000000000004
2014-12-22T18:06:51+01:00[+0.011]| vcpu-0| I120: SIGNAL: stack 7FBB3C44AC08 : 0x0000000400b13c16 0x00007fbb4365eec0
2014-12-22T18:06:51+01:00[+0.011]| vcpu-0| I120: SIGNAL: stack 7FBB3C44AC18 : 0x00007fbae001af00 0x0000000000000000
2014-12-22T18:06:51+01:00[+0.011]| vcpu-0| I120: SIGNAL: stack 7FBB3C44AC28 : 0x0000000000000000 0x00007fbb4362f3c0
2014-12-22T18:06:51+01:00[+0.011]| vcpu-0| I120: SIGNAL: stack 7FBB3C44AC38 : 0x00007fbb4361df00 0x00000000013cd400
2014-12-22T18:06:51+01:00[+0.011]| vcpu-0| I120: Backtrace:
2014-12-22T18:06:51+01:00[+0.012]| vcpu-0| I120: Backtrace[0] 00007fbb3c44a520 rip=00000000004f306e rbx=00000000004f2e40 rbp=0000000000000000 r12=00007fbb3c44b690 r13=00007fbb3c44ac48 r14=00007fbb3c44ac48 r15=000000000000000b
2014-12-22T18:06:51+01:00[+0.013]| vcpu-0| I120: Backtrace[1] 00007fbb3c44a550 rip=0000000000462c89 rbx=000000000000000b rbp=0000000000000004 r12=00007fbb3c44b690 r13=00007fbb3c44ac48 r14=00007fbb3c44ac48 r15=000000000000000b
2014-12-22T18:06:51+01:00[+0.013]| vcpu-0| I120: Backtrace[2] 00007fbb3c44a640 rip=00007fbb42e55cb0 rbx=0000000001edef58 rbp=0000000000000004 r12=0000000000000164 r13=00007fbb4365eec0 r14=0000000001a76e50 r15=00007fbb4365eec0
2014-12-22T18:06:51+01:00[+0.013]| vcpu-0| I120: Backtrace[3] 00007fbb3c44abc8 rip=0000000000000000 rbx=0000000001edef58 rbp=0000000000000004 r12=0000000000000164 r13=00007fbb4365eec0 r14=0000000001a76e50 r15=00007fbb4365eec0
2014-12-22T18:06:51+01:00[+0.013]| vcpu-0| I120: SymBacktrace[0] 00007fbb3c44a520 rip=00000000004f306e in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000
2014-12-22T18:06:51+01:00[+0.013]| vcpu-0| I120: SymBacktrace[1] 00007fbb3c44a550 rip=0000000000462c89 in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000
2014-12-22T18:06:51+01:00[+0.013]| vcpu-0| I120: SymBacktrace[2] 00007fbb3c44a640 rip=00007fbb42e55cb0 in function (null) in object /lib/x86_64-linux-gnu/libpthread.so.0 loaded at 00007fbb42e46000
2014-12-22T18:06:51+01:00[+0.014]| vcpu-0| I120: SymBacktrace[3] 00007fbb3c44abc8 rip=0000000000000000
2014-12-22T18:06:51+01:00[+0.014]| vcpu-0| I120: Unexpected signal: 11.
2014-12-22T18:06:51+01:00[+0.014]| vcpu-0| W110:
2014-12-22T18:06:51+01:00[+0.014]| vcpu-0| W110+ The core dump limit is set to ZERO; no core dump should be expected
2014-12-22T18:06:51+01:00[+0.200]| vcpu-0| W110: Core dumped.
2014-12-22T18:06:51+01:00[+0.201]| vcpu-0| I120: Core dump pipes to process /usr/share/apport/apport %p %s %c, core file unreliable
2014-12-22T18:06:51+01:00[+0.201]| vcpu-0| W110: A core file is available in "/home/psaxl/Machines virtuelles/OS X Mavericks/core"
2014-12-22T18:06:51+01:00[+0.201]| vcpu-0| W110: Writing monitor corefile "/home/psaxl/Machines virtuelles/OS X Mavericks/vmmcores.gz"
2014-12-22T18:06:51+01:00[+0.204]| vcpu-0| W110: Dumping core for vcpu-0
2014-12-22T18:06:51+01:00[+0.204]| vcpu-0| I120: Beginning monitor coredump
2014-12-22T18:06:51.892+01:00| mks| W110: Panic in progress... ungrabbing
2014-12-22T18:06:51.892+01:00| mks| I120: MKS: Release starting (panic).
2014-12-22T18:06:51.895+01:00| mks| I120: MKS: Release finished (panic).
2014-12-22T18:06:51.895+01:00| mks| W110: Panic in progress... ungrabbing
2014-12-22T18:06:51.895+01:00| mks| I120: MKS: Release starting (panic).
2014-12-22T18:06:51.895+01:00| mks| I120: MKS: Release finished (panic).
2014-12-22T18:06:51+01:00[+0.688]| vcpu-0| I120: End monitor coredump
2014-12-22T18:06:51+01:00[+0.688]| vcpu-0| W110: Dumping core for vcpu-1
2014-12-22T18:06:51+01:00[+0.688]| vcpu-0| I120: Beginning monitor coredump
2014-12-22T18:06:51+01:00[+1.442]| vcpu-0| I120: End monitor coredump
2014-12-22T18:06:51+01:00[+1.964]| vcpu-0| I120: Coredump encountered overflow 2075:2075 (350 duplicates)
2014-12-22T18:06:51+01:00[+2.192]| vcpu-0| I120: Backtrace:
2014-12-22T18:06:51+01:00[+2.192]| vcpu-0| I120: Backtrace[0] 00007fbb3c44a020 rip=00000000004f306e rbx=00000000004f2e40 rbp=0000000000000000 r12=0000000000000001 r13=00007fbb3c44ac48 r14=00007fbb3c44ac48 r15=000000000000000b
2014-12-22T18:06:51+01:00[+2.192]| vcpu-0| I120: Backtrace[1] 00007fbb3c44a050 rip=00000000004ce229 rbx=00007fbb3c44a070 rbp=00000000014c4260 r12=0000000000000001 r13=00007fbb3c44ac48 r14=00007fbb3c44ac48 r15=000000000000000b
2014-12-22T18:06:51+01:00[+2.192]| vcpu-0| I120: Backtrace[2] 00007fbb3c44a550 rip=0000000000462cd8 rbx=000000000000000b rbp=00007fbb3c44a580 r12=00007fbb3c44b690 r13=00007fbb3c44ac48 r14=00007fbb3c44ac48 r15=000000000000000b
2014-12-22T18:06:51+01:00[+2.192]| vcpu-0| I120: Backtrace[3] 00007fbb3c44a640 rip=00007fbb42e55cb0 rbx=0000000001edef58 rbp=0000000000000004 r12=0000000000000164 r13=00007fbb4365eec0 r14=0000000001a76e50 r15=00007fbb4365eec0
2014-12-22T18:06:51+01:00[+2.192]| vcpu-0| I120: Backtrace[4] 00007fbb3c44abc8 rip=0000000000000000 rbx=0000000001edef58 rbp=0000000000000004 r12=0000000000000164 r13=00007fbb4365eec0 r14=0000000001a76e50 r15=00007fbb4365eec0
2014-12-22T18:06:51+01:00[+2.193]| vcpu-0| I120: SymBacktrace[0] 00007fbb3c44a020 rip=00000000004f306e in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000
2014-12-22T18:06:51+01:00[+2.193]| vcpu-0| I120: SymBacktrace[1] 00007fbb3c44a050 rip=00000000004ce229 in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000
2014-12-22T18:06:51+01:00[+2.193]| vcpu-0| I120: SymBacktrace[2] 00007fbb3c44a550 rip=0000000000462cd8 in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000
2014-12-22T18:06:51+01:00[+2.193]| vcpu-0| I120: SymBacktrace[3] 00007fbb3c44a640 rip=00007fbb42e55cb0 in function (null) in object /lib/x86_64-linux-gnu/libpthread.so.0 loaded at 00007fbb42e46000
2014-12-22T18:06:51+01:00[+2.193]| vcpu-0| I120: SymBacktrace[4] 00007fbb3c44abc8 rip=0000000000000000
2014-12-22T18:06:51+01:00[+2.193]| vcpu-0| I120: Msg_Post: Error
2014-12-22T18:06:51+01:00[+2.193]| vcpu-0| I120: [msg.log.error.unrecoverable] VMware Workstation unrecoverable error: (vcpu-0)
2014-12-22T18:06:51+01:00[+2.193]| vcpu-0| I120+ Unexpected signal: 11.
2014-12-22T18:06:51+01:00[+2.193]| vcpu-0| I120: [msg.panic.haveLog] A log file is available in "/home/psaxl/Machines virtuelles/OS X Mavericks/vmware.log".  
2014-12-22T18:06:51+01:00[+2.193]| vcpu-0| I120: [msg.panic.requestSupport.withoutLog] You can request support.  
2014-12-22T18:06:51+01:00[+2.193]| vcpu-0| I120: [msg.panic.requestSupport.vmSupport.windowsOrLinux]
2014-12-22T18:06:51+01:00[+2.193]| vcpu-0| I120+ To collect data to submit to VMware support, choose "Collect Support Data" from the Help menu.
2014-12-22T18:06:51+01:00[+2.193]| vcpu-0| I120+ You can also run the "vm-support" script in the Workstation folder directly.
2014-12-22T18:06:51+01:00[+2.193]| vcpu-0| I120: [msg.panic.response] We will respond on the basis of your support entitlement.
2014-12-22T18:06:51+01:00[+2.193]| vcpu-0| I120: ----------------------------------------
2014-12-22T18:06:51+01:00[+92.433]| vcpu-0| I120: Exiting

post-1362041-0-04118400-1419270019_thumb.png

vmware.txt

OS X Mavericks.vmx.txt

Link to comment
Share on other sites

 

Hello,

 

I previously had VMware Workstation 10 on a Ubuntu Linux 12.04 LTS and upgraded (by uninstalling the reinstalling everything from scratch) to VMware Workstation 11 with Unlocker 2.0.2 yesterday. However, I can't properly use my OSX virtual machine from now on. Indeed, the VM crashes every 5 or 10 minutes and the following error message appears:

 

 

Can you add smc.vrsion = "0"  to vmx file as documented in readme.txt or downgrade virtual hardware to version 10.

Link to comment
Share on other sites

I've just tried this (downgrading to VM10 the virtual hardware and setting smc.version to value "0") but the same problem still occurs unfortunately... Here are some logs

 

You are running a distro from ZackehSoul. We don't support anything other than vanilla OS X as there is usually a load of kexts and other things that interfere with running OS X on VMware. Can you re-try using a clean installation of OS X  so we can rule that in or out of the problem please? .

I can confirm psaxl's crash (running on F20, x64, kernel 3.17.4-200). largely identical backtrace, trying to run any of 10.9 or 10.10

 

Can you attach a vmware.log to a post please? I should point out that the unlocker actually does very little to the core VMX executable, and there are reports of signal 11 errors for Workstation on Linux not related to unlocking VMX..

 

 

Can you both ensure you do not have 3D graphic s acceleration selected for the VM? This is a known issue for Workstation on Linux, and can cause signal 11.

Link to comment
Share on other sites

I have same problem with unexpected signal:

 

 

VMware Workstation unrecoverable error: (vcpu-0)
Unexpected signal: 11.

 

Running Ubuntu 14.04 as host OS and OS X 10.9 as guest. Seems to be linux host specific problem. However I found workaround, just disable sound card in virtal machine preferences and this error will go away. Crash happens when OS X trying to make sound.

  • Like 1
Link to comment
Share on other sites

Okay, I'm very reluctant to post, because I'm sure I've messed something up or misread, but aren't there supposed to be OSX options when creating a new VM? I have none. Also, one of my VMs got switched away when I was investigating and I can't change it back. Not sure what to check next.

 

Host OS: Windows 8.1 Pro

VMware Workstation 11.0 (reinstalled clean to check)

Unlocker 2.0.2 (reapplied after clean reinstall of VMware Workstation)

 

Argh. As I feared, opened my mouth and removed all doubt.

 

Reinstalling VMW did nothing, as did repairing, but I did a full on complete remove, reboot, manual check for leftover bits, reboot, install, reboot, unlocker, reboot, launch VMW cycle, and now the OSX guest options are back. Sorry for the trouble.

Link to comment
Share on other sites

You are running a distro from ZackehSoul. We don't support anything other than vanilla OS X as there is usually a load of kexts and other things that interfere with running OS X on VMware. Can you re-try using a clean installation of OS X  so we can rule that in or out of the problem please? .

 

Can you attach a vmware.log to a post please? I should point out that the unlocker actually does very little to the core VMX executable, and there are reports of signal 11 errors for Workstation on Linux not related to unlocking VMX..

 

 

Can you both ensure you do not have 3D graphic s acceleration selected for the VM? This is a known issue for Workstation on Linux, and can cause signal 11.

 

Weiredly im running a distro from ZackehSoul, but putting smc.version to value "0" Worked for me, Thanks a Lot donk for your unlocker. but im wondering, Yosemite is running slower on the vm11 than vm10, did i overlook anything?

Link to comment
Share on other sites

Hello

 

Firstly, thank you Donk for your amazing project! I really apreciate it!

 

 

I need help (i'm a begginer)

 

 

So, i'm trying to install Yosemite 10.10.1 (host is Win8.1 Pro VL x64 with a Haswell 4770K)

 

 

I'm using OS X Yosemite 10.10.1 (14B25) bootable USB (DMG File) [5.29 GB]

 

I installed VMware WS 11 > ran unlocker 2.0.3 > converted 'OS X Base System.dmg' to .iso using http://vu1tur.eu.org/tools/ > create a vm using default settings > smc.version = "0" added to .vmx file

 

 

When i power up, it gives this:

 

Error: http://i.imgur.com/aYREYH9.png ||| http://i.imgur.com/cyHZ0CP.png

Log: http://pastebin.com/hKvsHvBx

 

When '2015-01-06T15:41:42.632-02:00| vmx| I120: GuestRpcSendTimedOut: message to toolbox-dnd timed out.' pops in the log the error come out

 

 

 

What can it be?

 

 

 

Sorry for my bad english

 

 

Thanks :)

Link to comment
Share on other sites

Thanks Donk for the software! I am new to Mac and please help, everyone..

 

After installed Unlocker203, my Yosemite VM successfully boot up in VMware Workstation 11, but the resolution is limited to 1024x768, and a reminder for VMware Tools pop up. I tried to install the VMware Tools, but got the following error message instead:

 

"Could not find component on update server. Contact VMware Support or your system administrator".

 

The host PC is a 64-bit Ubuntu 14.10 with Xeon E3-1230v3 CPU/16GB/Nvidia Video Card/BenQ 1920x1080 Monitor. My Windows 7 Professional VM works fine under Workstation 11 for full screen 1920x1080 resolution.

 

The Guest Yosemite VM was made on a new MacBook Air Laptop that just purchased 2 days ago. I installed VMware Fusion 7 and no other updates or software installations on the laptop. The VM was created using Recovery Partition as VMware documentation indicated. Works perfectly on the laptop inside the Fusion 7.

 

I copied the VM across to the host PC, applied the Unlocker203 script with no issues. The VM boot up ok, but just resolution is restricted to 1024x768, and can't install VMware Tools. I did the software update and it works fine. I tried attach the 'vmware.log' file to this post, but the forum said "You aren't permitted to upload this kind of file".

 

Thanks in advance for the help...

Link to comment
Share on other sites

Thanks Donk for the software! I am new to Mac and please help, everyone..

 

After installed Unlocker203, my Yosemite VM successfully boot up in VMware Workstation 11, but the resolution is limited to 1024x768, and a reminder for VMware Tools pop up. I tried to install the VMware Tools, but got the following error message instead:

 

"Could not find component on update server. Contact VMware Support or your system administrator".

 

The host PC is a 64-bit Ubuntu 14.10 with Xeon E3-1230v3 CPU/16GB/Nvidia Video Card/BenQ 1920x1080 Monitor. My Windows 7 Professional VM works fine under Workstation 11 for full screen 1920x1080 resolution.

 

The Guest Yosemite VM was made on a new MacBook Air Laptop that just purchased 2 days ago. I installed VMware Fusion 7 and no other updates or software installations on the laptop. The VM was created using Recovery Partition as VMware documentation indicated. Works perfectly on the laptop inside the Fusion 7.

 

I copied the VM across to the host PC, applied the Unlocker203 script with no issues. The VM boot up ok, but just resolution is restricted to 1024x768, and can't install VMware Tools. I did the software update and it works fine. I tried attach the 'vmware.log' file to this post, but the forum said "You aren't permitted to upload this kind of file".

 

Thanks in advance for the help...

you need to manually install VMware Tools, pointing to the image VMware tools - Use iso image file - in the virtual cd device, when starting VM OS X.

Link to comment
Share on other sites

Thanks Donk for the software! I am new to Mac and please help, everyone..

 

After installed Unlocker203, my Yosemite VM successfully boot up in VMware Workstation 11, but the resolution is limited to 1024x768, and a reminder for VMware Tools pop up. I tried to install the VMware Tools, but got the following error message instead:

 

"Could not find component on update server. Contact VMware Support or your system administrator".

 

The host PC is a 64-bit Ubuntu 14.10 with Xeon E3-1230v3 CPU/16GB/Nvidia Video Card/BenQ 1920x1080 Monitor. My Windows 7 Professional VM works fine under Workstation 11 for full screen 1920x1080 resolution.

 

The Guest Yosemite VM was made on a new MacBook Air Laptop that just purchased 2 days ago. I installed VMware Fusion 7 and no other updates or software installations on the laptop. The VM was created using Recovery Partition as VMware documentation indicated. Works perfectly on the laptop inside the Fusion 7.

 

I copied the VM across to the host PC, applied the Unlocker203 script with no issues. The VM boot up ok, but just resolution is restricted to 1024x768, and can't install VMware Tools. I did the software update and it works fine. I tried attach the 'vmware.log' file to this post, but the forum said "You aren't permitted to upload this kind of file".

 

Thanks in advance for the help...

Tony,

11Al beat me to the draw, in Workstation 11 you cannot install the VMware Tools from the menu, it needs to be done manually. The tools are installed from the darwin.iso, which needs to be mounted via the CD/DVD drive, the iso is located in the tools directory of the unlocker203 and in the VMware Workstation installation directory. Once installed you should be able to change resolution.

Hello

 

Firstly, thank you Donk for your amazing project! I really apreciate it!

I need help (i'm a begginer)

So, i'm trying to install Yosemite 10.10.1 (host is Win8.1 Pro VL x64 with a Haswell 4770K)

 

I'm using OS X Yosemite 10.10.1 (14B25) bootable USB (DMG File) [5.29 GB]

 

I installed VMware WS 11 > ran unlocker 2.0.3 > converted 'OS X Base System.dmg' to .iso using http://vu1tur.eu.org/tools/ > create a vm using default settings > smc.version = "0" added to .vmx file

 

When i power up, it gives this:

 

Error: http://i.imgur.com/aYREYH9.png ||| http://i.imgur.com/cyHZ0CP.png

Log: http://pastebin.com/hKvsHvBx

 

When '2015-01-06T15:41:42.632-02:00| vmx| I120: GuestRpcSendTimedOut: message to toolbox-dnd timed out.' pops in the log the error come out

 

What can it be?

Sorry for my bad english

 

Thanks :)

lllFATAL1TY,

 

You need to create a DMG file which includes the Base System, have a look at the following topic it has all the steps required to install Yosemite in VMware Workstation 11:

 

http://www.insanelymac.com/forum/topic/290949-how-to-install-os-x-10x-snow-leopard-lion-mountain-lion-mavericks-and-yosemite-in-vmware-workstation-1011-or-player-67/

  • Like 1
Link to comment
Share on other sites

post-1239015-0-87417400-1420622352_thumb.png

 

Hi 11Al and MSoK,

 

Thanks for the reply. After mapping drive to that .iso file, installation of the VMware Tools can be started but can not be finished. Please see attached the screen snapshot for detail. Just before I could click 'restart' button, the error message window pop up, and close that window will close the Workstation 11 window as well. 

 

I must missed something here..

 

 

Link to comment
Share on other sites

tonyyz05,

Try turning off the sound card before starting the VM. Chaosmaster, pointed out that the error comes up everytime OS X tries to make a sound. His solution worked for me and I am now running the VM without a hitch (and without sound, also).

Still, I would like to find a fix for this bug as I would like to run GarageBand in the VM if possible.

 

Cheers.

Link to comment
Share on other sites

Hello everyone.

 

First thanks to Donk and everyone one who comtribute to the unlocker.

 

Quick questions :

 

  • Can this be used on Esxi 5.5U2 ?

 

Ps: I am running Maverick in esxi, whit GPU passtrough in vtd, (unlocker V1) and looking foward to upgrade to Yosemite.

Link to comment
Share on other sites

Hello everyone.

 

First thanks to Donk and everyone one who comtribute to the unlocker.

 

Quick questions :

 

  • Can this be used on Esxi 5.5U2 ?

 

Ps: I am running Maverick in esxi, whit GPU passtrough in vtd, (unlocker V1) and looking foward to upgrade to Yosemite.

 

No - use 1.3.1 for ESXi.

Link to comment
Share on other sites

 Share

×
×
  • Create New...