RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 658143 - RFE: Allow to change the maximum migration downtime
Summary: RFE: Allow to change the maximum migration downtime
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.0
Hardware: All
OS: Linux
high
medium
Target Milestone: rc
: ---
Assignee: Daniel Veillard
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 561935
Blocks: 658861
TreeView+ depends on / blocked
 
Reported: 2010-11-29 14:10 UTC by RHEL Program Management
Modified: 2013-01-11 03:36 UTC (History)
23 users (show)

Fixed In Version: libvirt-0.8.1-27.el6_0.1
Doc Type: Enhancement
Doc Text:
Live migration of a guest could take an exceptionally long time to converge to the switchover point if the guest was very busy. By allowing to increase the downtime setting of a guest, migration is more likely to complete. However, libvirt was sending an incorrectly formatted request to increase the downtime setting of a guest. With this update, libvirt correctly sends the downtime setting request.
Clone Of:
: 658861 (view as bug list)
Environment:
Last Closed: 2011-04-14 16:19:10 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0446 0 normal SHIPPED_LIVE libvirt bug fix update 2011-04-14 16:18:21 UTC

Description RHEL Program Management 2010-11-29 14:10:06 UTC 
This bug has been copied from bug #561935 and has been proposed
to be backported to 6.0 z-stream (EUS).
Comment 3 Jiri Denemark 2010-11-29 23:52:10 UTC 
Patches built into libvirt-0.8.1-27.el6_0.1
Comment 4 zhanghaiyan 2010-12-01 02:26:33 UTC 
Verified this bug PASS with libvirt-0.8.1-27.el6_0.1
- kernel-2.6.32-71.el6.x86_64
- qemu-kvm-0.12.1.2-2.113.el6.x86_64
- qemu-img-0.12.1.2-2.113.el6.x86_64

Test steps
1. Set up migration environment on source host A and destination host B
2. Start domain 'vm1' on host A
   # virsh start vm1
3. In domain vm1 load high i/o with iozone
   # ./iozone -a
4. Live migrate vm1 to host B WITHOUT setting MaxShutdown time
   # virsh migrate --live vm1 qemu+ssh://10.66.93.59/system
5. Migrate the guest back from destination host to source host
6. Live migrate vm1 to host B WITH setting MaxShutdown time
   # virsh migrate --live vm1 qemu+ssh://10.66.93.59/system
7. Before step6 is finished, open another terminal, set maximum tolerable downtime of the domain.
   # virsh migrate-setmaxdowntime  --domain vm1 --downtime 1000
8. Check the /var/log/libvirt/libvirtd.log file on source host


Actual result
Step4
Migration is slow and lasts about 6 seconds.Guest is changed from running -> shutoff status on source host.
Step 7
Migration is faster than in step4. Guest is changed from running -> paused -> shutoff status on source host.
Step 8
Qemu command 'migrate_set_downtime' should be executed successfully as below
.....

04:22:25.213: debug : qemuMonitorJSONCommandWithFd:217 : Send command '{"execute":"migrate_set_downtime","arguments":{"value":1.000000}}' for write with FD -1
04:22:25.214: debug : qemuMonitorJSONIOProcessLine:115 : Line [{"return": {}}]
04:22:25.214: debug : qemuMonitorJSONIOProcess:188 : Total used 16 bytes out of 16 available in buffer
04:22:25.214: debug : qemuMonitorJSONCommandWithFd:222 : Receive command reply ret=0 errno=0 14 bytes '{"return": {}}'
......

Will change this bug status to VERIFIED after it is changed to ON_QA
Comment 5 zhanghaiyan 2010-12-21 07:14:57 UTC 
Verified this bug PASS with libvirt-0.8.1-27.el6_0.2.x86_64
- kernel-2.6.32-71.13.1.el6.x86_64
- qemu-kvm-0.12.1.2-2.113.el6_0.5.x86_64

Test steps and actual result are the same in comment 4
Comment 7 koka xiong 2011-01-31 08:20:19 UTC 
Verified with
libvirt: libvirt-0.8.1-27.el6_0.3
kernel: kernel-2.6.32-71.16.1.el6
qemu-kvm: qemu-kvm-0.12.1.2-2.113.el6_0.6

Test steps
1. Set up migration environment on source host A and destination host B
2. Start domain 'vm1' on host A
   # virsh start vm1
3. In domain vm1 load high i/o with iozone
   # ./iozone -a
4. Live migrate vm1 to host B WITHOUT setting MaxShutdown time
   # virsh migrate --live vm1 qemu+ssh://10.66.93.59/system
5. Migrate the guest back from destination host to source host
6. Live migrate vm1 to host B WITH setting MaxShutdown time
   # virsh migrate --live vm1 qemu+ssh://10.66.93.59/system
7. Before step6 is finished, open another terminal, set maximum tolerable
downtime of the domain.
   # virsh migrate-setmaxdowntime  --domain vm1 --downtime 1000
8. Check the /var/log/libvirt/libvirtd.log file on source host


Actual result
Step4
Migration is slow and lasts about 6 seconds.Guest is changed from running ->
shutoff status on source host.
Step 7
Migration is faster than in step4. Guest is changed from running -> paused ->
shutoff status on source host.
Step 8
Qemu command 'migrate_set_downtime' should be executed successfully as below
.....

04:22:25.213: debug : qemuMonitorJSONCommandWithFd:217 : Send command
'{"execute":"migrate_set_downtime","arguments":{"value":1.000000}}' for write
with FD -1
04:22:25.214: debug : qemuMonitorJSONIOProcessLine:115 : Line [{"return": {}}]
04:22:25.214: debug : qemuMonitorJSONIOProcess:188 : Total used 16 bytes out of
16 available in buffer
04:22:25.214: debug : qemuMonitorJSONCommandWithFd:222 : Receive command reply
ret=0 errno=0 14 bytes '{"return": {}}'
......
Comment 8 errata-xmlrpc 2011-04-14 16:19:10 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/RHBA-2011-0446.html
Comment 9 Martin Prpič 2011-04-15 14:18:24 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Live migration of a guest could take an exceptionally long time to converge to the switchover point if the guest was very busy. By allowing to increase the downtime setting of a guest, migration is more likely to complete. However, libvirt was sending an incorrectly formatted request to increase the downtime setting of a guest. With this update, libvirt correctly sends the downtime setting request.
Note You need to log in before you can comment on or make changes to this bug.