From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=41738 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1PKXA6-0003aO-Tb
	for qemu-devel@nongnu.org; Mon, 22 Nov 2010 09:14:32 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <kwolf@redhat.com>) id 1PKXA5-00054D-OD
	for qemu-devel@nongnu.org; Mon, 22 Nov 2010 09:14:30 -0500
Received: from mx1.redhat.com ([209.132.183.28]:36607)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kwolf@redhat.com>) id 1PKXA5-00053k-HA
	for qemu-devel@nongnu.org; Mon, 22 Nov 2010 09:14:29 -0500
Received: from int-mx02.intmail.prod.int.phx2.redhat.com
	(int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12])
	by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id oAMEESwH005065
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK)
	for <qemu-devel@nongnu.org>; Mon, 22 Nov 2010 09:14:28 -0500
Message-ID: <4CEA7AFD.2050609@redhat.com>
Date: Mon, 22 Nov 2010 15:15:25 +0100
From: Kevin Wolf <kwolf@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH 1/1] NBD isn't used by qemu-img,	so don't
	link qemu-img against NBD objects
References: <1290184248-30078-1-git-send-email-Jes.Sorensen@redhat.com>
	<4CEA6102.3020709@redhat.com> <4CEA794F.40506@redhat.com>
In-Reply-To: <4CEA794F.40506@redhat.com>
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit
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.nongnu.org/archive/html/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: Jes Sorensen <Jes.Sorensen@redhat.com>
Cc: qemu-devel@nongnu.org

Am 22.11.2010 15:08, schrieb Jes Sorensen:
> On 11/22/10 13:24, Kevin Wolf wrote:
>> Am 19.11.2010 17:30, schrieb Jes.Sorensen@redhat.com:
>>> From: Jes Sorensen <Jes.Sorensen@redhat.com>
>>>
>>> Signed-off-by: Jes Sorensen <Jes.Sorensen@redhat.com>
>>
>> You're compiling the nbd block driver out here. This is certainly not
>> what you were attempting. (However, it's the only way to make it work,
>> because otherwise qemu-img will need the top-level nbd.o)
>>
>> qemu-img -help before this change shows:
>>
>> Supported formats: raw cow qcow vdi vmdk cloop dmg bochs vpc vvfat qcow2
>> parallels nbd blkdebug sheepdog blkverify host_cdrom host_floppy
>> host_device file tftp ftps ftp https http
>>
>> Afterwards:
>>
>> Supported formats: raw cow qcow vdi vmdk cloop dmg bochs vpc vvfat qcow2
>> parallels blkdebug sheepdog blkverify host_cdrom host_floppy host_device
>> file tftp ftps ftp https http
> 
> I am aware of that, but what on earth is qemu-img doing with NBD in the
> first place? Doesn't make much sense to me.

The same as it's doing with file, host_device or http: Accessing images.
Start an NBD server (e.g. with qemu-nbd) and try something like qemu
-hda nbd:localhost. This is how you use the nbd block driver.

Kevin