vCenter error: The resource '400' is in use < ProVirtualzone

A couple of days when some of Windows teams members try to clone a VM they get this error “The resource ‘400’ is in use” and the clone was not possible.

Was the first time I see this error.

When you read in a vCenter a VM related error like “Resource is in use” then you know is a resource in the VM that is being use. Or in this case a vCenter resource.

Troubleshooting the logs in the VM, but also in the vCenter first we need to identify what is the resource 400.

In the logs we have this:


-->                      backing = (vim.vm.device.VirtualEthernetCard.DistributedVirtualPortBackingInfo) {
-->                         port = (vim.dvs.PortConnection) {
-->                            switchUuid = "d3 c1 00 50 98 4a 1c 57-ee 6e 99 92 5c d2 16 07",
-->                            portgroupKey = "dvportgroup-1712",
-->                            portKey = "400",
-->                            connectionCookie = 761017209
-->                         }

--> backing = (vim.vm.device.VirtualEthernetCard.DistributedVirtualPortBackingInfo) {

--> port = (vim.dvs.PortConnection) {

--> switchUuid = "d3 c1 00 50 98 4a 1c 57-ee 6e 99 92 5c d2 16 07",

--> portgroupKey = "dvportgroup-1712",

--> portKey = "400",

--> connectionCookie = 761017209

--> }

So we can identify that the resource belongs to Network, specifically to a vDS Portgroup.

Checking VM settings we can see that this is port ID used by the VM in the vDS Portgroup.

So we need to troubleshoot vCenter logs in the clone why is this resource being use and canceling the clone.

This is what we see in the vCenter logs:


…”
error vpxd[fusion_builder_container hundred_percent="yes" overflow="visible"][fusion_builder_row][fusion_builder_column type="1_1" background_position="left top" background_color="" border_size="" border_color="" border_style="solid" spacing="yes" background_image="" background_repeat="no-repeat" padding="" margin_top="0px" margin_bottom="0px" class="" id="" animation_type="" animation_speed="0.3" animation_direction="left" hide_on_mobile="no" center_content="no" min_height="none"][21016] [Originator@6876 sub=coreanchor opID=E41217AA-0000011D-95-20] [Vds::Anchor::ProcessVmConfigSpec] Failed in reserving a port (vim.fault.ResourceInUse). Rolling back the previously reserved ports
info vpxd[11924] [Originator@6876 sub=vpxLro opID=69a43162] [VpxLRO] -- BEGIN task-internal-46214 -- ServiceInstance -- vim.ServiceInstance.GetContent -- 520d2706-dc38-8115-39cc-ba1f1714beb9

warning vpxd[27200] [Originator@6876 sub=VmprovUtil opID=E41217AA-0000011D-95-20-cc] [VpxdVmprovUtil::PatchConfig] Not persisting the serial port network backings. If you have VMs with network backings for serial ports, please set config option: vpxd.SerialPort.PersistNetworkBacking.
info vpxd[19668] [Originator@6876 sub=vpxLro opID=5928a086] [VpxLRO] -- BEGIN task-internal-46323 -- host-26437 -- vim.HostSystem.acquireCimServicesTicket -- 52fc85cd-5654-2c23-f50f-029957048d9b(5295d922-2f27-65b1-11f5-d957ffc89292)
warning vpxd[26412] [Originator@6876 sub=VpxProfiler opID=E41217AA-0000011D-95-20-TaskLoop-365a3afd] TaskLoop [TotalTime] took 20167 ms
info vpxd[21016] [Originator@6876 sub=VmProv opID=E41217AA-0000011D-95-20] [WorkflowXAction] Done undo action vpx.vmprov.CreateSnapshot with output:
--> false
error vpxd[21016] [Originator@6876 sub=vpxLro opID=E41217AA-0000011D-95-20] [VpxLRO] Unexpected Exception: vim.fault.ResourceInUse “…

…”

error vpxd[fusion_builder_container hundred_percent="yes" overflow="visible"][fusion_builder_row][fusion_builder_column type="1_1" background_position="left top" background_color="" border_size="" border_color="" border_style="solid" spacing="yes" background_image="" background_repeat="no-repeat" padding="" margin_top="0px" margin_bottom="0px" class="" id="" animation_type="" animation_speed="0.3" animation_direction="left" hide_on_mobile="no" center_content="no" min_height="none"][21016] [Originator@6876 sub=coreanchor opID=E41217AA-0000011D-95-20] [Vds::Anchor::ProcessVmConfigSpec] Failed in reserving a port (vim.fault.ResourceInUse). Rolling back the previously reserved ports

info vpxd[11924] [Originator@6876 sub=vpxLro opID=69a43162] [VpxLRO] -- BEGIN task-internal-46214 -- ServiceInstance -- vim.ServiceInstance.GetContent -- 520d2706-dc38-8115-39cc-ba1f1714beb9

warning vpxd[27200] [Originator@6876 sub=VmprovUtil opID=E41217AA-0000011D-95-20-cc] [VpxdVmprovUtil::PatchConfig] Not persisting the serial port network backings. If you have VMs with network backings for serial ports, please set config option: vpxd.SerialPort.PersistNetworkBacking.

info vpxd[19668] [Originator@6876 sub=vpxLro opID=5928a086] [VpxLRO] -- BEGIN task-internal-46323 -- host-26437 -- vim.HostSystem.acquireCimServicesTicket -- 52fc85cd-5654-2c23-f50f-029957048d9b(5295d922-2f27-65b1-11f5-d957ffc89292)

warning vpxd[26412] [Originator@6876 sub=VpxProfiler opID=E41217AA-0000011D-95-20-TaskLoop-365a3afd] TaskLoop [TotalTime] took 20167 ms

info vpxd[21016] [Originator@6876 sub=VmProv opID=E41217AA-0000011D-95-20] [WorkflowXAction] Done undo action vpx.vmprov.CreateSnapshot with output:

--> false

error vpxd[21016] [Originator@6876 sub=vpxLro opID=E41217AA-0000011D-95-20] [VpxLRO] Unexpected Exception: vim.fault.ResourceInUse “…

Looking at the logs seems that the issue is when cloning the VM and removing the vDS port(source and destination)

The resource ‘400’ is the vDS port on the VM source subnet. The cause is that the cloning is trying to create in the destination a vDS with the Port ID 400 using the same subnet that is already been use in the vDS Portgroup, so the clone fails.

Solution:

When cloning we need to remove the interface(or change the network to vSwitch network) of the clone and finish the clone. After the conning just recreate the Interface, or just back to the original vDS network that we need.

Clone again and before finish, just choose the option Edit virtual hardware and then remove the interface(or change to a vSwitch network).

Found also a KB similar to this issue: KB2064681

Hope this can help bypass this error in the future.

Note: Share this article, if you think is worth sharing.[/fusion_builder_column][/fusion_builder_row][/fusion_builder_container]