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.

Description of problem:

  When migrating to a file using "migrate exec:" (as with libvirt's virDomainSave), saving 2GB of state can take upwards of 10 minutes on a quite high-performance server.

  This happens only when the file descriptor on which the migration is occurring is marked non-blocking; commenting out the socket_set_nonblock() call in migration-exec.c:exec_start_outgoing_migration works around the issue, resulting in a save-to-disk time on the scale of 2 minutes for this same guest.

  The symptoms of the issue were described by detail by Pierre Riteau in a mailing list post titled "[BUG] Regression of exec migration" on 8/27/2009.

  Anthony Ligouri noted in the following thread that setting this socket to be non-blocking is essential for live migration support. However, this performance degredation happens even when a guest is stopped during the migration process.

Version-Release number of selected component (if applicable):

  qemu-kvm-0.12.1.2-2.17.el6.x86_64

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release. It has
been denied for the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **

Please consider this for a future release (ie. RHEL6.1).

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