From: Francesco Latino <francesco.latino@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] qemu-io capabilities exposed through APIs
Date: Thu, 21 May 2009 18:41:59 +0200 [thread overview]
Message-ID: <3f0d98a60905210941r1be8b00ct7124500adad2b9da@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 603 bytes --]
hello,
I am writing a C code that discovers and browses virtual images on a KVM
server.
I can discover virtual images with libvirt API.
I can correctly read (bytes - by - bytes ) virtual images with qemu-io -c
"read -v 0 512" command line.
But I prefer to perform this step by calling a library and not the qemu-io
command line.
Are the qemu-io capabilites exposed through a shared object I can
dynamically load at runtime ?
I mean I need something like the libvirt virDomainBlockPeek.
Ex:
sectors = qemu_read_sector_from_image () -> which works just like qemu-io -c
"read -v "
Thanks,
Francesco
[-- Attachment #2: Type: text/html, Size: 691 bytes --]
reply other threads:[~2009-05-21 16:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3f0d98a60905210941r1be8b00ct7124500adad2b9da@mail.gmail.com \
--to=francesco.latino@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).