qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: mdroth@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH 1/1] qga: update docs with systemd suspend support info
Date: Tue, 13 Nov 2018 14:49:58 -0200	[thread overview]
Message-ID: <1ff5be0e-0023-2b78-0b4b-19cd23ec6fe3@gmail.com> (raw)
In-Reply-To: <914ac120-dcd1-06ac-7a97-5cc73b759cb0@gmail.com>



On 11/13/18 2:39 PM, Daniel Henrique Barboza wrote:
>
>
> On 11/13/18 2:32 PM, Eric Blake wrote:
>> On 11/13/18 10:09 AM, Daniel Henrique Barboza wrote:
>>> Commit 067927d62e ("qga: systemd hibernate/suspend/hybrid-sleep
>>> support") failed to update qapi-schema.json after adding systemd
>>> hibernate/suspend/hybrid-sleep capabilities to guest-suspend-* QGA
>>> commands.
>>>
>>> Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com>
>>> ---
>>>   qga/qapi-schema.json | 37 ++++++++++++++++++++++++++-----------
>>>   1 file changed, 26 insertions(+), 11 deletions(-)
>>
>>> +++ b/qga/qapi-schema.json
>>> @@ -532,12 +532,16 @@
>>>   #
>>>   # Suspend guest to disk.
>>>   #
>>> -# This command tries to execute the scripts provided by the 
>>> pm-utils package.
>>> -# If it's not available, the suspend operation will be performed by 
>>> manually
>>> -# writing to a sysfs file.
>>> +# This command attempts to suspend the guest using three 
>>> strategies, in this
>>> +# order:
>>>   #
>>> -# For the best results it's strongly recommended to have the pm-utils
>>> -# package installed in the guest.
>>> +# - systemd hibernate
>>> +# - pm-utils (via pm-hibernate)
>>> +# - manual write into sysfs
>>> +#
>>> +# If the guest does not have systemd hibernate support, the scripts 
>>> in pm-utils
>>> +# package are executed, in case pm-utils is available. Manual write 
>>> in sysfs
>>> +# is a last resort.
>>
>> Does this paragraph add any information compared to the earlier list?
>
> Perhaps we can remove the paragraph and add "if available" remarks in 
> the listing?
> Like:
>
> +# - systemd hibernate, if supported
> +# - pm-utils (via pm-hibernate), if pm-utils is installed
> +# - manual write into sysfs as a last resort
>
> Same for the other 2 cases below.

Actually, nevermind. Removing the extra paragraph and keeping the list as is
seems cleaner. One can easily assume that, in the lack of guest support of
systemd hibernate, the command will try the next option. Same thing
with pm-utils.

>
>>
>>>   #
>>>   # This command does NOT return a response on success. There is a 
>>> high chance
>>>   # the command succeeded if the VM exits with a zero exit status 
>>> or, when
>>> @@ -560,12 +564,16 @@
>>>   #
>>>   # Suspend guest to ram.
>>>   #
>>> -# This command tries to execute the scripts provided by the 
>>> pm-utils package.
>>> -# If it's not available, the suspend operation will be performed by 
>>> manually
>>> -# writing to a sysfs file.
>>> +# This command attempts to suspend the guest using three 
>>> strategies, in this
>>> +# order:
>>> +#
>>> +# - systemd suspend
>>> +# - pm-utils (via pm-suspend)
>>> +# - manual write into sysfs
>>>   #
>>> -# For the best results it's strongly recommended to have the pm-utils
>>> -# package installed in the guest.
>>> +# If the guest does not have systemd suspend support, the scripts 
>>> in pm-utils
>>> +# package are executed, in case pm-utils is available. Manual write 
>>> in sysfs
>>> +# is a last resort.
>>
>> Likewise.
>>
>>>   #
>>>   # IMPORTANT: guest-suspend-ram requires QEMU to support the 
>>> 'system_wakeup'
>>>   # command.  Thus, it's *required* to query QEMU for the presence 
>>> of the
>>> @@ -592,7 +600,14 @@
>>>   #
>>>   # Save guest state to disk and suspend to ram.
>>>   #
>>> -# This command requires the pm-utils package to be installed in the 
>>> guest.
>>> +# This command attempts to suspend the guest using three 
>>> strategies, in this
>>> +# order:
>>> +#
>>> +# - systemd hybrid-sleep
>>> +# - pm-utils (via pm-suspend-hybrid)
>>> +#
>>> +# If the guest does not have systemd hybrid-sleep support, the 
>>> scripts in
>>> +# pm-utils package are executed, in case pm-utils is available.
>>
>> "using three strategies" but a list of only 2 seems odd.
>>
>
> Copy/paste busted!

      reply	other threads:[~2018-11-13 17:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-13 16:09 [Qemu-devel] [PATCH 1/1] qga: update docs with systemd suspend support info Daniel Henrique Barboza
2018-11-13 16:32 ` Eric Blake
2018-11-13 16:39   ` Daniel Henrique Barboza
2018-11-13 16:49     ` Daniel Henrique Barboza [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=1ff5be0e-0023-2b78-0b4b-19cd23ec6fe3@gmail.com \
    --to=danielhb413@gmail.com \
    --cc=eblake@redhat.com \
    --cc=mdroth@linux.vnet.ibm.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 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).