From: Eric Blake <eblake@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Ekaterina Tumanova" <tumanova@linux.vnet.ibm.com>,
"Alexander Graf" <agraf@suse.de>,
qemu-devel <qemu-devel@nongnu.org>,
"Rabin Vincent" <rabin@rab.in>,
"Christian Borntraeger" <borntraeger@de.ibm.com>,
"Jens Freimann" <jfrei@linux.vnet.ibm.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH 1/2] Split out dump-guest-memory memory mapping code
Date: Wed, 24 Apr 2013 10:23:58 -0600 [thread overview]
Message-ID: <5178071E.7020908@redhat.com> (raw)
In-Reply-To: <20130424115022.2ac2667d@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2011 bytes --]
On 04/24/2013 09:50 AM, Luiz Capitulino wrote:
>> This raises an interesting question about introspection - how will
>> management apps (such as libvirt) be able to determine whether the
>> paging command is supported for a given architecture? Do we need to
>> expand the 'MachineInfo' QMP datatype so that 'query-machines' can tell
>> us whether a given machine will support or reject attempts to set
>> 'paging':true during 'dump-guest-memory'?
>
> Is libvirt going to query this for the automatic dump feature?
Probably. Right now, libvirt has already exposed the paging option to
users, and uses the try-and-fail approach of reporting back any error
message from QMP if the dump command fails. But we've had error reports
in the past against libvirt that the error reported by qemu isn't always
the sanest, and that sometimes it is much nicer to have libvirt detect
in advance that a qemu command cannot succeed than it is to do a
try-and-fail approach. There's also a matter of clean rollbacks;
libvirt has to set up some state when starting a dump command, and has
to undo that state if try-and-fail reported an error; whereas a
capability detection can avoid having to set up any state in the first
place.
>
> I'm asking this because if the fact that an arch doesn't support memory
> dump is only visible to human users, then try & fail doesn't seem bad.
Introspection can't hurt, even if libvirt doesn't use it right away. It
may be the sort of thing where we commit the initial capability with
try-and-fail handling, then down the road, decide whether the error
quality is good enough; it also seems like introspection is the sort of
thing that is easy to backport, even if the introspection does not go in
at the same time as the original feature, where improved error messages
becomes a quality-of-implementation value-added by distro packagers.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]
next prev parent reply other threads:[~2013-04-24 16:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 15:30 [Qemu-devel] [PATCH 0/2] s390: dump-guest-memory support Jens Freimann
2013-04-23 15:30 ` [Qemu-devel] [PATCH 1/2] Split out dump-guest-memory memory mapping code Jens Freimann
2013-04-23 15:41 ` Eric Blake
2013-04-23 15:54 ` Jens Freimann
2013-05-17 10:18 ` Andreas Färber
2013-04-24 15:50 ` Luiz Capitulino
2013-04-24 16:23 ` Eric Blake [this message]
2013-04-24 17:25 ` Luiz Capitulino
2013-04-24 17:07 ` Ekaterina Tumanova
2013-04-24 19:57 ` Eric Blake
2013-05-17 10:58 ` [Qemu-devel] [RFC qom-cpu] dump: Unconditionally compile Andreas Färber
2013-05-17 11:12 ` Paolo Bonzini
2013-05-20 20:44 ` Andreas Färber
2013-04-23 15:30 ` [Qemu-devel] [PATCH 2/2] s390: dump guest memory implementation Jens Freimann
2013-04-26 17:12 ` Alexander Graf
2013-04-29 11:39 ` Ekaterina Tumanova
2013-04-30 10:02 ` Alexander Graf
2013-04-30 10:20 ` Ekaterina Tumanova
2013-04-30 10:25 ` Alexander Graf
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=5178071E.7020908@redhat.com \
--to=eblake@redhat.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=jfrei@linux.vnet.ibm.com \
--cc=lcapitulino@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rabin@rab.in \
--cc=tumanova@linux.vnet.ibm.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).