qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: qemu-devel@nongnu.org, quintela@redhat.com
Subject: [Qemu-devel] Re: [PATCH V2] savevm: use error_report for vmstate_save error
Date: Fri, 07 Jan 2011 17:27:10 +0100	[thread overview]
Message-ID: <4D273EDE.1070003@web.de> (raw)
In-Reply-To: <1294416650.3214.9.camel@x201>

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

Am 07.01.2011 17:10, Alex Williamson wrote:
> On Fri, 2011-01-07 at 17:03 +0100, Jan Kiszka wrote:
>> Am 07.01.2011 16:58, Alex Williamson wrote:
>>> If migration is done in the background with the -d option, mon is
>>> NULL and this error message is lost.  Instead use error_report().
>>>
>>> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
>>
>> Reviewed-by: Jan Kiszka <jan.kiszka@siemens.com>
>>
>> As already at it: Is this the only error during migration that can get
>> lost this way?
> 
> On the migration source side, I think so.  All the save callbacks are
> return void, so device saves aren't allow to fail.  The unmigratable
> device registration is the only way I know to trigger an error on this
> end.  Thanks,

Hmm, thinking about this again, wouldn't it be a better user experience
to check this in advance, at a time where the issuing console is still
listening?

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]

  reply	other threads:[~2011-01-07 16:27 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-07  7:18 [Qemu-devel] [PATCH] savevm: print migration failure to stderr rather than monitor Alex Williamson
2011-01-07  8:51 ` [Qemu-devel] " Jan Kiszka
2011-01-07 15:39   ` Alex Williamson
2011-01-07 15:46     ` Jan Kiszka
2011-01-07 15:56       ` Alex Williamson
2011-01-07 15:58 ` [Qemu-devel] [PATCH V2] savevm: use error_report for vmstate_save error Alex Williamson
2011-01-07 16:03   ` [Qemu-devel] " Jan Kiszka
2011-01-07 16:10     ` Alex Williamson
2011-01-07 16:27       ` Jan Kiszka [this message]
2011-01-07 18:41         ` Alex Williamson
2011-01-07 18:39   ` [Qemu-devel] [PATCH v3] savevm: Fix no_migrate Alex Williamson
2011-01-07 18:47     ` [Qemu-devel] " Jan Kiszka
2011-01-09  9:57       ` Michael S. Tsirkin
2011-01-09 11:44         ` Blue Swirl
2011-01-07 22:13     ` [Qemu-devel] [PATCH v4] " Alex Williamson
2011-01-09 10:02       ` [Qemu-devel] " Michael S. Tsirkin
2011-01-09 10:47       ` Michael S. Tsirkin
2011-01-10 17:47         ` Alex Williamson
2011-01-10 21:19           ` Michael S. Tsirkin
2011-01-10 10:24       ` Daniel P. Berrange
2011-01-10 14:52         ` Alex Williamson
2011-01-11 21:39       ` [Qemu-devel] [PATCH v5] " Alex Williamson
2011-01-11 22:39         ` [Qemu-devel] " Michael S. Tsirkin

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=4D273EDE.1070003@web.de \
    --to=jan.kiszka@web.de \
    --cc=alex.williamson@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.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).