Search the VMware Knowledge Base (KB)
View by Article ID

Hardware changes to a VM fail in vCloud Director with the error: PBM error occurred during PreMigrateCheckCallback (2149108)

  • 0 Ratings

Symptoms

  • Making a hardware change to a virtual machine in vCloud Director fails with the error:
[ a7b3753c-7bbc-4eb7-8bab-f988adf6ba1e ] A general system error occurred: PBM error occurred during PreMigrateCheckCallback: vmodl.fault.InvalidArgument;

vCenter Server task (moref: task-5271236) failed in vCenter Server '' (c32898a5-dabe-4d95-98aa-f3b9d5849232).
- A general system error occurred: PBM error occurred during PreMigrateCheckCallback: vmodl.fault.InvalidArgument;

  • In the C:\ProgramData\VMware\vCenterServer\logs\vmware-vpx\vpxd.log file, you see entries similar to:
2017-02-03T15:43:49.570+01:00 error vpxd[166784] [Originator@6876 sub=pbm opID=vcd-a7b3753c-7bbc-4eb7-8bab-f988adf6ba1e;activity=urn:uuid:ec338913-efa8-43f5-94b4-3b9dd17fc46d-32-33] PBMCallback: PbmCallBack::FillRelocateSpecWithSourceVmDisk: Invalid disk vm-30284:2002 profile setting. Host and datastore are not changed. May use VM reconfig instead
2017-02-03T15:43:49.570+01:00 error vpxd[166784] [Originator@6876 sub=pbm opID=vcd-a7b3753c-7bbc-4eb7-8bab-f988adf6ba1e;activity=urn:uuid:ec338913-efa8-43f5-94b4-3b9dd17fc46d-32-33] PBMCallback: PbmService::HandleInternalFaultMessage: PBM error occurred during PreMigrateCheckCallback: vmodl.fault.InvalidArgument;

2016-12-21T10:41:57.826+01:00 error vpxd[04304] [Originator@6876 sub=pbm opID=vcd-b0e380d8-a945-405f-955f-a45d0dedb5bc;activity=urn:uuid:2d3c6c42-c2bc-4810-8e8d-90143a965825-a2-e5] PBMCallback: PbmCallBack::FillRelocateSpecWithSourceVmHome: VM PbmCallBack::FillRelocateSpecWithSourceVmHome: Invalid VM home profile setting. Host and datastore are not changed. May use VM reconfig instead
2016-12-21T10:41:57.826+01:00 error vpxd[04304] [Originator@6876 sub=pbm opID=vcd-b0e380d8-a945-405f-955f-a45d0dedb5bc;activity=urn:uuid:2d3c6c42-c2bc-4810-8e8d-90143a965825-a2-e5] PBMCallback: PbmService::HandleInternalFaultMessage: PBM error occurred during PreMigrateCheckCallback: vmodl.fault.InvalidArgument;

2016-12-21T10:41:57.852+01:00 error vpxd[04304] [Originator@6876 sub=vpxLro opID=vcd-b0e380d8-a945-405f-955f-a45d0dedb5bc;activity=urn:uuid:2d3c6c42-c2bc-4810-8e8d-90143a965825-a2-e5] [VpxLRO] Unexpected Exception: vmodl.fault.SystemError
2016-12-21T10:41:57.852+01:00 info vpxd[04304] [Originator@6876 sub=vpxLro opID=vcd-b0e380d8-a945-405f-955f-a45d0dedb5bc;activity=urn:uuid:2d3c6c42-c2bc-4810-8e8d-90143a965825-a2-e5] [VpxLRO] -- FINISH task-internal-793610
2016-12-21T10:41:57.852+01:00 info vpxd[04304] [Originator@6876 sub=Default opID=vcd-b0e380d8-a945-405f-955f-a45d0dedb5bc;activity=urn:uuid:2d3c6c42-c2bc-4810-8e8d-90143a965825-a2-e5] [VpxLRO] -- ERROR task-internal-793610 -- -- VmprovWorkflow: vmodl.fault.SystemError:
--> Result:
--> (vmodl.fault.SystemError) {
--> faultCause = (vmodl.MethodFault) null,
--> reason = "PBM error occurred during PreMigrateCheckCallback: vmodl.fault.InvalidArgument;
--> ",
--> msg = ""
--> }
--> Args:
-->

Note: This log excerpt is an example. Date, time, and environmental variables may vary depending on your environment.

 

Cause

This issue occurs when, as a part of the hardware reconfiguration, first attempt to relocate a virtual machine is made where the host and datastore do not change.

Resolution

This is a known issue in VMware vCloud Director that can affect the ability to make hardware changes to a virtual machine.

To work around the issue perform these steps:
 
Note: These steps may migrate VMs to different datastores when changing the Storage Policy of the VMs.
  1. Create a new (Temp-SP) Storage Policy in vCenter Server which is accessible to all shared vCD used Datastores in vCenter Server.
  2. Add the newly created Storage Policy to the Provider VDCs and Org VDCs where affected VMs reside.
  3. Go to the VM Properties of an affected VM.
  4. In the General Tab make a note of the current Storage Policy and change it to Temp-SP.
  5. In the Hardware Tab, make a note of the current Storage Policy settings of the Disks and change them to Temp-SP.
  6. Click OK.

    Note: You should see the VM update moving it to the new Storage Policy.

  7. After the change is complete, access the VM Properties again and set the Storage Policies back to their previous settings.
  8. Click OK.

    Note: You should see the VM update again changing the Storage Policy information to as it was before.

  9. Repeat for other affected VMs.
  10. Remove Temp-SP from vCloud Director and vCenter Server after the successful completion of the steps.
After completing the preceding steps, the affected VMs should be manageable via vCloud Director again.

Additional Information

To be alerted when this article is updated, click Subscribe to Document in the Actions box.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 0 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 0 Ratings
Actions
KB: