From: Kevin Wolf <kwolf@suse.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Stop VM on ENOSPC error
Date: Wed, 14 Jan 2009 15:28:58 +0100 [thread overview]
Message-ID: <496DF6AA.7000302@suse.de> (raw)
In-Reply-To: <20090114135231.GA4559@redhat.com>
Gleb Natapov schrieb:
> On Wed, Jan 14, 2009 at 02:20:20PM +0200, Dor Laor wrote:
>> Daniel P. Berrange wrote:
>>> On Wed, Jan 14, 2009 at 02:03:58PM +0200, Gleb Natapov wrote:
>>>
>>>> And repeat last IDE command after VM restart.
>>>>
>>> How is a management application to determine when this occurs ?
>>> It is not desirable to poll for whether the VM is stopped all
>>> the time, and we need a reliable way to detect this, otherwise
>>> the user and/or mgmt app will just think their VM has hung.
>>>
>>> Thus I'd suggest we need an async notification of this event,
>>> and only enable this behaviour if the app controlling QEMU has
>>> explicitly enabled this notification / feature.
>>>
>>>
>> Correct. There is async message for it (==printf...).
>> Once the libmonitor is introduced it will be real async event
> There is not printf in this version of the patch, but I can add it if
> needed.
I think you should add it. Not only because of management applications
but also for the user. I for one would be at least a bit confused if my
VM stopped automatically without saying anything about the reason.
Kevin
next prev parent reply other threads:[~2009-01-14 14:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 12:03 [Qemu-devel] [PATCH] Stop VM on ENOSPC error Gleb Natapov
2009-01-14 12:11 ` Daniel P. Berrange
2009-01-14 12:20 ` Dor Laor
2009-01-14 13:52 ` Gleb Natapov
2009-01-14 14:28 ` Kevin Wolf [this message]
2009-01-14 16:46 ` Jamie Lokier
2009-01-14 17:30 ` Daniel P. Berrange
2009-01-14 18:29 ` Anthony Liguori
2009-01-14 18:37 ` Jamie Lokier
2009-01-14 16:47 ` Jamie Lokier
2009-01-14 17:01 ` Gleb Natapov
2009-01-14 18:39 ` Jamie Lokier
2009-01-14 19:24 ` Gleb Natapov
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=496DF6AA.7000302@suse.de \
--to=kwolf@suse.de \
--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).