Bug 541731

Summary: kvm: migration: mechanism to make older savevm versions to be emitted on some cases
Product: Red Hat Enterprise Linux 5 Reporter: Eduardo Habkost <ehabkost>
Component: kvmAssignee: Juan Quintela <quintela>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: high    
Version: 5.5CC: cpelland, llim, summer, tburke, virt-maint, ykaul
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: kvm-83-142.el5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-03-30 07:54:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 527722    
Bug Blocks: 541921, 542665, 552529    

Description Eduardo Habkost 2009-11-26 21:16:48 UTC
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.

Comment 1 Dor Laor 2009-11-30 13:47:58 UTC
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.

Comment 11 errata-xmlrpc 2010-03-30 07:54:13 UTC
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