|
From: | Jes Sorensen |
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 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.12) Gecko/20101103 Fedora/1.0-0.33.b2pre.fc14 Lightning/1.0b3pre Thunderbird/3.1.6 |
On 11/22/10 13:24, Kevin Wolf wrote: > Am 19.11.2010 17:30, schrieb address@hidden: >> From: Jes Sorensen <address@hidden> >> >> Signed-off-by: Jes Sorensen <address@hidden> > > 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
[Prev in Thread] | Current Thread | [Next in Thread] |