From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org, Luiz Capitulino <lcapitulino@redhat.com>,
armbru@redhat.com, stefanha@linux.vnet.ibm.com
Subject: [Qemu-devel] Re: [PATCH 2/3] Introduce do_snapshot_blkdev() and monitor command to handle it.
Date: Wed, 15 Dec 2010 17:57:25 +0100 [thread overview]
Message-ID: <4D08F375.3060907@redhat.com> (raw)
In-Reply-To: <4D08F305.1040503@redhat.com>
On 12/15/10 17:55, Kevin Wolf wrote:
>> +int do_snapshot_blkdev(Monitor *mon, const QDict *qdict, QObject **ret_data)
>> +{
>> + const char *device = qdict_get_str(qdict, "device");
>> + const char *filename = qdict_get_try_str(qdict, "snapshot_file");
>> + const char *format = qdict_get_try_str(qdict, "format");
>> + const char format_qcow2[] = "qcow2";
>> + BlockDriverState *bs;
>> + BlockDriver *drv, *proto_drv;
>> + int ret = 0;
>> + int flags;
>> +
>> + bs = bdrv_find(device);
>> + if (!bs) {
>> + qerror_report(QERR_DEVICE_NOT_FOUND, device);
>> + ret = -1;
>> + goto out;
>> + }
>> +
>> + if (!format) {
>> + format = format_qcow2;
>> + }
>> +
>> + drv = bdrv_find_format(format);
>> + if (!drv) {
>> + qerror_report(QERR_INVALID_BLOCK_FORMAT, format);
>> + ret = -1;
>> + goto out;
>> + }
>> +
>> + proto_drv = bdrv_find_protocol(filename);
>> + if (!proto_drv) {
>> + qerror_report(QERR_INVALID_BLOCK_FORMAT, format);
>> + ret = -1;
>> + goto out;
>> + }
>> +
>> + ret = bdrv_img_create(filename, format, bs->filename,
>> + bs->drv->format_name, NULL, -1, bs->open_flags);
>> + if (ret) {
>> + goto out;
>> + }
>> +
>> + qemu_aio_flush();
>> + bdrv_flush(bs);
>> +
>> + flags = bs->open_flags;
>> + bdrv_close(bs);
>> + ret = bdrv_open(bs, filename, flags, drv);
>> + /*
>> + * If reopening the image file we just created fails, we really
>> + * are in trouble :(
>> + */
>> + assert(ret == 0);
>> +out:
>> + if (ret) {
>> + ret = 1;
>
> I seem to remember that errors are always -1 for monitor commands.
I mapped it after something else, but admitted I cannot remember where -
can someone clarify?
Cheers,
Jes
next prev parent reply other threads:[~2010-12-15 16:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-13 7:32 [Qemu-devel] [PATCH 0/3] Re-factor img_create() and add live snapshots Jes.Sorensen
2010-12-13 7:32 ` [Qemu-devel] [PATCH 1/3] qemu-img.c: Re-factor img_create() Jes.Sorensen
2010-12-13 7:32 ` [Qemu-devel] [PATCH 2/3] Introduce do_snapshot_blkdev() and monitor command to handle it Jes.Sorensen
2010-12-15 16:55 ` [Qemu-devel] " Kevin Wolf
2010-12-15 16:57 ` Jes Sorensen [this message]
2010-12-15 17:26 ` Luiz Capitulino
2010-12-13 7:32 ` [Qemu-devel] [PATCH 3/3] Prevent creating an image with the same filename as backing file Jes.Sorensen
2010-12-15 16:52 ` [Qemu-devel] Re: [PATCH 0/3] Re-factor img_create() and add live snapshots Kevin Wolf
2010-12-15 16:57 ` Jes Sorensen
-- strict thread matches above, loose matches on Subject: below --
2010-12-16 11:04 [Qemu-devel] [PATCH v2 " Jes.Sorensen
2010-12-16 11:04 ` [Qemu-devel] [PATCH 2/3] Introduce do_snapshot_blkdev() and monitor command to handle it Jes.Sorensen
2010-12-16 11:45 ` [Qemu-devel] " Kevin Wolf
2010-12-16 12:14 ` Jes Sorensen
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=4D08F375.3060907@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.com \
/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).