From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GuCn7-0005oT-De for qemu-devel@nongnu.org; Tue, 12 Dec 2006 13:55:49 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GuCn4-0005oE-Rp for qemu-devel@nongnu.org; Tue, 12 Dec 2006 13:55:47 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GuCn4-0005oB-N2 for qemu-devel@nongnu.org; Tue, 12 Dec 2006 13:55:46 -0500 Received: from [80.91.229.2] (helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1GuCn4-000811-K7 for qemu-devel@nongnu.org; Tue, 12 Dec 2006 13:55:46 -0500 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1GuCmn-0000uy-M7 for qemu-devel@nongnu.org; Tue, 12 Dec 2006 19:55:29 +0100 Received: from 62.87.55.189 ([62.87.55.189]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 12 Dec 2006 19:55:29 +0100 Received: from sfandino by 62.87.55.189 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 12 Dec 2006 19:55:29 +0100 From: Salvador Fandino Date: Tue, 12 Dec 2006 20:00:37 +0100 Message-ID: References: <20061212171340.GA24143@nevyn.them.org> <20061212173322.5126.qmail@web26813.mail.ukl.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit In-Reply-To: <20061212173322.5126.qmail@web26813.mail.ukl.yahoo.com> Sender: news Subject: [Qemu-devel] Re: RE : Re: Re: NBD server for QEMU images 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 Sylvain Petreolle wrote: >>>> It's mostly intended to be used for accessing the files inside QEMU disk >>>> images locally, without having to launch a virtual machine and accessing >>>> then from there. >>> mount -o loop does this. >> How is everybody missing the point? :-) mount -o loop doesn't mount >> qcow images. >> > Would be that difficult to write a qcow fs module ? well, it would mean adapting the qemu disk image handling code to run in kernel mode (or just reimplementing the required functionality), and wrapping it inside a block device driver similar to 'loop'. My solution is much simpler because it's just a small adapter (600 lines of C) that links with the unmodified qemu source and it runs in user space. Cheers, - Salva