VMware Cloud Community
XWAVG
Contributor
Contributor

VMHSSpawnVMXUW: unable to spawn /bin/vmx: Operation not permitted

Folks:

Can someone point me to the right direction in resolving this error? Thank you.

2013-10-09T10:51:49.449Z [4DB5AB90 verbose 'Cimsvc'] Ticket issued for CIMOM version 1.0, user root

2013-10-09T10:51:51.644Z [4D840B90 info 'Vimsvc.TaskManager' opID=21D44435-00000040] Task Created : haTask-27-vim.VirtualMachine.powerOn-432031893

2013-10-09T10:51:51.645Z [4DB9BB90 verbose 'Vmsvc.vm:/vmfs/volumes/51cafb34-0fd1f9ba-2cd4-90b11c435659/QA-AutoWin7/QA-AutoWin7.vmx' opID=21D44435-00000040] Power on request recieved

2013-10-09T10:51:51.645Z [4DB9BB90 verbose 'Vmsvc.vm:/vmfs/volumes/51cafb34-0fd1f9ba-2cd4-90b11c435659/QA-AutoWin7/QA-AutoWin7.vmx' opID=21D44435-00000040] Reconfigure ethernet backing if required

2013-10-09T10:51:51.645Z [4DB9BB90 info 'Vimsvc.ha-eventmgr' opID=21D44435-00000040] Event 254 : QA-AutoWin7_120 on host [deleted fqdn] in ha-datacenter is starting

2013-10-09T10:51:51.646Z [4DB9BB90 info 'Vmsvc.vm:/vmfs/volumes/51cafb34-0fd1f9ba-2cd4-90b11c435659/QA-AutoWin7/QA-AutoWin7.vmx' opID=21D44435-00000040] State Transition (VM_STATE_OFF -> VM_STATE_POWERING_ON)

2013-10-09T10:51:51.646Z [4DB9BB90 verbose 'Hostsvc.HaHost' opID=21D44435-00000040] ModeMgr::Begin: op = normal, current = normal, count = 15

2013-10-09T10:51:51.646Z [4DB9BB90 verbose 'Vmsvc.vm:/vmfs/volumes/51cafb34-0fd1f9ba-2cd4-90b11c435659/QA-AutoWin7/QA-AutoWin7.vmx' opID=21D44435-00000040] Invoking interceptor:3-ha-vmsvc

SIOC: SIOC is notified not to start injector

2013-10-09T10:51:51.647Z [4DB9BB90 verbose 'Vmsvc.vm:/vmfs/volumes/51cafb34-0fd1f9ba-2cd4-90b11c435659/QA-AutoWin7/QA-AutoWin7.vmx' opID=21D44435-00000040] Done invoking interceptor:3-ha-vmsvc

2013-10-09T10:51:51.649Z [4DB9BB90 verbose 'Hostsvc.ServiceSystem' opID=21D44435-00000040] Invoking command /bin/sh /etc/init.d/xorg status

2013-10-09T10:51:51.650Z [4DB9BB90 info 'SysCommandPosix' opID=21D44435-00000040] ForkExec(/bin/sh)  120706

2013-10-09T10:51:51.687Z [4DB9BB90 verbose 'Hostsvc.ServiceSystem' opID=21D44435-00000040] Command finished with status 3

2013-10-09T10:51:51.736Z [4DB9BB90 verbose 'Hostsvc' opID=21D44435-00000040] Security domain hostd27 not found

2013-10-09T10:51:51.736Z [4DB9BB90 info 'Libs' opID=21D44435-00000040] Vix: [5466 foundryHandleProperties.c:3359]: Error VIX_E_NOT_FOUND in Vix_GetPropertiesImpl(): Unable to get bool property 107.

2013-10-09T10:51:51.737Z [4DB9BB90 verbose 'Vmsvc.vm:/vmfs/volumes/51cafb34-0fd1f9ba-2cd4-90b11c435659/QA-AutoWin7/QA-AutoWin7.vmx' opID=21D44435-00000040] PowerOn request queued

2013-10-09T10:51:51.737Z [4DD9EB90 verbose 'Vmsvc.vm:/vmfs/volumes/51cafb34-0fd1f9ba-2cd4-90b11c435659/QA-AutoWin7/QA-AutoWin7.vmx'] Retrieved current VM state from foundry 7, 6

2013-10-09T10:51:51.738Z [4D9C5B90 info 'vm:VMHSVMCbPower: /vmfs/volumes/51cafb34-0fd1f9ba-2cd4-90b11c435659/QA-AutoWin7/QA-AutoWin7.vmx']  Setting state of VM to powerOn with option soft

2013-10-09T10:51:51.740Z [4D9C5B90 info 'Libs'] Starting vmx as /bin/vmx

2013-10-09T10:51:51.740Z [4D9C5B90 info 'Libs'] Starting vmx as /bin/vmx

2013-10-09T10:51:51.741Z [4D9C5B90 info 'vm:/vmfs/volumes/51cafb34-0fd1f9ba-2cd4-90b11c435659/QA-AutoWin7/QA-AutoWin7.vmx']  VMHS: VM /vmfs/volumes/51cafb34-0fd1f9ba-2cd4-90b11c435659/QA-AutoWin7/QA-AutoWin7.vmx in directory /vmfs/volumes/51cafb34-0fd1f9ba-2cd4-90b11c435659/QA-AutoWin7

2013-10-09T10:51:51.741Z [4D9C5B90 info 'vm:/vmfs/volumes/51cafb34-0fd1f9ba-2cd4-90b11c435659/QA-AutoWin7/QA-AutoWin7.vmx']  VMHS: Exec()'ing /bin/vmx.

2013-10-09T10:51:51.741Z [4D9C5B90 info 'Libs'] VMHS: VMKernel_ForkExec(/bin/vmx, detached=1): rc=195887383 pid=1296313312

2013-10-09T10:51:51.741Z [4D9C5B90 warning 'Libs'] VMHSSpawnVMXUW: unable to spawn /bin/vmx: Operation not permitted

2013-10-09T10:51:51.742Z [4D9C5B90 info 'Libs'] VigorClient_StartAndConnect Failed: Failed to launch peer process

2013-10-09T10:51:51.742Z [4D9C5B90 info 'vm:/vmfs/volumes/51cafb34-0fd1f9ba-2cd4-90b11c435659/QA-AutoWin7/QA-AutoWin7.vmx']  Reloading config state.

2013-10-09T10:51:51.784Z [4D9C5B90 info 'Libs'] VMHS: Transitioned vmx/execState/val to poweredOff

2013-10-09T10:51:51.796Z [4DB9BB90 info 'Vmsvc.vm:/vmfs/volumes/51cafb34-0fd1f9ba-2cd4-90b11c435659/QA-AutoWin7/QA-AutoWin7.vmx'] Upgrade is required for virtual machine, version: 8

2013-10-09T10:51:51.796Z [4DB9BB90 verbose 'Vmsvc.vm:/vmfs/volumes/51cafb34-0fd1f9ba-2cd4-90b11c435659/QA-AutoWin7/QA-AutoWin7.vmx'] Running status of tools changed to: 0

2013-10-09T10:51:51.796Z [4D9C5B90 info 'vm:FoundryVMDBPowerOpCallback: VMDB reports power op failed for VM /vmfs/volumes/51cafb34-0fd1f9ba-2cd4-90b11c435659/QA-AutoWin7/QA-AutoWin7.vmx'] with error msg = "The virtual machine could not start. Make sure VMware ESX is installed correctly. You must also have rights to run the software and access all directories the

2013-10-09T10:51:51.797Z [4DB9BB90 verbose 'Vmsvc.vm:/vmfs/volumes/51cafb34-0fd1f9ba-2cd4-90b11c435659/QA-AutoWin7/QA-AutoWin7.vmx'] Retrieved current VM state from foundry 5, 2

2013-10-09T10:51:51.797Z [4D881B90 info 'Vmsvc.vm:/vmfs/volumes/51cafb34-0fd1f9ba-2cd4-90b11c435659/QA-AutoWin7/QA-AutoWin7.vmx' opID=21D44435-00000040] Failed to do Power Op: Error: (3041) The virtual machine could not start

2013-10-09T10:51:51.797Z [4D881B90 info 'Hostsvc' opID=21D44435-00000040] Decremented SIOC Injector Flag2

2013-10-09T10:51:51.837Z [4D9C5B90 info 'vm:Vix: [5290 foundryVMPowerOps.c:980]: FoundryVMPowerStateChangeCallback: /vmfs/volumes/51cafb34-0fd1f9ba-2cd4-90b11c435659/QA-AutoWin7/QA-AutoWin7.vmx']  vmx/execState/val = poweredOff.

2013-10-09T10:51:51.841Z [4D881B90 warning 'Vmsvc.vm:/vmfs/volumes/51cafb34-0fd1f9ba-2cd4-90b11c435659/QA-AutoWin7/QA-AutoWin7.vmx' opID=21D44435-00000040] Failed operation

2013-10-09T10:51:51.841Z [4D881B90 info 'Vimsvc.ha-eventmgr' opID=21D44435-00000040] Event 255 : Cannot power on QA-AutoWin7_120 on [deleted fqdn] in ha-datacenter. A general system error occurred:

2013-10-09T10:51:51.842Z [4D881B90 info 'Vmsvc.vm:/vmfs/volumes/51cafb34-0fd1f9ba-2cd4-90b11c435659/QA-AutoWin7/QA-AutoWin7.vmx' opID=21D44435-00000040] State Transition (VM_STATE_POWERING_ON -> VM_STATE_OFF)

2013-10-09T10:51:51.842Z [4D881B90 verbose 'Hostsvc.HaHost' opID=21D44435-00000040] ModeMgr::End: op = normal, current = normal, count = 16

2013-10-09T10:51:51.866Z [4D881B90 info 'Hostsvc.HaHost' opID=21D44435-00000040] vmxSwapEnabled = true vmmOvhd.anonymous: 16693 vmmOvhd.paged: 54221 vmmOvhd.nonpaged: 13511

2013-10-09T10:51:51.866Z [4D881B90 info 'Hostsvc.HaHost' opID=21D44435-00000040] vmkOvhd.fixd = 303104 vmkOvhd.variable: 2050 vmkOvhd.selfSwap: 3145728

2013-10-09T10:51:51.866Z [4D881B90 info 'Hostsvc.HaHost' opID=21D44435-00000040] Computed from lib overhead: 123715584 for (memPages: 524288, fbSize: 2048, #vcpus: 1, #lsiscsi: 1, #pvscsi: 0, #passthru: 0, #network: 1) vmkOverhead: 7647232

2013-10-09T10:51:51.866Z [4D881B90 info 'Hostsvc.HaHost' opID=21D44435-00000040] overhead result (no CBRC): 131362816

2013-10-09T10:51:51.866Z [4D881B90 info 'Hostsvc.HaHost' opID=21D44435-00000040] Predicted overhead: 131362816 for (memory: 2147483648, video: 8388608, #vcpus: 1, autodetect: false, enable3D: false, svgaPtFbSize: 8388608, cbrcOverhead: 0

2013-10-09T10:51:51.866Z [4D881B90 verbose 'Vmsvc.vm:/vmfs/volumes/51cafb34-0fd1f9ba-2cd4-90b11c435659/QA-AutoWin7/QA-AutoWin7.vmx' opID=21D44435-00000040] Time to gather config: 24 (msecs)

2013-10-09T10:51:51.867Z [4D903B90 verbose 'Hbrsvc'] Replicator: ReconfigListener triggered for config VM 27

2013-10-09T10:51:51.867Z [4D881B90 info 'Hostsvc' opID=21D44435-00000040] Lookupvm: World ID not set for VM 27

2013-10-09T10:51:51.881Z [4D881B90 info 'Vimsvc.TaskManager' opID=21D44435-00000040] Task Completed : haTask-27-vim.VirtualMachine.powerOn-432031893 Status error

2013-10-09T10:51:51.882Z [4D903B90 verbose 'Hbrsvc'] Replicator: VmReconfig ignoring VM 27 not configured for replication

2013-10-09T10:51:57.124Z [4D840B90 verbose 'SoapAdapter'] Responded to service state request

0 Kudos
5 Replies
zXi_Gamer
Virtuoso
Virtuoso

Well, this should be the message you must be looking at

The virtual machine could not start. Make sure VMware ESX is installed correctly. You must also have rights to run the software and access all directories the

2013-10-09T10:51:51.797Z [4DB9BB90 verbose 'Vmsvc.vm:/vmfs/volumes/51cafb34-0fd1f9ba-2cd4-90b11c435659/QA-AutoWin7/QA-AutoWin7.vmx'] Retrieved current VM state from foundry 5, 2

Are you logged in as an user who has the rights for vm power ops and most imp, is the host having proper license Smiley Wink

XWAVG
Contributor
Contributor

Looks like it is related to the Mac OS X unlocker (unlock-all-v120), when I installed it in ESXi I run into this issue, and when I uninstall it this issue went away, but I can not run my Mac OS VMs.

Anybody know if ESXi 5.5 resolves the Mac OS X guest OS support issue from real experience?

0 Kudos
zXi_Gamer
Virtuoso
Virtuoso

Wow that is interesting, introducing a MacOSX VM disrupts the power ops of other Windows VMs?? Hmm.. Let me take a stab at my setup.

btw.

Support for Mac OS X 10.8.5 has been introduced for products:

  • ESXi 5.1 , ESXi 5.1 Update 1 and ESXi 5.5
0 Kudos
dariusd
VMware Employee
VMware Employee

Support for OS X guests continues to require that the host is Apple-branded hardware.  This is in accordance with Apple's Software License Agreement (SLA) for the relevant versions of OS X.

An "unlocker" will modify the internals of the ESXi operating system in a way which renders it unsupportable, and -- as seen in this case -- may interfere with the hypervisor's ability to run other VMs as well.

--

Darius

0 Kudos
thorsfall
Contributor
Contributor

Try restarting the hostd process.  For the record, I am not advocating the use of the OS X Unlocker tool (else Darius will probably delete my reply), but there do seem to be reports that VMs cannot be started from time to time after the tool has been run.  The workaround is to restart hostd, which in older ESX 5.1 releases meant running /etc/init.d/hostd restart as from the ESXi console.  YMMV.

Of course, you could also go out and buy a hideously expensive Mac Pro desktop and install ESXi on it, then run only OS X 10.7 or 10.8, as that's all Apple allows in their draconian licence terms. :smileymischief:

0 Kudos