From: "Wangjing(Hogan)" via <qemu-devel@nongnu.org>
To: "Markus Armbruster" <armbru@redhat.com>,
"Daniel P.Berrangé" <berrange@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"marcandre.lureau@redhat.com" <marcandre.lureau@redhat.com>,
"Wangxin (Alexander)" <wangxinxin.wang@huawei.com>
Subject: Re: [PATCH] dump: introduce dump-cancel QMP command
Date: Thu, 21 Jul 2022 11:25:06 +0000 [thread overview]
Message-ID: <1758bfebd35b4d3a9a9c3dc809251e2b@huawei.com> (raw)
> Daniel P. Berrangé <berrange@redhat.com> writes:
>
> > On Thu, Jul 21, 2022 at 02:21:18PM +0800, Hogan Wang via wrote:
> >> There's no way to cancel the current executing dump process, lead to
> >> the virtual machine manager daemon((e.g. libvirtd) cannot restore the
> >> dump job after daemon restart.
> >>
> >> Add the 'cancelling' and 'cancelled' dump states.
> >>
> >> Use 'dump-cancel' qmp command Set the dump state as 'cancelling'.
> >> The dump process check the 'cancelling' state and break loops.
> >> The 'cancelled' state mark the dump process cancelled success.
> >
> > On the one hand this patch is fairly simple which is obviously
> > desirable.
> >
> > On the other hand though, this feels like it is further re-inventing
> > the jobs concept.
> >
> > IMHO ideally the 'dump' command probably ought to get a 'job-id'
> > parameter, and integrate with the generic background jobs framework.
> > This would unlock the ability to use existing commands like
> > 'job-cancel', 'job-pause', 'job-resume', 'queyr-jobs' to interact with
> > it.
>
> Seconded.
>
> Hogan Wang, would you be interested in rebasing the dump feature onto the jobs infrastructure?
Yes! I'm glad to do this, but it'll take some time.
next reply other threads:[~2022-07-21 11:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 11:25 Wangjing(Hogan) via [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-22 8:56 [PATCH] dump: introduce dump-cancel QMP command Wangjing(Hogan) via
2022-07-21 6:21 Hogan Wang via
2022-07-21 8:05 ` Marc-André Lureau
2022-07-21 8:13 ` Daniel P. Berrangé
2022-07-21 10:57 ` Markus Armbruster
2022-07-21 11:40 ` Daniel P. Berrangé
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=1758bfebd35b4d3a9a9c3dc809251e2b@huawei.com \
--to=qemu-devel@nongnu.org \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=hogan.wang@huawei.com \
--cc=marcandre.lureau@redhat.com \
--cc=wangxinxin.wang@huawei.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).