From: Kevin Wolf <kwolf@redhat.com>
To: Lin Ma <lma@suse.com>
Cc: qemu-devel@nongnu.org, mreitz@redhat.com
Subject: Re: [Qemu-devel] RFC: Make 'info snapshots' show all of snapshots with multiple devices info
Date: Mon, 23 May 2016 11:00:12 +0200 [thread overview]
Message-ID: <20160523090012.GA4951@noname.redhat.com> (raw)
In-Reply-To: <5741F282020000620006D415@prv-mh.provo.novell.com>
Am 22.05.2016 um 11:55 hat Lin Ma geschrieben:
> Currently, the output of 'info snapshots' show fully available snapshots.
>
> In my opinion there are 2 disadvantages:
> 1. It's opaque, hides some snapshot information to users. It's not convenient
> if users want to know more about all of snapshots on every block device via
> monitor.
>
> 2. It uses snapshot id to determine whether the snapshots are 'fully
> available'.
> It causes incorrect output in some scenario.
>
> For instance:
> (qemu) info block
> drive_image1 (#block113): /opt/vms/SLES12-SP1-JeOS-x86_64-GM/disk0.qcow2
> (qcow2)
> Cache mode: writeback
>
> drive_image2 (#block349): /opt/vms/SLES12-SP1-JeOS-x86_64-GM/disk1.qcow2
> (qcow2)
> Cache mode: writeback
> (qemu)
> (qemu) info snapshots
> There is no snapshot available.
> (qemu)
> (qemu) snapshot_blkdev_internal drive_image1 snap1
> (qemu)
> (qemu) info snapshots
> There is no suitable snapshot available
> (qemu)
> (qemu) savevm checkpoint-1
> (qemu)
> (qemu) info snapshots
> ID TAG VM SIZE DATE VM CLOCK
> 1 snap1 0 2016-05-22 16:57:31 00:01:30.567
> (qemu)
>
> $ qemu-img snapshot -l disk0.qcow2
> Snapshot list:
> ID TAG VM SIZE DATE VM CLOCK
> 1 snap1 0 2016-05-22 16:57:31 00:01:30.567
> 2 checkpoint-1 165M 2016-05-22 16:58:07 00:02:06.813
>
> $ qemu-img snapshot -l disk1.qcow2
> Snapshot list:
> ID TAG VM SIZE DATE VM CLOCK
> 1 checkpoint-1 0 2016-05-22 16:58:07 00:02:06.813
>
>
>
> I'd like to patch it to make the output looking like this:
> (qemu) info snapshots
>
> Snapshot list from drive_image1:
> ID TAG VM SIZE DATE VM CLOCK
> 1 snap1 0 2016-05-22 16:57:31 00:01:30.567
> 2 checkpoint-1 165M 2016-05-22 16:58:07 00:02:06.813
>
>
> Snapshot list from drive_image2:
> ID TAG VM SIZE DATE VM CLOCK
> 1 checkpoint-1 0 2016-05-22 16:58:07 00:02:06.813
I think that would clutter the output too much in the common case where
all images have the same snapshots. How about having a list with all
loadable snapshots first, and then only an additional list for images
that have snapshots that aren't present on all images?
(qemu) info snapshots
List of snapshots present on all disks:
ID TAG VM SIZE DATE VM CLOCK
-- checkpoint-1 165M 2016-05-22 16:58:07 00:02:06.813
List of partial (non-loadable) snapshots on 'drive_image1':
ID TAG VM SIZE DATE VM CLOCK
1 snap1 0 2016-05-22 16:57:31 00:01:30.567
Kevin
next prev parent reply other threads:[~2016-05-23 9:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-22 9:55 [Qemu-devel] RFC: Make 'info snapshots' show all of snapshots with multiple devices info Lin Ma
2016-05-23 9:00 ` Kevin Wolf [this message]
2016-05-25 5:49 ` [Qemu-devel] 答复: " Lin Ma
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=20160523090012.GA4951@noname.redhat.com \
--to=kwolf@redhat.com \
--cc=lma@suse.com \
--cc=mreitz@redhat.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).