From: "Nicholas Piggin" <npiggin@gmail.com>
To: "Shaoqin Huang" <shahuang@redhat.com>, <kvm@vger.kernel.org>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Nico Boehr" <nrb@linux.ibm.com>
Subject: Re: [kvm-unit-tests PATCH 0/3] migration: fixes and multiple migration
Date: Sun, 30 Jul 2023 20:06:13 +1000 [thread overview]
Message-ID: <CUFF8EFNM4SV.AMHSXOE0DB04@wheely> (raw)
In-Reply-To: <c7469514-145b-2a90-9352-6d83c254afcc@redhat.com>
On Fri Jul 28, 2023 at 6:44 PM AEST, Shaoqin Huang wrote:
> Hi Nicholas,
>
> With the patch3 arch-run: Support multiple migrations.
>
> The run_test.sh will fail on the migration test on arm64 platform. But
> the patch1 and patch2 looks good, only apply these two patches the
> migration test works good.
>
> I haven't had time to investigate it. But first let you know that.
Hey, thanks for testing. I noticed some problem with it too. Let's
leave patch 3 out for now, I'll post an update with some users
added and hopefully bugs fixed.
Thanks,
Nick
prev parent reply other threads:[~2023-07-30 10:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 3:39 [kvm-unit-tests PATCH 0/3] migration: fixes and multiple migration Nicholas Piggin
2023-07-25 3:39 ` [kvm-unit-tests PATCH 1/3] migration: Fix test harness hang on fifo Nicholas Piggin
2023-07-28 7:20 ` Nico Boehr
2023-07-25 3:39 ` [kvm-unit-tests PATCH 2/3] migration: Fix test harness hang if source does not reach migration point Nicholas Piggin
2023-07-28 7:34 ` Nico Boehr
2023-07-30 10:03 ` Nicholas Piggin
2023-09-25 11:14 ` Nico Boehr
2023-10-16 18:32 ` Thomas Huth
2023-10-19 7:55 ` Nico Boehr
2023-10-19 8:10 ` Thomas Huth
2023-07-25 3:39 ` [kvm-unit-tests PATCH 3/3] arch-run: Support multiple migrations Nicholas Piggin
2023-07-28 8:44 ` [kvm-unit-tests PATCH 0/3] migration: fixes and multiple migration Shaoqin Huang
2023-07-30 10:06 ` Nicholas Piggin [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=CUFF8EFNM4SV.AMHSXOE0DB04@wheely \
--to=npiggin@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=nrb@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=shahuang@redhat.com \
--cc=thuth@redhat.com \
/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.