ldm list -l Causes ldmd to Dump Core After Upgrading From Logical Domains 1.1 to Logical Domains 1.2

Bug ID 6855534: When upgrading the control domain OS image from a previous release of Logical Domains, ensure that you preserve the constraints database file on the control domain. See Saving and Restoring the Logical Domains Constraints Database File in Logical Domains 1.2 Administration Guide.

If you were unable to preserve the constraints database, do not populate the control domain with a constraints database that does not match the running configuration. Such a mismatch could result in the Logical Domains Manager aborting when the ldm list -l command is issued, as follows:

primary# ldm list -l ldg0
Invalid response
primary#

Workaround: To recover, remove any existing constraints database files on the upgraded control domain. Then, use the svcadm restart ldmd command to restart the Logical Domains Manager and to resume normal operations.