Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
The difference of the steps for the above issue (comment 4) and bug 1066338 is:
This bug: Switching cache size between 512M and 1G for several time (about 4~5 times in my test) after migration starts.
Bug 1066338: Waiting for migration "remaining ram" becomes small, and before migration finish, change the cache size to 128M. So in that bug I only changed the migration cache size for once.
Comment 10Dr. David Alan Gilbert
2014-07-10 18:42:16 UTC
Hi Qunfang,
Can you retest this on the latest 7.0.z please
(at least qemu-kvm-1.5.3-60.el7_0.3 or newer)
and the current 7.1 world (at least qemu-kvm-1.5.3-63.el7)
I'm hoping this is fixed by the fixes in bz 1066338/bz1110191.
Thanks,
Dave
(In reply to Dr. David Alan Gilbert from comment #10)
> Hi Qunfang,
> Can you retest this on the latest 7.0.z please
> (at least qemu-kvm-1.5.3-60.el7_0.3 or newer)
> and the current 7.1 world (at least qemu-kvm-1.5.3-63.el7)
>
> I'm hoping this is fixed by the fixes in bz 1066338/bz1110191.
>
> Thanks,
>
> Dave
Hi, Dave
I just have a test on both rhel7.0-z build qemu-kvm-1.5.3-60.el7_0.5.x86_64.rpm and rhel7.1 build qemu-kvm-1.5.3-66.el7.x86_64.rpm, for each build I did ping-pong migration for 10 times. This issue could not be reproduced any more. Guest works well after migration. The test steps are the same as comment 0.
So, this bug should be fixed IMO.
Thanks,
Qunfang
Comment 12Dr. David Alan Gilbert
2014-07-11 08:04:12 UTC
Thanks Qunfang; marking as duplicate with bz 1066338.
*** This bug has been marked as a duplicate of bug 1066338 ***