All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liu Yuan <namei.unix@gmail.com>
To: MORITA Kazutaka <morita.kazutaka@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	sheepdog@lists.wpkg.org, qemu-devel@nongnu.org,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [sheepdog] [PATCH v3] sheepdog: fix loadvm operation
Date: Thu, 25 Apr 2013 20:32:42 +0800	[thread overview]
Message-ID: <5179226A.1010004@gmail.com> (raw)
In-Reply-To: <m2r4hz2agu.wl%morita.kazutaka@gmail.com>

On 04/25/2013 06:03 PM, MORITA Kazutaka wrote:
> The block driver tries to delete the vdi, but the sheepdog servers
> return "No such vdi" - I thought that something goes wrong in this
> case.
> 
> What's the scenario where the sheepdog servers return SD_RES_NO_VDI?
> Can we ignore it safely?

V2 has this problem, if we loadvm twice in a short of time that no
sd_create_branch is called in the time window, the second loadvm will
get this NO_VDI error. But with V3 we don't have this problem. Anyway it
is okay to printf message for this case for v3. I'll update v4.

Thanks,
Yuan

  reply	other threads:[~2013-04-25 12:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-24 16:47 [Qemu-devel] [PATCH v2] sheepdog: fix loadvm operation Liu Yuan
2013-04-25  4:12 ` Liu Yuan
2013-04-25  8:11   ` [Qemu-devel] [sheepdog] " MORITA Kazutaka
2013-04-25  8:27     ` Liu Yuan
2013-04-25  8:42 ` [Qemu-devel] [PATCH v3] " Liu Yuan
2013-04-25  9:40   ` [Qemu-devel] [sheepdog] " MORITA Kazutaka
2013-04-25  9:44     ` Liu Yuan
2013-04-25 10:03       ` MORITA Kazutaka
2013-04-25 12:32         ` Liu Yuan [this message]
2013-04-25 12:49 ` [Qemu-devel] [PATCH v4] " Liu Yuan
2013-04-25 13:06   ` [Qemu-devel] [sheepdog] " MORITA Kazutaka
2013-04-26  9:04     ` Liu Yuan
2013-04-26 11:39       ` Stefan Hajnoczi
2013-04-26 11:48         ` Liu Yuan
2013-04-26 11:41   ` [Qemu-devel] " Stefan Hajnoczi

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=5179226A.1010004@gmail.com \
    --to=namei.unix@gmail.com \
    --cc=kwolf@redhat.com \
    --cc=morita.kazutaka@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sheepdog@lists.wpkg.org \
    --cc=stefanha@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 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.