Jump to content
InsanelyMac Forum

AidanLinz

Members
  • Content count

    8
  • Joined

  • Last visited

About AidanLinz

  • Rank
    InsanelyMac Protégé
  • Birthday 09/20/1984

Contact Methods

  • Website URL
    http://

Profile Information

  • Gender
    Male
  • Location
    Chapel Hill, NC
  1. AidanLinz

    ESXi 5 Mac OS X Unlocker

    The vmware.log files for the machines themselves weren't written to by the power on attempts, so they won't be much use, that snippet came from hostd.log...I'll send it your way shortly. I also just saw this in the kernel logs: 2012-11-06T04:30:40.418Z cpu0:6003)VmkAccess: 637: hostd-vix-poll: access denied:: dom:appDom(2), obj:vmxSys(66), mode:syscall_allow(2) 2012-11-06T04:37:19.983Z cpu0:6003)VmkAccess: 637: hostd-vix-poll: access denied:: dom:appDom(2), obj:vmxSys(66), mode:syscall_allow(2) 2012-11-06T05:21:12.758Z cpu5:6003)VmkAccess: 637: hostd-vix-poll: access denied:: dom:appDom(2), obj:vmxSys(66), mode:syscall_allow(2) 2012-11-06T05:36:40.141Z cpu5:1037388)VmkAccess: 637: vmx: access denied:: dom:appDom(2), obj:vmxSys(66), mode:syscall_allow(2) 2012-11-06T05:36:46.002Z cpu3:1041489)VmkAccess: 637: vmx: access denied:: dom:appDom(2), obj:vmxSys(66), mode:syscall_allow(2) Yes, it is a cluster -- though that host just got kicked out of it. We upgraded, re-applied unlocker, unapplied unlocker, and re-applied unlocker. Thanks for the swift response!
  2. AidanLinz

    ESXi 5 Mac OS X Unlocker

    Donk, in reference to alexiskai-- I've isolated the source of the problem down to this snippet from the logs: 2012-11-06T05:21:12.760Z [314F4B90 warning 'Libs'] VMHSSpawnVMXUW: unable to spawn /bin/vmx: Operation not permitted 2012-11-06T05:21:12.760Z [314F4B90 info 'Libs'] VigorClient_StartAndConnect Failed: Failed to launch peer process /bin/vmx Error during version check: Failed to get vmkernel version: 0xffffffff I can provide more of the logs if they'd be helpful. I cloned the machine in question and that was the first attempt to power it on (it's been 3 so far that have fallen victem to the no-power-on issue). I don't remember what I did with migration to get the machines back on -- that was before I figured out what the cause was. As soon as I reverted unlocker, before rebooting, the machine powered on immediately.
×