From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:36242) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S37Up-0002Ro-Eq for qemu-devel@nongnu.org; Thu, 01 Mar 2012 10:00:50 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1S37UL-00063Z-MV for qemu-devel@nongnu.org; Thu, 01 Mar 2012 10:00:42 -0500 Received: from mx1.redhat.com ([209.132.183.28]:19569) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S37UL-00063F-E3 for qemu-devel@nongnu.org; Thu, 01 Mar 2012 10:00:13 -0500 Message-ID: <4F4F8FCD.7010106@redhat.com> Date: Thu, 01 Mar 2012 16:03:41 +0100 From: Kevin Wolf MIME-Version: 1.0 References: <4F4E9E31.50903@storagecraft.com> In-Reply-To: <4F4E9E31.50903@storagecraft.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] Add support for new image type List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Kai Meyer Cc: qemu-devel@nongnu.org Am 29.02.2012 22:52, schrieb Kai Meyer: > Is it possible to extend qemu to support a new image type? I have an > image type that is ready for consumption and I'm looking for the > integration point between qemu and the new image format. Which image format do you want to get integrated? Have a look at block/qcow2.c to get an idea of what a qemu block driver looks like. At the bottom of the file there is a struct that contains function pointers to all exported functions, so this is usually a good place to start exploring a driver. Kevin