All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Stop VM on ENOSPC error
Date: Wed, 14 Jan 2009 21:24:39 +0200	[thread overview]
Message-ID: <20090114192439.GA9379@redhat.com> (raw)
In-Reply-To: <20090114183954.GI6431@shareable.org>

On Wed, Jan 14, 2009 at 06:39:55PM +0000, Jamie Lokier wrote:
> Gleb Natapov wrote:
> > On Wed, Jan 14, 2009 at 04:47:17PM +0000, Jamie Lokier wrote:
> > > Gleb Natapov wrote:
> > > > And repeat last IDE command after VM restart.
> > > 
> > > If there are multiple AIOs in flight when you get ENOSPC, you may need
> > > to repeat all of them.
> > > 
> > IDE does not support multiple outstanding commands. For SCSI that will have
> > to be done though. What my patch is missing is PIO mode support, but this
> > should be easy to add.
> 
> For some reason I imagined IDE with TCQ(sp?), or SATA with NCQ :-)
> 
But we don't support it yet.

> What about multiple IDE controllers.  If the VM is stopped (for any
> reason, not just ENOSPC) and resumed later, do _other_ controllers'
> AIOs in flight need to be replayed?  Are they saved in snapshot state?
> 
I think (not sure) vmstop stops only CPU execution, but all outstanding IOs
will complete.

--
			Gleb.

      reply	other threads:[~2009-01-14 19:26 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
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 [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=20090114192439.GA9379@redhat.com \
    --to=gleb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.