From: Fabiano Rosas <farosas@suse.de>
To: Prasad Pandit <ppandit@redhat.com>
Cc: Peter Xu <peterx@redhat.com>,
qemu-devel@nongnu.org, berrange@redhat.com,
Prasad Pandit <pjp@fedoraproject.org>
Subject: Re: [PATCH v9 0/7] Allow to enable multifd and postcopy migration together
Date: Tue, 06 May 2025 10:40:37 -0300 [thread overview]
Message-ID: <87plglg8mi.fsf@suse.de> (raw)
In-Reply-To: <CAE8KmOzBZd=_FmmJTiwqKw5yPoYR7_+q+umpXBFJGPYZYuMgWw@mail.gmail.com>
Prasad Pandit <ppandit@redhat.com> writes:
> Hi,
>
> On Tue, 6 May 2025 at 00:34, Fabiano Rosas <farosas@suse.de> wrote:
>> >> # Running /ppc64/migration/multifd+postcopy/tcp/plain/cancel
>> >> # Using machine type: pseries-10.0
>> >> # starting QEMU: exec ./qemu-system-ppc64 -qtest
>> >> # {
>> >> # "error": {
>> >> # "class": "GenericError",
>> >> # "desc": "Postcopy is not supported: Userfaultfd not available: Function not implemented"
>> >> # }
>> >> # }
>> >
> ===
> [ ~]#
> ...
> PPC KVM module is not loaded. Try modprobe kvm_hv.
> qemu-system-ppc64: -accel kvm: failed to initialize kvm: Invalid argument
> qemu-system-ppc64: -accel kvm: ioctl(KVM_CREATE_VM) failed: Invalid argument
> PPC KVM module is not loaded. Try modprobe kvm_hv.
> qemu-system-ppc64: -accel kvm: failed to initialize kvm: Invalid argument
The tests should fallback to TCG and that should be enough to reproduce
this issue. I don't think you even need a ppc machine, the CI uses a
x86_64 container.
> [ ~]#
>
> [ ~]# modprobe kvm-hv
> modprobe: ERROR: could not insert 'kvm_hv': No such device
> [ ~]#
> [ ~]# ls -l /dev/kvm /dev/userfaultfd
> crw-rw-rw-. 1 root kvm 10, 232 May 6 07:06 /dev/kvm
> crw----rw-. 1 root root 10, 123 May 6 06:30 /dev/userfaultfd
> [ ~]#
> ===
>
> * I tried to reproduce this issue across multiple Power9 and Power10
> machines, but I -qtest could not run due to above errors.
>
There are several considerations to take into account with ppc64le, you
probably have either a distro version that doesn't provide the KVM
module or a machine that doesn't have KVM support at all.
>> We're missing a check on has_uffd for the multifd+postcopy tests.
>
> * If it is about missing the 'e->has_uffd' check, does that mean
> Postcopy tests are skipped on this machine because 'e->has_uffd' is
> false?
>
I haven't verified, but yes, the ones that check has_uffd should be
skipped.
I don't think you need to go to the extent to reproduce this. Look at
migrate_caps_check(), whenever postcopy-ram is enabled for the first
time, it will call postcopy_ram_supported_by_host(), so it follows that
any test that enables postcopy-ram must first check env->has_uffd.
>
> Thank you.
> ---
> - Prasad
prev parent reply other threads:[~2025-05-06 13:41 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 11:45 [PATCH v9 0/7] Allow to enable multifd and postcopy migration together Prasad Pandit
2025-04-11 11:45 ` [PATCH v9 1/7] migration/multifd: move macros to multifd header Prasad Pandit
2025-04-11 11:45 ` [PATCH v9 2/7] migration: refactor channel discovery mechanism Prasad Pandit
2025-04-17 16:07 ` Fabiano Rosas
2025-04-11 11:45 ` [PATCH v9 3/7] migration: Add save_postcopy_prepare() savevm handler Prasad Pandit
2025-04-17 16:07 ` Fabiano Rosas
2025-04-11 11:45 ` [PATCH v9 4/7] migration/ram: Implement save_postcopy_prepare() Prasad Pandit
2025-04-17 16:08 ` Fabiano Rosas
2025-04-11 11:45 ` [PATCH v9 5/7] migration: enable multifd and postcopy together Prasad Pandit
2025-04-11 11:45 ` [PATCH v9 6/7] tests/qtest/migration: consolidate set capabilities Prasad Pandit
2025-04-17 16:11 ` Fabiano Rosas
2025-04-11 11:45 ` [PATCH v9 7/7] tests/qtest/migration: add postcopy tests with multifd Prasad Pandit
2025-04-17 16:10 ` Fabiano Rosas
2025-04-16 0:31 ` [PATCH v9 0/7] Allow to enable multifd and postcopy migration together Fabiano Rosas
2025-04-16 12:59 ` Fabiano Rosas
2025-04-17 11:13 ` Prasad Pandit
2025-04-17 16:05 ` Fabiano Rosas
2025-04-23 22:50 ` Peter Xu
2025-04-29 12:51 ` Prasad Pandit
2025-04-29 13:04 ` Peter Xu
2025-04-29 13:28 ` Prasad Pandit
2025-04-29 13:47 ` Peter Xu
2025-04-29 15:20 ` Prasad Pandit
2025-04-29 15:49 ` Peter Xu
2025-05-05 19:01 ` Fabiano Rosas
2025-05-06 12:32 ` Prasad Pandit
2025-05-05 19:04 ` Fabiano Rosas
2025-05-06 12:38 ` Prasad Pandit
2025-05-06 13:40 ` Fabiano Rosas [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=87plglg8mi.fsf@suse.de \
--to=farosas@suse.de \
--cc=berrange@redhat.com \
--cc=peterx@redhat.com \
--cc=pjp@fedoraproject.org \
--cc=ppandit@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.