qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Stop VM on ENOSPC error
Date: Wed, 14 Jan 2009 12:11:48 +0000	[thread overview]
Message-ID: <20090114121147.GI24995@redhat.com> (raw)
In-Reply-To: <20090114120358.GS3267@redhat.com>

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.

Daniel
-- 
|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|

  reply	other threads:[~2009-01-14 12:11 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 [this message]
2009-01-14 12:20   ` Dor Laor
2009-01-14 13:52     ` Gleb Natapov
2009-01-14 14:28       ` Kevin Wolf
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=20090114121147.GI24995@redhat.com \
    --to=berrange@redhat.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).