From: Peter Xu <peterx@redhat.com>
To: Li Zhijian <lizhijian@fujitsu.com>
Cc: Fabiano Rosas <farosas@suse.de>,
qemu-devel@nongnu.org, Laurent Vivier <lvivier@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v2 1/2] qtest/migration/rdma: Enforce RLIMIT_MEMLOCK >= 128MB requirement
Date: Fri, 9 May 2025 11:33:23 -0400 [thread overview]
Message-ID: <aB4gQ7AxNNv7C2PD@x1.local> (raw)
In-Reply-To: <20250509014211.1272640-1-lizhijian@fujitsu.com>
On Fri, May 09, 2025 at 09:42:10AM +0800, Li Zhijian wrote:
> Ensure successful migration over RDMA by verifying that RLIMIT_MEMLOCK is
> set to at least 128MB. This allocation is necessary due to the requirement
> to pin significant portions of guest memory, typically exceeding 100MB
> in this test, while the remainder is transmitted as compressed zero pages.
>
> Otherwise, it will fail with:
> stderr:
> qemu-system-x86_64: cannot get rkey
> qemu-system-x86_64: error while loading state section id 2(ram)
> qemu-system-x86_64: load of migration failed: Operation not permitted
> qemu-system-x86_64: rdma migration: recv polling control error!
> qemu-system-x86_64: RDMA is in an error state waiting migration to abort!
> qemu-system-x86_64: failed to save SaveStateEntry with id(name): 2(ram): -1
> qemu-system-x86_64: Channel error: Operation not permitted
>
> Reported-by: Peter Xu <peterx@redhat.com>
> Signed-off-by: Li Zhijian <lizhijian@fujitsu.com>
Thanks, this works for me.
I'll queue this one first separately.
--
Peter Xu
prev parent reply other threads:[~2025-05-09 15:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 1:42 [PATCH v2 1/2] qtest/migration/rdma: Enforce RLIMIT_MEMLOCK >= 128MB requirement Li Zhijian via
2025-05-09 1:42 ` [PATCH v2 2/2] qtest/migration/rdma: Add test for rdma migration with ipv6 Li Zhijian via
2025-05-09 15:32 ` Peter Xu
2025-05-12 5:49 ` Zhijian Li (Fujitsu) via
2025-05-09 15:33 ` Peter Xu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aB4gQ7AxNNv7C2PD@x1.local \
--to=peterx@redhat.com \
--cc=farosas@suse.de \
--cc=lizhijian@fujitsu.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).