"A general system error occurred" while trying to power on VM
Article ID: 416006
Updated On:
Products
VMware vSphere ESXi
Issue/Introduction
- After upgrading ESXI host, unable to power on VMs from VC and host
- We see the below error in the GUI and the command line as well
Powering on VM:
Power on failed: (vmodl.fault.SystemError) {
faultCause = (vmodl.MethodFault) null,
faultMessage = <unset>,
reason = "Error:
system_error
Messages:
vapi.send.failed<Send of frame failed: N7Vmacore15SystemExceptionE(No such file or directory)
[context]zKq7AVICAgAAAP////8LaG9zdGQAAANZQWxpYnZtYWNvcmUuc28AACDGKADvCykAuAwpAIUTKQCnGSkAjjEoALBMKABL2UkBgnoAbGlicHRocmVhZC5zby4wAALvLg9saWJjLnNvLjYA[/context]>
"
msg = "A general system error occurred: Error:
system_error
Messages:
vapi.send.failed<Send of frame failed: N7Vmacore15SystemExceptionE(No such file or directory)
[context]zKq7AVICAgAAAP////8LaG9zdGQAAANZQWxpYnZtYWNvcmUuc28AACDGKADvCykAuAwpAIUTKQCnGSkAjjEoALBMKABL2UkBgnoAbGlicHRocmVhZC5zby4wAALvLg9saWJjLnNvLjYA[/context] - As per the /var/run/log/hostd.log
XXXX-XX-XXTHH:MM:SS.969Z In(166) Hostd[2745240]: [Originator@6876 sub=Vimsvc.TaskManager opID=m16opgz7-1517645-auto-#####-#####-##### sid=52ed### user=vpxuser:<no user>] Task Created : haTask-####-vim.VirtualMachine.powerOn-1936677528
XXXX-XX-XXTHH:MM:SS.970Z In(166) Hostd[2746561]: [Originator@6876 sub=Vimsvc.ha-eventmgr opID=m16opgz7-1517645-auto-#####-#####-##### sid=52ed#### user=vpxuser:<no user>] Event 32671 : <VM_Name> on <Host FQDN> in ha-datacenter is starting
YYYY-MM-DDTHH:MM:SS.971Z In(166) Hostd[2746561]: [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/vsan:525#####/9c07b961-#####-#####-#####/VM_Name.vmx opID=m16opgz7-1517645-auto-wj0u-h5:70065584-fd-01-01-01-01-de-88bc sid=52eda146 user=vpxuser:<no user>] State Transition (VM_STATE_OFF -> VM_STATE_POWERING_ON)
YYYY-MM-DDTHH:MM:SS.986Z Wa(164) Hostd[2745216]: [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/vsan:525#####/9c07b961-#####-#####-#####/VM_Name.vmx] Failed operation
YYYY-MM-DDTHH:MM:SS.986Z In(166) Hostd[2745216]: [Originator@6876 sub=Vimsvc.ha-eventmgr] Event 32672 : Cannot power on <VM_Name> on <Host FQDN> in ha-datacenter: A general system error occurred:
YYYY-MM-DDTHH:MM:SS.977Z Wa(164) Hostd[2745240]: [Originator@6876 sub=IO.Connection] Failed to connect; <io_obj p:0x0000002c3a8###, h:60, <UNIX ''>, <UNIX 'vmwLocalSocketSandboxVapi'>>, e: 2(No such file or directory), duration: 0msec
YYYY-MM-DDTHH:MM:SS.977Z Wa(164) Hostd[2745240]: [Originator@6876 sub=HttpConnectionPool-000000] Failed to get pooled connection; <cs p:0000002c111###, PIPE:vmwLocalSocketSandboxVapi>, (null), duration: 0msec, N7Vmacore15SystemExceptionE(No such file or directory)
- As per the /var/run/log/vmkwarning.log
YYYY-MM-DDTHH:MM:SS.048Z Wa(180) vmkwarning: cpu66:2941728)WARNING: VMotion: 3219: ############### D: failed to resolve net stack instance due to mismatch with vMotion server. Migration instance: vmotion. Server instance: defaultTcpipStack.
YYYY-MM-DDTHH:MM:SS.048Z In(182) vmkernel: cpu66:2941728)MigrateNet: 554: netStack=0x4315a28c2c00(vmotion) handle=0x466cc0001388
YYYY-MM-DDTHH:MM:SS.048Z Wa(180) vmkwarning: cpu66:2941728)WARNING: Migrate: 785: ############### D: Destroying non-empty VOB migrant context migrateExtVobCtx
- As per /vmfs/volumes/datastore/vm_directory/vmware.log
YYYY-MM-DDTHH:MM:SS.728Z In(05) vmx m16opgz7-2125841-auto-#####-#####-##### MigrateVMXdrToSpec: scsi:0:0 -> /vmfs/volumes/620d47f1-#####-###-###/VM_Name/VM_Name.vmdk, parent:null, parentShared: 0, rdmDevice: null,transform: 2, numSnapshots: 0, policy: 'null', independentFilters: ''
YYYY-MM-DDTHH:MM:SS.728Z In(05) vmx m16opgz7-2125841-auto-#####-#####-##### MigrateVMXdrToSpec: encryptedVMotion: 1
YYYY-MM-DDTHH:MM:SS.728Z In(05) vmx m16opgz7-2125841-auto-#####-#####-##### MigrateVMXdrToSpec: type 1 unsharedSwap 1 memMinToTransfer 0 cpuMinToTransfer 0 numDisks 1 numStreamIps 1 numFtStreamIps 0
YYYY-MM-DDTHH:MM:SS.728Z In(05) vmx m16opgz7-2125841-auto-#####-#####-##### Received migrate 'to' request for mid id 20723183########, src ip <10.62.xx.xx>, dst ip <10.62.xx.xx>(invalidate source config).
YYYY-MM-DDTHH:MM:SS.728Z In(05) vmx m16opgz7-2125841-auto-#####-#####-##### MigrateSetInfo: state=1 srcIp=<10.##.##.##> dstIp=<10.##.##.##> mid=20723183######## uuid=4c###-####-###-###-## priority=high
YYYY-MM-DDTHH:MM:SS.955Z In(05) vmx - MigrateVMXdrToSpec: scsi:0:0 -> /vmfs/volumes/620d47f1-#####-###-###/VM_Name/VM_Name.vmdk, parent:null, parentShared: 0, rdmDevice: null,transform: 2, numSnapshots: 0, policy: 'null', independentFilters: ''
YYYY-MM-DDTHH:MM:SS.955Z In(05) vmx - MigrateVMXdrToSpec: encryptedVMotion: 1
YYYY-MM-DDTHH:MM:SS.955Z In(05) vmx - MigrateVMXdrToSpec: type 1 unsharedSwap 1 memMinToTransfer 0 cpuMinToTransfer 0 numDisks 1 numStreamIps 1 numFtStreamIps 0
YYYY-MM-DDTHH:MM:SS.955Z In(05) vmx - Received migrate 'from' request for mid id 20723183########, src ip <10.##.##.##>.
YYYY-MM-DDTHH:MM:SS.955Z In(05) vmx - MigrateSetInfo: state=8 srcIp=<10.##.##.##> dstIp=<10.##.##.##> mid=############### uuid=4c###-####-###-###-## priority=high
...
YYYY-MM-DDTHH:MM:SS.048Z Wa(03) vmx - MigratePlatformInitMigration: Not supported
Environment
VMware ESXi 8.0 Update 2
Cause
If you install or remove a VIB on an ESX host in a VXrail environment followed by the backup.sh 1 command without rebooting the host, an issue in the ConfigStore framework might cause the host to enter into an inconsistent state. As a result, virtual machines on such hosts cannot power on or migrate.
Resolution
Permanent Fix: This problem is resolved in: VMware ESXi 8.0 Update 3e
Feedback
Yes
No
Powered by
