qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Konstantin Kostiuk <kkostiuk@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@redhat.com>
Cc: qemu-devel@nongnu.org, Michael Roth <michael.roth@amd.com>,
	 Kfir Manor <kfir@daynix.com>, Yan Vugenfirer <yan@daynix.com>
Subject: Re: [PATCH 0/3] qga/win/vss: add VSS backup type options
Date: Wed, 15 Feb 2023 04:21:54 -0600	[thread overview]
Message-ID: <CAPMcbCqQAca01aagME6v7Z3G1zsQGW7wKpqFRBvL5M79mfKbQQ@mail.gmail.com> (raw)
In-Reply-To: <CAMxuvaw0Z6YKm5hVF3=eB1nVR1_9rR4Mo_HeD4bfnz91nYfdGg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2824 bytes --]

On Tue, Feb 14, 2023 at 3:20 AM Marc-André Lureau <
marcandre.lureau@redhat.com> wrote:

> Hi
>
> On Mon, Feb 13, 2023 at 8:20 PM Konstantin Kostiuk <kkostiuk@redhat.com>
> wrote:
>
>> Hi Marc-André,
>>
>> Can you please review this patch set?
>>
>> Best Regards,
>> Konstantin Kostiuk.
>>
>>
>> On Thu, Feb 9, 2023 at 10:50 AM Kfir Manor <kfir@daynix.com> wrote:
>>
>>> Resolves: https://gitlab.com/qemu-project/qemu/-/issues/775
>>>
>>> The problem, VSS backup type VSS-FULL (the only available VSS backup
>>> type currently) can break other backups that use VSS-FULL(for example,
>>> Bareos-Fullbackup).
>>>
>>> Fix, add other backup types.
>>>
>>> Implementation, put the desired backup type number inside Regkey value
>>> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\QEMU Guest Agent VSS
>>> Provider\VssOption, so that the program can query the desired backup type.
>>>
>>> VSS backup types:
>>> number   type
>>> 1        VSS_BT_FULL
>>> 2        VSS_BT_INCREMENTAL
>>> 3        VSS_BT_DIFFERENTIAL
>>> 4        VSS_BT_LOG
>>> 5        VSS_BT_COPY
>>>
>>> for more information about the different backup types
>>> https://learn.microsoft.com/en-us/windows/win32/vss/vss-backup-state
>>>
>>> Additionally, the program would work as before with VSS-FULL in cases
>>> where VssOption doesn't exist, or VssOption value isn't a known backup type.
>>>
>>
> The patch series looks ok (just minor stylistic changes could be made),
> but I do not fully understand the way qga-vss.dll works in details for
> freeze/thaw.
>
> My understanding is that FIFREEZE do not exist on win32, so we call VSS to
> tell (some) apps to flush/freeze pretending a backup is going on, then we
> get notified on completion by our own provider (CommitSnapshots) and wait
> there for thaw (1 min while VM is suspended?).
>
> But I don't understand how this interacts with other providers (real
> backup solutions), and why they are involved/conflict as described in
> https://gitlab.com/qemu-project/qemu/-/issues/775.
>

This is a very good question. To understand the reason for the conflict we
should dig deeper into VSS.
For some reason, MS provides different VSS backup types. Currently, we
don't use other types but we got
a request from the community. I think this is ok, to add more freedom of
configuration if someone wants it.
Anyway, the default behavior is not changed.


>
>
>>
>>> Kfir Manor (3):
>>>   add VssOption to installer
>>>   query VSS backup type
>>>   requester_freeze changes
>>>
>>>  qga/installer/qemu-ga.wxs   |  4 ++++
>>>  qga/vss-win32/requester.cpp | 41 ++++++++++++++++++++++++++++++++++++-
>>>  qga/vss-win32/vss-handles.h |  3 +++
>>>  3 files changed, 47 insertions(+), 1 deletion(-)
>>>
>>> --
>>> 2.38.1
>>>
>>>

[-- Attachment #2: Type: text/html, Size: 4754 bytes --]

      reply	other threads:[~2023-02-15 10:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-09  8:50 [PATCH 0/3] qga/win/vss: add VSS backup type options Kfir Manor
2023-02-09  8:50 ` [PATCH 1/3] qga/win/installer: add VssOption to installer Kfir Manor
2023-02-15 10:22   ` Konstantin Kostiuk
2023-02-09  8:50 ` [PATCH 2/3] qga/win/vss: query VSS backup type Kfir Manor
2023-02-15 10:23   ` Konstantin Kostiuk
2023-02-09  8:50 ` [PATCH 3/3] qga/win/vss: requester_freeze changes Kfir Manor
2023-02-15 10:23   ` Konstantin Kostiuk
2023-02-13 16:20 ` [PATCH 0/3] qga/win/vss: add VSS backup type options Konstantin Kostiuk
2023-02-14  9:20   ` Marc-André Lureau
2023-02-15 10:21     ` Konstantin Kostiuk [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=CAPMcbCqQAca01aagME6v7Z3G1zsQGW7wKpqFRBvL5M79mfKbQQ@mail.gmail.com \
    --to=kkostiuk@redhat.com \
    --cc=kfir@daynix.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=michael.roth@amd.com \
    --cc=qemu-devel@nongnu.org \
    --cc=yan@daynix.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).