Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 511376

Summary: Possible to crash a guest by setting migration speed
Product: Red Hat Enterprise Linux 5 Reporter: Glauber Costa <gcosta>
Component: kvmAssignee: Glauber Costa <gcosta>
Status: CLOSED DUPLICATE QA Contact: Lawrence Lim <llim>
Severity: medium Docs Contact:
Priority: low    
Version: 5.4CC: tburke, tools-bugs, virt-maint, ykaul
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-01-21 12:58:53 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:

Description Glauber Costa 2009-07-14 20:48:18 UTC 
Description of problem:

qemu-kvm segfaults when one tries to change a migration speed after a migration has finished (in any state). I consider this pretty harsh, since a small mistake can lead to a guest crash. To be honest, I have no idea how I never came across this before.


How reproducible:
100 %

Steps to Reproduce:
In the monitor of src machine:
1. migrate <params>
2. wait until it fails/finishes
3. migrate_set_speed <whatever>
  
Actual results:
crash

Expected results:
migrate_set_speed is ignored, since it makes no sense to set speed of a migration that does not exist.

Additional info:
The problem exists upstream too, and a patch was sent by me today.
The patch (if accepted in its current state) is pretty trivial, and do not introduce further risks. Given a harm/risk ratio, I say we should consider it for inclusion as soon as upstream takes it.
Comment 1 Glauber Costa 2009-07-20 14:18:51 UTC 
Followup: committed upstream.
Comment 2 Glauber Costa 2010-01-21 12:58:53 UTC 

*** This bug has been marked as a duplicate of bug 522887 ***