migration-stress tests

migration-stress tests

[John Snow]

Heya folks:

I'm working on a series that removes the qemu.qmp package from the
qemu.git tree and notice that
tests/migration-stress/guestperf/engine.py makes use of the
QEMUMachine class (which depends on qemu.qmp) -- Can you please let me
know which test(s) utilize this code so I can ensure that there are no
disruptions to these tests after the pivot to utilizing an external
library?

If they aren't executed by "make check", could you please give me some
instructions for how they are normally run?

Thanks,
--js

Re: migration-stress tests

[Fabiano Rosas]

John Snow <jsnow@redhat.com> writes:

> Heya folks:
>
> I'm working on a series that removes the qemu.qmp package from the
> qemu.git tree and notice that
> tests/migration-stress/guestperf/engine.py makes use of the
> QEMUMachine class (which depends on qemu.qmp) -- Can you please let me
> know which test(s) utilize this code so I can ensure that there are no
> disruptions to these tests after the pivot to utilizing an external
> library?
>
> If they aren't executed by "make check", could you please give me some
> instructions for how they are normally run?
>
> Thanks,
> --js

Hi!

This is a little benchmarking tool we have. You need to first build the
guest workload (might need to install a couple static libraries):

cd build
make ./tests/migration-stress/initrd-stress.img

Then:

./run ../tests/migration-stress/guestperf.py --debug --verbose --output
output.json

It starts a guest and migrates it, but with the --debug flag you'll
already see lots of qemu.qmp debug messages flying past.

Beware this is poorly maintained, I just checked it's working, but it
might bite you. Let's us know!

Re: migration-stress tests

[John Snow]

On Fri, Jan 16, 2026 at 5:07 PM Fabiano Rosas <farosas@suse.de> wrote:
>
> John Snow <jsnow@redhat.com> writes:
>
> > Heya folks:
> >
> > I'm working on a series that removes the qemu.qmp package from the
> > qemu.git tree and notice that
> > tests/migration-stress/guestperf/engine.py makes use of the
> > QEMUMachine class (which depends on qemu.qmp) -- Can you please let me
> > know which test(s) utilize this code so I can ensure that there are no
> > disruptions to these tests after the pivot to utilizing an external
> > library?
> >
> > If they aren't executed by "make check", could you please give me some
> > instructions for how they are normally run?
> >
> > Thanks,
> > --js
>
> Hi!
>
> This is a little benchmarking tool we have. You need to first build the
> guest workload (might need to install a couple static libraries):
>
> cd build
> make ./tests/migration-stress/initrd-stress.img
>
> Then:
>
> ./run ../tests/migration-stress/guestperf.py --debug --verbose --output
> output.json

Oh, fantastic, you're already using the new runscript. That makes
things an awful lot easier for me. This is soon going to become
effectively *required* for you to run this script; I will add a little
error message into the script that makes this obvious in case you
forget it.

>
> It starts a guest and migrates it, but with the --debug flag you'll
> already see lots of qemu.qmp debug messages flying past.
>
> Beware this is poorly maintained, I just checked it's working, but it
> might bite you. Let's us know!
>

Thanks!
--js