qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Halsey Pian <halsey.pian@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Help: Convert HDD to QCOW2 img
Date: Mon, 1 Dec 2014 09:52:24 +0000	[thread overview]
Message-ID: <CAJSP0QXB9ifVi3LGNn7ekuB4tdrLfZ6hHWdu5EwEYuiST240pg@mail.gmail.com> (raw)
In-Reply-To: <00c201d00d4a$e5ea1a50$b1be4ef0$@gmail.com>

On Mon, Dec 1, 2014 at 9:40 AM, Halsey Pian <halsey.pian@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

  parent reply	other threads:[~2014-12-01  9:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-27 10:15 [Qemu-devel] Help: Convert HDD to QCOW2 img Halsey Pian
2014-11-27 16:31 ` Stefan Hajnoczi
     [not found]   ` <00c201d00d4a$e5ea1a50$b1be4ef0$@gmail.com>
2014-12-01  9:52     ` Stefan Hajnoczi [this message]
2014-12-01 14:25       ` Halsey

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=CAJSP0QXB9ifVi3LGNn7ekuB4tdrLfZ6hHWdu5EwEYuiST240pg@mail.gmail.com \
    --to=stefanha@gmail.com \
    --cc=halsey.pian@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).