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 2089431 - [RFE] RFE to allow enabling ZEROCOPY live migration through libvirt
Summary: [RFE] RFE to allow enabling ZEROCOPY live migration through libvirt
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: libvirt
Version: 9.1
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Jiri Denemark
QA Contact: Fangge Jin
URL:
Whiteboard:
Depends On: 1968509
Blocks: 2089433 2092752
TreeView+ depends on / blocked
 
Reported: 2022-05-23 16:17 UTC by Nils Koenig
Modified: 2023-01-12 06:54 UTC (History)
8 users (show)

Fixed In Version: libvirt-8.5.0-1.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-15 10:04:39 UTC
Type: Feature Request
Target Upstream Version: 8.5.0
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker LIBVIRTAT-13288 0 None None None 2022-09-20 06:49:31 UTC
Red Hat Issue Tracker LIBVIRTAT-13289 0 None None None 2022-09-20 06:49:31 UTC
Red Hat Issue Tracker LIBVIRTAT-13290 0 None None None 2022-09-20 06:49:31 UTC
Red Hat Issue Tracker LIBVIRTAT-13416 0 None None None 2022-09-20 16:52:21 UTC
Red Hat Issue Tracker RHELPLAN-123019 0 None None None 2022-05-23 16:51:01 UTC
Red Hat Product Errata RHSA-2022:8003 0 None None None 2022-11-15 10:05:06 UTC

Comment 2 Jiri Denemark 2022-06-24 12:33:22 UTC 
Pushed upstream as

commit 8744beecb36600e773c8a8c4823db2bf4b3e262d
Refs: v8.4.0-289-g8744beecb3
Author:     Jiri Denemark <jdenemar>
AuthorDate: Wed Jun 22 16:35:50 2022 +0200
Commit:     Jiri Denemark <jdenemar>
CommitDate: Thu Jun 23 16:45:39 2022 +0200

    Add VIR_MIGRATE_ZEROCOPY flag

    The flag can be used to enable zero-copy mechanism for migrating memory
    pages.

    Signed-off-by: Jiri Denemark <jdenemar>
    Reviewed-by: Ján Tomko <jtomko>

commit efa3baeae70fbdf4ab032ca485cb9272ee96bd50
Refs: v8.4.0-290-gefa3baeae7
Author:     Jiri Denemark <jdenemar>
AuthorDate: Wed Jun 22 16:36:53 2022 +0200
Commit:     Jiri Denemark <jdenemar>
CommitDate: Thu Jun 23 16:45:39 2022 +0200

    virsh: Add support for VIR_MIGRATE_ZEROCOPY flag

    Signed-off-by: Jiri Denemark <jdenemar>
    Reviewed-by: Ján Tomko <jtomko>

commit d375993ab314a41bca7ef6c846e07afc18c37774
Refs: v8.4.0-291-gd375993ab3
Author:     Jiri Denemark <jdenemar>
AuthorDate: Wed Jun 22 16:37:31 2022 +0200
Commit:     Jiri Denemark <jdenemar>
CommitDate: Thu Jun 23 16:45:39 2022 +0200

    qemu_migration: Implement VIR_MIGRATE_ZEROCOPY flag

    Resolves: https://gitlab.com/libvirt/libvirt/-/issues/306

    Signed-off-by: Jiri Denemark <jdenemar>
    Reviewed-by: Ján Tomko <jtomko>
Comment 6 Fangge Jin 2022-07-12 10:09:56 UTC 
Scenario 1(negative): parallel + zerocopy + native_tls + non-p2p
# virsh migrate uefi qemu+tcp://***/system --live --postcopy --bandwidth 10 --auto-converge  --zerocopy --parallel --tls
error: operation failed: job 'migration out' failed: Requested Zero Copy feature is not available: Invalid argument
Comment 7 Fangge Jin 2022-07-12 10:20:49 UTC 
Scenario 2(negative): non_parallel + zerocopy 
# virsh migrate uefi qemu+tcp://***/system --live --postcopy --bandwidth 10 --auto-converge  --zerocopy --parallel --tls [--p2p]
error: operation failed: job 'migration out' failed: Requested Zero Copy feature is not available: Invalid argument

Scenario 3: parallel + zerocopy
virsh migrate uefi qemu+tcp://dell-per640-09.lab.eng.pek2.redhat.com/system --live --postcopy --bandwidth 10 --auto-converge --zerocopy --parallel [--p2p]

Scenario 4: parallel + zerocopy, abort migration, then migrate again.
Comment 8 Fangge Jin 2022-07-14 03:16:17 UTC 
(In reply to Fangge Jin from comment #7)
> Scenario 2(negative): non_parallel + zerocopy 
> # virsh migrate uefi qemu+tcp://***/system --live --postcopy --bandwidth 10
> --auto-converge  --zerocopy --parallel --tls [--p2p]
> error: operation failed: job 'migration out' failed: Requested Zero Copy
> feature is not available: Invalid argument
Correct a typo here:
It should be:
# virsh migrate uefi qemu+tcp://***/system --live --postcopy --bandwidth 10 --auto-converge  --zerocopy --tls [--p2p]
error: Requested operation is not valid: zero-copy is only available for parallel migration
Comment 9 Fangge Jin 2022-07-14 10:48:30 UTC 
Hi Jirka

I did more testing today and found one issue about memlock limit. Could you please help to confirm whether this is a bug?
Steps:
1. Start vm, and check prlimit:
   # prlimit -p 38921 -l
   RESOURCE DESCRIPTION                             SOFT      HARD UNITS
   MEMLOCK  max locked-in-memory address space 134217728 134217728 bytes

2. Migrate vm, and check prlimit before migration completes:
   # virsh migrate uefi qemu+tcp://***/system --live --postcopy --bandwidth 10 --auto-converge  --zerocopy --p2p --parallel
   # prlimit -p 38921 -l
   RESOURCE DESCRIPTION                              SOFT       HARD UNITS
   MEMLOCK  max locked-in-memory address space 2147483648 2147483648 bytes

3. Kill source virtqemud before migration completes, migration will fail. But prlimit is not restored:
   # prlimit -p 38921 -l
   RESOURCE DESCRIPTION                              SOFT       HARD UNITS
   MEMLOCK  max locked-in-memory address space 2147483648 2147483648 bytes
   
Additional info:
1. If I abort migration by "virsh domjobabort", prlimit can be restored.
Comment 10 Jiri Denemark 2022-07-14 13:41:20 UTC 
(In reply to Fangge Jin from comment #9)
> 3. Kill source virtqemud before migration completes, migration will fail.
> But prlimit is not restored:
>    # prlimit -p 38921 -l
>    RESOURCE DESCRIPTION                              SOFT       HARD UNITS
>    MEMLOCK  max locked-in-memory address space 2147483648 2147483648 bytes

Do you just kill the daemon or do you even start it again. If you only kill it
and keep it stop, there's nothing that could restore the limit back. But if
you start the daemon again and the limit still stays the same, we have a bug
somewhere. The "qemu_migration: Restore original memory locking limit" commit
should be handling this, but I might have missed something there...
Comment 11 Fangge Jin 2022-07-14 14:12:40 UTC 
I just kill the daemon, but systemd will restart the daemon immediately and automatically.
Comment 12 Fangge Jin 2022-07-14 14:13:14 UTC 
(In reply to Fangge Jin from comment #11)
I just kill the daemon, but systemd will restart the daemon immediately and automatically when the daemon is killed.
Comment 13 Jiri Denemark 2022-07-14 14:30:08 UTC 
OK, thanks for confirming. Could you please file a separate BZ for this issue?
Comment 14 Fangge Jin 2022-07-15 02:21:08 UTC 
Bug filed for issue in Comment 9
Bug 2107424 - "mem lock limit" of qemu process is not restored when kill src virtqemud during zerocopy migration.
Comment 16 errata-xmlrpc 2022-11-15 10:04:39 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Low: libvirt security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:8003
Note You need to log in before you can comment on or make changes to this bug.