From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IG3SK-0003vw-Lw for qemu-devel@nongnu.org; Tue, 31 Jul 2007 21:56:56 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IG3SI-0003v7-VM for qemu-devel@nongnu.org; Tue, 31 Jul 2007 21:56:56 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IG3SI-0003v3-QN for qemu-devel@nongnu.org; Tue, 31 Jul 2007 21:56:54 -0400 Received: from mout.perfora.net ([74.208.4.194]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IG3SI-0003z6-CQ for qemu-devel@nongnu.org; Tue, 31 Jul 2007 21:56:54 -0400 Message-ID: <46AFE651.8080306@filteredperception.org> Date: Tue, 31 Jul 2007 20:48:01 -0500 From: dmc MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] RFE- snapshot data storage location configurable Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org I have a pretty ugly patch against qemu 0.8 which allows the location of data used with the -snapshot feature to be somewhere other than /var/tmp. I have a use-case where I am creating many gigabytes of changes to disk in snapshot mode. When 0.9 came out, I looked, but it seemed less than trivial to update my patch, which was a pretty ugly hack to begin with. I don't suppose anybody else thinks this would be a useful feature? Or at least someone who can rattle off the top of their heads the sorts of things I should keep in mind while trying to put it together myself? A further extension, which I would like, but is also more complex to add, would be the ability to specify -snapshot, _per device_. thanks, -dmc