To support migration from hosts that have additiona savevm fields (e.g. containing the fix to #531701) to hosts that don't have it, we need a mechanism to force the savevm code to use an older version. The current proposal is to use the -M option to tie savevm versions to specific machine-types.
For all rhel5.4.* incarnations, we'll always use -M rhel5.4 as a default, unless instructed differently by mgmt. So, newer vdsm/libvirt should start using rhel5.4.x for newer VMs, otherwise ATM pvclock will drift.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2010-0271.html