"There is no VM_NAME process running for config file" error when deploying a virtual machine
Article ID: 318456
Updated On:
Products
VMware vSphere ESXi
Issue/Introduction
Symptoms:
When virtual machines are deployed, you may experience these symptoms intermittently:
When virtual machines are deployed, you may experience these symptoms intermittently:
- In the vSphere Web Client, you see the entry similar to:
"Disconnected from virtual machine."
- In the vpxd.log file, you see entries similar to:
2019-01-30T06:59:33.536Z info vpxd[7F609C958700] [Originator@6876 sub=Default opID=4a20be67] [VpxLRO] -- ERROR task-519360 -- vm-16985 -- vim.VirtualMachine.powerOn: vim.fault.GenericVmConfigFault:
--> Result:
--> (vim.fault.GenericVmConfigFault) {
--> faultCause = (vmodl.MethodFault) null,
--> faultMessage = (vmodl.LocalizableMessage) [
--> (vmodl.LocalizableMessage) {
--> key = "msg.vigor.transport.connection.error",
--> arg = ,
--> message = "Disconnected from virtual machine."
--> },
--> (vmodl.LocalizableMessage) {
--> key = "msg.vigor.transport.connection.fail",
--> arg = (vmodl.KeyAnyValue) [
--> (vmodl.KeyAnyValue) {
--> key = "1",
--> value = "9"
--> },
--> (vmodl.KeyAnyValue) {
--> key = "2",
--> value = "There is no VMware_test process running for config file /vmfs/volumes/vsan:5262e56b243ed0b1-fbadb4f39d648c18/2c4b515c-b81b-aeae-f87c-98f2b3240a48/VMware_test.vmx"
--> }
--> ],
--> message = "Failed to establish transport connection (9): There is no VMware_test process running for config file /vmfs/volumes/vsan:5262e56b243ed0b1-fbadb4f39d648c18/2c4b515c-b81b-aeae-f87c-98f2b3240a48/VMware_test.vmx."
--> },
--> (vmodl.LocalizableMessage) {
--> key = "msg.asyncsocket.remotedisconnect",
--> arg = ,
--> message = "Remote disconnected"
--> },
--> (vmodl.LocalizableMessage) {
--> key = "vpxd.vm.poweron.unexpectedfailure",
--> arg = (vmodl.KeyAnyValue) [
--> (vmodl.KeyAnyValue) {
--> key = "1",
--> value = "VMware_test"
--> }
--> ],
--> message = "An unexpected error was received from the ESX host while powering on VM VMware_test."
--> }
--> ],
--> reason = "Disconnected from virtual machine."
--> msg = "Disconnected from virtual machine."
--> Result:
--> (vim.fault.GenericVmConfigFault) {
--> faultCause = (vmodl.MethodFault) null,
--> faultMessage = (vmodl.LocalizableMessage) [
--> (vmodl.LocalizableMessage) {
--> key = "msg.vigor.transport.connection.error",
--> arg = ,
--> message = "Disconnected from virtual machine."
--> },
--> (vmodl.LocalizableMessage) {
--> key = "msg.vigor.transport.connection.fail",
--> arg = (vmodl.KeyAnyValue) [
--> (vmodl.KeyAnyValue) {
--> key = "1",
--> value = "9"
--> },
--> (vmodl.KeyAnyValue) {
--> key = "2",
--> value = "There is no VMware_test process running for config file /vmfs/volumes/vsan:5262e56b243ed0b1-fbadb4f39d648c18/2c4b515c-b81b-aeae-f87c-98f2b3240a48/VMware_test.vmx"
--> }
--> ],
--> message = "Failed to establish transport connection (9): There is no VMware_test process running for config file /vmfs/volumes/vsan:5262e56b243ed0b1-fbadb4f39d648c18/2c4b515c-b81b-aeae-f87c-98f2b3240a48/VMware_test.vmx."
--> },
--> (vmodl.LocalizableMessage) {
--> key = "msg.asyncsocket.remotedisconnect",
--> arg = ,
--> message = "Remote disconnected"
--> },
--> (vmodl.LocalizableMessage) {
--> key = "vpxd.vm.poweron.unexpectedfailure",
--> arg = (vmodl.KeyAnyValue) [
--> (vmodl.KeyAnyValue) {
--> key = "1",
--> value = "VMware_test"
--> }
--> ],
--> message = "An unexpected error was received from the ESX host while powering on VM VMware_test."
--> }
--> ],
--> reason = "Disconnected from virtual machine."
--> msg = "Disconnected from virtual machine."
- In the /var/core you see vmx core dump vmx-zdump.000.
Environment
VMware vSphere ESXi 6.7
VMware vSphere ESXi 6.5
VMware vSphere ESXi 6.5
Cause
This issue occur due to a race condition between Namespace DB creation and migration activity.
Resolution
This issue is resolved in ESXi 6.5 P04 build-15256549
Release Name: ESXi650-201912002
Workaround:
To workaround this issue use one of the following options.
Release Name: ESXi650-201912002
Workaround:
To workaround this issue use one of the following options.
- Use Linked Clones
- Don't use NSX Guest Introspection for the IC pool.
- Place the problematic host into maintenance mode.
Feedback
Yes
No
Powered by
