From: Prasad Pandit <ppandit@redhat.com>
To: "Arisetty, Chakri" <carisett@akamai.com>
Cc: Fabiano Rosas <farosas@suse.de>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"qemu-block@nongnu.org" <qemu-block@nongnu.org>,
Peter Xu <peterx@redhat.com>, Kevin Wolf <kwolf@redhat.com>,
Eric Blake <eblake@redhat.com>,
"Blew III, Will" <wblewiii@akamai.com>,
"Massry, Abraham" <amassry@akamai.com>,
"Tottenham, Max" <mtottenh@akamai.com>,
"Greve, Mark" <mgreve@akamai.com>
Subject: Re: Issue with QEMU Live Migration
Date: Mon, 26 Aug 2024 17:34:49 +0530 [thread overview]
Message-ID: <CAE8KmOzMFtw0oMQP2=EeiVic5TaK6dc2Fvy2=kcfp_nRg1bn9w@mail.gmail.com> (raw)
In-Reply-To: <5DBD942C-E192-46F8-9E73-20DD0A5D6983@akamai.com>
On Sun, 25 Aug 2024 at 22:40, Arisetty, Chakri <carisett@akamai.com> wrote:
> > - start the mirror job
> > - qmp_migrate
> > - once PRE_SWITCHOVER is reached, issue block-job-cancel
> > - qmp_migrate_continue
>
> We use exact same steps to do live migration. I repeated the test now
>
> Sure, as you suggested to rule out any incorrect usage, I repeated the test with above steps.
> once RAM migration state moved to pre-switchover, issued block-job-cancel. There are no more dirty blocks.
> But all the disk writes from 'pre-switchover' state to 'complete' state are lost.
> Thus, it is creating loss of customer data.
>
* How is 'issue block-job-cancel' command issued exactly at the
PRE_SWITCHOVER stage? virsh blockjob --abort?
* Recently a postcopy issue, wherein the migrated guest on the
destination machine hangs sometimes with migrate-postcopy but not with
virsh ---postcopy-after-precopy. It seems virsh(1) handles the switch
better. Wondering if it's similar with 'block-job-cancel'.
Thank you.
---
- Prasad
next prev parent reply other threads:[~2024-08-26 12:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-21 13:32 Issue with QEMU Live Migration Arisetty, Chakri
2024-08-21 13:56 ` Fabiano Rosas
2024-08-21 16:55 ` Arisetty, Chakri
2024-08-22 13:47 ` Fabiano Rosas
2024-08-23 13:30 ` Arisetty, Chakri
2024-08-23 13:41 ` Arisetty, Chakri
2024-08-23 14:42 ` Fabiano Rosas
2024-08-25 17:09 ` Arisetty, Chakri
2024-08-26 12:04 ` Prasad Pandit [this message]
2024-08-26 19:05 ` Arisetty, Chakri
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='CAE8KmOzMFtw0oMQP2=EeiVic5TaK6dc2Fvy2=kcfp_nRg1bn9w@mail.gmail.com' \
--to=ppandit@redhat.com \
--cc=amassry@akamai.com \
--cc=carisett@akamai.com \
--cc=eblake@redhat.com \
--cc=farosas@suse.de \
--cc=kwolf@redhat.com \
--cc=mgreve@akamai.com \
--cc=mtottenh@akamai.com \
--cc=peterx@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=wblewiii@akamai.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 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).