From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1F4lEu-0000ZO-9s
	for qemu-devel@nongnu.org; Thu, 02 Feb 2006 15:39:36 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1F4lEq-0000Sr-KM
	for qemu-devel@nongnu.org; Thu, 02 Feb 2006 15:39:34 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1F4lEV-0008Q2-0r
	for qemu-devel@nongnu.org; Thu, 02 Feb 2006 15:39:11 -0500
Received: from [65.74.133.4] (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 1F4lDO-0007sk-2B
	for qemu-devel@nongnu.org; Thu, 02 Feb 2006 15:38:02 -0500
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] VMDK block device as a kernel module ?
Date: Thu, 2 Feb 2006 20:35:49 +0000
References: <aa1862360602010354i341a8b96ja494ea45a99a8605@mail.gmail.com>
In-Reply-To: <aa1862360602010354i341a8b96ja494ea45a99a8605@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200602022035.49546.paul@codesourcery.com>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

On Wednesday 01 February 2006 11:54, Bogdan Harjoc wrote:
> Hello,
>
> I haven't been watching qemu development too closely but AFAIK (and
> a quick search through the list archives says the same thing) there
> haven't been any efforts in building the vmware block driver as a kernel
> (block device) driver.

Probably because that's got nothing to do with qemu.

I expect you could probably use the kernel DM or loopback layers.

Paul