From: Kevin Wolf <kwolf@redhat.com>
To: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
Cc: pbonzini@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com,
dietmar@proxmox.com
Subject: Re: [Qemu-devel] [PATCH 0/4] export internal snapshot by qemu-nbd
Date: Fri, 19 Jul 2013 10:20:10 +0200 [thread overview]
Message-ID: <20130719082010.GB2992@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <51E8DCC4.3080508@linux.vnet.ibm.com>
Am 19.07.2013 um 08:29 hat Wenchao Xia geschrieben:
> 于 2013-7-17 22:23, Eric Blake 写道:
> >On 07/17/2013 08:03 AM, Wenchao Xia wrote:
> >>This series allow user to read internal snapshot's contents without qemu-img
> >>convert. Another purpose is that, when qemu is online and have taken an
> >>internal snapshot, let user invoke qemu-nbd to do any thing on it except write.
> >>
> >>This brings two interesting issues:
> >>1 is it safe to let qemu-nbd and qemu access that file at same time?
> >
> >Probably not, for the same reason we tell people to not use qemu-img
> >while qemu is active on a file.
> >
> For external case, or backing chain, qemu-nbd export while qemu is
> active, do you think it is OK?
>
> base->imageA
>
> qemu-nbd export base
> qemu use imageA.
It depends. If you use 'qemu-nbd -r' to export it, it's okay. The
reason is that it's allowed to have either one process opening the file
read-write, or an arbitrary number of processes opening the file
read-only. In the case of qemu using imageA, base is only opened
read-only, so qemu-nbd can be another read-only user.
Kevin
next prev parent reply other threads:[~2013-07-19 8:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-17 14:03 [Qemu-devel] [PATCH 0/4] export internal snapshot by qemu-nbd Wenchao Xia
2013-07-17 14:03 ` [Qemu-devel] [PATCH 1/4] snapshot: distinguish id and name in load_tmp Wenchao Xia
2013-07-17 14:03 ` [Qemu-devel] [PATCH 2/4] qemu-nbd: support internal snapshot export Wenchao Xia
2013-07-17 14:03 ` [Qemu-devel] [PATCH 3/4] qemu-nbd: add doc for " Wenchao Xia
2013-07-26 8:11 ` Stefan Hajnoczi
2013-07-29 1:57 ` Wenchao Xia
2013-07-29 7:39 ` Stefan Hajnoczi
2013-07-17 14:03 ` [Qemu-devel] [PATCH 4/4] qemu-iotests: add 057 internal snapshot export with qemu-nbd case Wenchao Xia
2013-07-17 14:23 ` [Qemu-devel] [PATCH 0/4] export internal snapshot by qemu-nbd Eric Blake
2013-07-17 15:21 ` Kevin Wolf
2013-07-18 2:28 ` Wenchao Xia
2013-07-18 7:15 ` Fam Zheng
2013-07-19 6:29 ` Wenchao Xia
2013-07-19 8:20 ` Kevin Wolf [this message]
2013-07-22 5:20 ` Wenchao Xia
2013-07-18 5:43 ` Stefan Hajnoczi
2013-07-19 9:03 ` Wenchao Xia
2013-07-19 9:19 ` Kevin Wolf
2013-07-19 10:02 ` Wenchao Xia
2013-07-22 2:10 ` Fam Zheng
2013-07-22 3:26 ` Wenchao Xia
2013-07-25 2:30 ` Wenchao Xia
2013-07-25 8:06 ` Stefan Hajnoczi
2013-07-26 2:23 ` Wenchao Xia
2013-07-26 8:20 ` Stefan Hajnoczi
2013-07-29 2:05 ` Wenchao Xia
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=20130719082010.GB2992@dhcp-200-207.str.redhat.com \
--to=kwolf@redhat.com \
--cc=dietmar@proxmox.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=xiawenc@linux.vnet.ibm.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).