On Thu, Dec 13, 2018 at 11:27 PM Eric Blake <ebl...@redhat.com> wrote:
> On 12/13/18 11:44 AM, Nir Soffer wrote: > > >> The things is, qemu-io was never meant to be used by other > >> applications that need to process the results, it's a tool for testing > >> and debugging. If we had meant it to be used by other programs, we would > >> have given it a machine-friendly interface. > >> > >> The machine-friendly interface to the QEMU block layer is qemu-nbd. > >> > > > > nbd is awesome, but much more complicated to use for testing. You need > to: > > > > 1. start qemu-nbd > > 2. wait until it is ready > > 3. use nbd client (we have one now), or connect the qemu-nbd to > /dev/ndbX, > > which on > > Fedora 28 leaves stale /dev/nbdX devices after disconnection > > (I reported this few month ago here). > > Is that true even when you use 'qemu-nbd -d /dev/nbdX' after you are done? > It was true when I reported this here: http://lists.nongnu.org/archive/html/qemu-block/2018-07/msg00168.html
