From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Denis V. Lunev" <den@virtuozzo.com>
Cc: "Marc-André Lureau" <marcandre.lureau@gmail.com>,
"Nikolai Barybin" <nikolai.barybin@virtuozzo.com>,
qemu-devel@nongnu.org, "Ani Sinha" <anisinha@redhat.com>
Subject: Re: [PATCH v4 2/2] dump: enhance win_dump_available to report properly
Date: Fri, 5 Jun 2026 17:10:21 +0100 [thread overview]
Message-ID: <aiL07TJlvZM8-ZAk@redhat.com> (raw)
In-Reply-To: <9bef9acb-3153-4ef8-b3c6-6ff6303336f5@virtuozzo.com>
On Thu, Jan 08, 2026 at 10:30:29AM +0100, Denis V. Lunev wrote:
> On 1/8/26 09:11, Marc-André Lureau wrote:
> > Hi Nikolai
> >
> > On Wed, Sep 24, 2025 at 12:30 PM Marc-André Lureau
> > <marcandre.lureau@redhat.com> wrote:
> >> Hi
> >>
> >> On Thu, Sep 11, 2025 at 4:37 PM Nikolai Barybin <nikolai.barybin@virtuozzo.com> wrote:
> >>> QMP query-dump-guest-memory-capability reports win dump as available for
> >>> any x86 VM, which is false.
> >>>
> >>> This patch implements proper query of vmcoreinfo and calculation of
> >>> guest note size. Based on that we can surely report whether win dump
> >>> available or not.
> >>>
> >>> To perform this I suggest to split dump_init() into dump_preinit() and
> >>> dump_init_complete() to avoid exausting copypaste in
> >>> win_dump_available().
> >>>
> >>> For further reference one may review this libvirt discussion:
> >>> https://lists.libvirt.org/archives/list/devel@lists.libvirt.org/thread/HJ3JRLWLGN3IKIC22OQ3PMZ4J3EFG5XB/#HJ3JRLWLGN3IKIC22OQ3PMZ4J3EFG5XB
> >>> [PATCH 0/4] Allow xml-configured coredump format on VM crash
> >>>
> >>> Signed-off-by: Nikolai Barybin <nikolai.barybin@virtuozzo.com>
> >>> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
> >>
> > Have you looked at my review & updated the patches? thanks
> I will send updated version next week after vacation. Nikolai has
> left Virtuozzo.
>
> Thank you for the reminder and best regards,
I don't recall seeing a followup v5 for this ? Were you still
interested in progressing this work ?
With regards,
Daniel
--
|: https://berrange.com ~~ https://hachyderm.io/@berrange :|
|: https://libvirt.org ~~ https://entangle-photo.org :|
|: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|
next prev parent reply other threads:[~2026-06-05 16:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-11 12:36 [PATCH v4 0/2] dump: enhance win_dump_available to report properly Nikolai Barybin
2025-09-11 12:36 ` [PATCH v4 1/2] dump: enhance dump_state_prepare fd initialization Nikolai Barybin
2025-09-11 12:36 ` [PATCH v4 2/2] dump: enhance win_dump_available to report properly Nikolai Barybin
2025-09-24 8:27 ` Marc-André Lureau
2026-01-08 8:11 ` Marc-André Lureau
2026-01-08 9:30 ` Denis V. Lunev
2026-06-05 16:10 ` Daniel P. Berrangé [this message]
2026-06-05 16:20 ` Denis V. Lunev
2025-09-23 16:33 ` [PATCH v4 0/2] " 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=aiL07TJlvZM8-ZAk@redhat.com \
--to=berrange@redhat.com \
--cc=anisinha@redhat.com \
--cc=den@virtuozzo.com \
--cc=marcandre.lureau@gmail.com \
--cc=nikolai.barybin@virtuozzo.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.