From: Jeff Cody <jcody@redhat.com>
To: Supriya Kannery <supriyak@linux.vnet.ibm.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Shrinidhi Joshi <spjoshi31@gmail.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
qemu-devel@nongnu.org, Luiz Capitulino <lcapitulino@redhat.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [Qemu-devel] [v2 Patch 0/9]block: Image file reopen and dynamic host pagecache change
Date: Thu, 09 Aug 2012 00:26:05 -0400 [thread overview]
Message-ID: <50233BDD.1000000@redhat.com> (raw)
In-Reply-To: <20120730213409.21536.7589.sendpatchset@skannery.in.ibm.com>
On 07/30/2012 05:34 PM, Supriya Kannery wrote:
> For changing host pagecache setting of a running VM, it is
> important to have a safe way of reopening its image file.
>
> V1 introduced:
> * a generic way to reopen image files safely.
> In this approach, before reopening an image, for each
> block driver, its state will be stashed. Incase preparation,
> (bdrv_reopen_prepare) for reopening returns success, the stashed
> state will be cleared (bdrv_reopen_commit) and reopened state will
> be used further. Incase preparation of reopening returns failure,
> the state of the driver will be rolled back (bdrv_reopen_abort)
> to the stashed state. This approach is implemented for raw-posix,
> raw-win32, vmdk, qcow, qcow2 and qed block drivers.
>
> * qmp and hmp command 'block_set_hostcache' using which host
> pagecache setting for a block device can be changed
> when the VM is running.
>
> * BDRVReopenState, a generic structure which can be
> extended by each of the block drivers to reopen
> respective image files.
>
> V2:
> * Changed ordering of patches such that code changes related to
> generic framework for safely reopening images gets applied first.
>
> * For block drivers not having bdrv_reopen_xx functions
> implemented, return "feature not supported" error.
>
> Testing:
> =======
> [Thanks! to Yoganananth Subramanian for helping out with testing]
>
> Steps:
> 1) boot up guest image of different formats qed, raw, qcow2, vmdk
> 2) run iozone in these guests
> command: iozone -a
> 3) view cache setting of image file through qemu monitor
> command: info block
> "hostcache =" 0/1 should be displayed
> 4) Toggle hostcache value using block_set_hostcache
> command: block_set_hostcache virtio0 on
> 5) Disable and enable hostcache at randon intervals while iozone is
> running inside guest.
> command: block_set_hostcache virtio0 on/off
> 6) Info block should reflect toggled hostcache value
> and iozone should complete without any issue
>
> Results:
> Verified above steps for raw-posix, qcow2, qed and vmdk images.
> raw-posix, qed and vmdk images (split files) worked fine. With
> qcow2 image getting an error of double free after iozone running
> for a while.
I believe the double free you are seeing above is due to closing the
refcount at the end of qcow2_reopen_commit() (see comments on patch
5/9). Whenever that image is closed with bdrv_close(),
qcow2_refcount_close() is called again.
I had to make just a few small changes to the patches to get them
working for reopen() calls that had file access permission changes
(r/o->r/w), so I will try and document each of these changes in replies
to your other patches.
I applied the changes in my other replies your patches to my github branch
so they would work for going from r/o->r/w->r/o, for testing block commit:
https://github.com/codyprime/qemu-kvm-jtc/commits/jtc-live-commit-v3
I only made patches for qcow2 and raw-posix, which is what I have been
testing with block commit (although I imagine the changes for the other
formats are similar).
Another thought, that is more design oriented: as it currently is,
reopen() is not transactional for multiple BlockDriverStates. It would
be nice if we could queue up multiple BDSs to reopen into a transaction,
and only perform the commit() if the prepare() was successful for all of
the BDS entries. Perhaps using something like QSIMPLEQ could be useful
to accomplish this.
I think this is especially important for formats like qcow2, where we
need to reopen both the bs and bs->file.
>
> To Do:
> ======
> * Debug the issue with qcow2 image and resolve asap.
> * Enhance code around dup3 in raw-posix to fall back to
> dup2/dup when dup3 is not supported by OS.
> * Do some more extensive testing, especially with qcow2 and
> qed drivers.
>
> New block command added:
> "block_set_hostcache"
> -- Sets hostcache parameter for block device while guest is running.
>
> Usage:
> block_set_hostcache <device> <option>
> <device> = block device
> <option> = on/off
>
> qemu/block.c | 79 ++++++++++++++++++++++
> qemu/block.h | 5 +
> qemu/block/qcow.c | 108 ++++++++++++++++++++++++++++++
> qemu/block/qcow2.c | 175 +++++++++++++++++++++++++++++++++++++++++++++++++
> qemu/block/qed.c | 103 ++++++++++++++++++++++++++++
> qemu/block/raw-posix.c | 121 +++++++++++++++++++++++++++++++++
> qemu/block/raw-win32.c | 96 ++++++++++++++++++++++++++
> qemu/block/raw.c | 20 +++++
> qemu/block/vmdk.c | 103 ++++++++++++++++++++++++++++
> qemu/block_int.h | 12 +++
> qemu/blockdev.c | 19 +++++
> qemu/hmp-commands.hx | 15 ++++
> qemu/hmp.c | 11 ++
> qemu/hmp.h | 1
> qemu/qapi-schema.json | 21 ++++-
> qemu/qemu-common.h | 1
> qemu/qmp-commands.hx | 24 ++++++
> 17 files changed, 912 insertions(+), 2 deletions(-)
>
>
>
>
>
prev parent reply other threads:[~2012-08-09 4:26 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-30 21:34 [Qemu-devel] [v2 Patch 0/9]block: Image file reopen and dynamic host pagecache change Supriya Kannery
2012-07-30 21:34 ` [Qemu-devel] [v2 Patch 1/9]block: Framework for reopening image files safely Supriya Kannery
2012-08-01 15:51 ` Stefan Hajnoczi
2012-08-02 20:19 ` Luiz Capitulino
2012-08-14 8:54 ` Supriya Kannery
2012-08-08 21:13 ` Jeff Cody
2012-08-14 9:21 ` Supriya Kannery
2012-08-09 4:26 ` Jeff Cody
2012-08-09 9:20 ` Kevin Wolf
2012-08-09 13:02 ` Jeff Cody
2012-08-14 10:24 ` Supriya Kannery
2012-07-30 21:34 ` [Qemu-devel] [v2 Patch 2/9]block: raw-posix image file reopen Supriya Kannery
2012-07-31 17:17 ` Eric Blake
2012-08-01 6:18 ` Kevin Wolf
2012-08-03 22:32 ` Jeff Cody
2012-08-14 10:53 ` Supriya Kannery
2012-08-09 4:26 ` Jeff Cody
2012-08-10 13:45 ` Corey Bryant
2012-08-14 11:13 ` Supriya Kannery
2012-08-14 11:35 ` Kevin Wolf
2012-07-30 21:34 ` [Qemu-devel] [v2 Patch 3/9]block: raw-win32 " Supriya Kannery
2012-07-30 21:35 ` [Qemu-devel] [v2 Patch 4/9]block: vmdk " Supriya Kannery
2012-07-31 17:43 ` Eric Blake
2012-07-30 21:35 ` [Qemu-devel] [v2 Patch 5/9]block: qcow2 " Supriya Kannery
2012-08-09 4:26 ` Jeff Cody
2012-08-09 9:37 ` Kevin Wolf
2012-07-30 21:35 ` [Qemu-devel] [v2 Patch 7/9]block: qed " Supriya Kannery
2012-07-30 21:36 ` [Qemu-devel] [v2 Patch 9/9]block: Enhance "info block" to display host cache setting Supriya Kannery
2012-07-31 17:47 ` Eric Blake
2012-07-31 20:33 ` [Qemu-devel] [v2 Patch 0/9]block: Image file reopen and dynamic host pagecache change Jeff Cody
2012-08-01 17:11 ` Supriya Kannery
2012-08-01 18:36 ` [Qemu-devel] [v2 Patch 6/9]block: qcow image file reopen Supriya Kannery
2012-08-01 18:44 ` [Qemu-devel] [v2 Patch 8/9]block: Cmd "block_set_hostcache" for dynamic cache change Supriya Kannery
2012-08-01 19:21 ` Eric Blake
2012-08-02 20:36 ` Luiz Capitulino
2012-08-31 19:32 ` Jeff Cody
2012-08-09 4:26 ` Jeff Cody [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=50233BDD.1000000@redhat.com \
--to=jcody@redhat.com \
--cc=hch@lst.de \
--cc=kwolf@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=spjoshi31@gmail.com \
--cc=stefanha@gmail.com \
--cc=supriyak@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).