From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1F4Orn-0003yd-Tw
	for qemu-devel@nongnu.org; Wed, 01 Feb 2006 15:46:18 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1F4NKB-0006R7-0D
	for qemu-devel@nongnu.org; Wed, 01 Feb 2006 14:07:31 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1F4Gck-00009Z-FL
	for qemu-devel@nongnu.org; Wed, 01 Feb 2006 06:58:11 -0500
Received: from [66.249.92.196] (helo=uproxy.gmail.com)
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1F4GbO-00081Z-LY
	for qemu-devel@nongnu.org; Wed, 01 Feb 2006 06:56:46 -0500
Received: by uproxy.gmail.com with SMTP id u2so271770uge
	for <qemu-devel@nongnu.org>; Wed, 01 Feb 2006 03:54:55 -0800 (PST)
Message-ID: <aa1862360602010354i341a8b96ja494ea45a99a8605@mail.gmail.com>
Date: Wed, 1 Feb 2006 13:54:55 +0200
From: Bogdan Harjoc <harjoc@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_11403_26231513.1138794895174"
Subject: [Qemu-devel] VMDK block device as a kernel module ?
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

------=_Part_11403_26231513.1138794895174
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

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.

This would of course be a complete waste of somebody's time _except_
(arguably) for something like booting a kernel natively but mounting root
(et cetera) from a .vmdk file.

I would equally appreciate any pointer towards somebody's attempt at
doing this or an opinion on whether it is worth doing at all (although
the FUSE framework would probably make a first attempt worthwhile).


Cheers,
Bogdan.

------=_Part_11403_26231513.1138794895174
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hello, <br><br>I haven't been watching qemu development too closely but AFA=
IK (and<br>a quick search through the list archives says the same thing) th=
ere <br>haven't been any efforts in building the vmware block driver as a k=
ernel
<br>(block device) driver. <br><br>This would of course be a complete waste=
 of somebody's time _except_ <br>(arguably) for something like booting a ke=
rnel natively but mounting root <br>(et cetera) from a .vmdk file.<br><br>
I would equally appreciate any pointer towards somebody's attempt at <br>do=
ing this or an opinion on whether it is worth doing at all (although<br>the=
 FUSE framework would probably make a first attempt worthwhile).<br><br>
<br>Cheers,<br>Bogdan.<br><br>

------=_Part_11403_26231513.1138794895174--