From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Flq4u-00084B-7C for qemu-devel@nongnu.org; Thu, 01 Jun 2006 12:31:20 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Flq4r-00081s-RY for qemu-devel@nongnu.org; Thu, 01 Jun 2006 12:31:19 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Flq4r-00081p-PX for qemu-devel@nongnu.org; Thu, 01 Jun 2006 12:31:17 -0400 Received: from [65.74.133.6] (helo=mail.codesourcery.com) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1FlqB8-0006Xo-Tw for qemu-devel@nongnu.org; Thu, 01 Jun 2006 12:37:47 -0400 From: Paul Brook Subject: Re: [Qemu-devel] block device loopback Date: Thu, 1 Jun 2006 17:31:13 +0100 References: <5370f2820606010908w7204c1afr17132397ec625c76@mail.gmail.com> In-Reply-To: <5370f2820606010908w7204c1afr17132397ec625c76@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200606011731.14325.paul@codesourcery.com> 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 > The aim of this driver is quite similar to the loop driver but instead of > "emulating" a partition, it emulates a IDE Hard Drive and give an access to > it via /dev/vdX and it's partition via /dev/vdXpY. > Perhaps you will wonder why i use the qemu's mailing-list for this problem > : - i don't know exactly where i can find a way to achieve this project ; - > i wonder how you read your hda.disk without using qemu ; I'd be surprised if this problem wasn't already fixed by the kernel device-mapper infrastructure. I also think this list is the wrong place to discuss this. There's nothing qemu specific about it. > - i would like to know how qemu fix the virtual drive property inside the > virtual machine (cylinders, sectors, etc...) ; qemu doesn't know or care about the contents of the image. It's entirely up to the guest OS. Paul