Hi Stefan, Thanks for so much info you provided.
Okay, I would keep qemu-devel mailing list in the loop, no problem. Currently, I have finished the coding of the wrapper, now testing the bdrv_read/write qcow2 img. I would look into these libraries and incorporate them based on the concept of interface design. Thanks. Halsey Sent from my iPhone > On 2014年12月1日, at 17:52, Stefan Hajnoczi <stefa...@gmail.com> wrote: > > On Mon, Dec 1, 2014 at 9:40 AM, Halsey Pian <halsey.p...@gmail.com> wrote: > > Please keep qemu-devel@nongnu.org CCed so the discussion stays on the > mailing list. I have added it back. > >> Hi Stefan, not know if there is similar module, currently I have not seen >> it. If yes, please forgive me. And for the program if it >> is unique, there should be some policies for involving QEMU team, right? >> Thanks. > > QEMU does not have something directly equivalent to VMware's SDK for storage. > > But there is a very powerful API called libguestfs. Maybe it does > what you want: > http://libguestfs.org/ > > libvirt has APIs for snapshotting and managing storage: > http://libvirt.org/html/libvirt-libvirt-storage.html > > QEMU's qemu-img supports JSON output to make it easy to parse. > qemu-nbd can be used for read-write access. > > There was an attempt to create something called libqblock but the work > was never completed. I guess your approach is similar: > https://lists.gnu.org/archive/html/qemu-devel/2013-02/msg02356.html > > Stefan
