From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/1] NBD isn't used by qemu-img, so don't link qemu-img against NBD objects
Date: Mon, 22 Nov 2010 15:08:15 +0100 [thread overview]
Message-ID: <4CEA794F.40506@redhat.com> (raw)
In-Reply-To: <4CEA6102.3020709@redhat.com>
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.
Cheers,
Jes
next prev parent reply other threads:[~2010-11-22 14:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 16:30 [Qemu-devel] [PATCH 1/1] NBD isn't used by qemu-img, so don't link qemu-img against NBD objects Jes.Sorensen
2010-11-20 17:22 ` Andreas Färber
2010-11-20 17:39 ` Stefan Hajnoczi
2010-11-20 18:04 ` Andreas Färber
2010-11-20 18:31 ` Stefan Hajnoczi
2010-11-21 12:30 ` Jes Sorensen
2010-11-21 12:31 ` Jes Sorensen
2010-11-22 12:24 ` Kevin Wolf
2010-11-22 14:08 ` Jes Sorensen [this message]
2010-11-22 14:15 ` Kevin Wolf
2010-11-22 14:27 ` Jes Sorensen
2010-11-22 14:38 ` Kevin Wolf
2010-11-22 14:53 ` Jes Sorensen
2010-11-22 14:54 ` Anthony Liguori
2010-11-22 14:58 ` Jes Sorensen
2010-11-22 15:08 ` Anthony Liguori
2010-11-22 15:10 ` Jes Sorensen
2010-11-22 15:20 ` Anthony Liguori
2010-11-22 15:23 ` Jes Sorensen
2010-12-10 12:46 ` Markus Armbruster
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CEA794F.40506@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.