From: Kevin Wolf <kwolf@redhat.com>
To: Chris Lalancette <clalance@redhat.com>
Cc: lcapitulino@redhat.com,
Miguel Di Ciurcio Filho <miguel.filho@gmail.com>,
armbru@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH] monitor: Really show snapshot information about all devices
Date: Wed, 16 Jun 2010 17:32:58 +0200 [thread overview]
Message-ID: <4C18EEAA.3060106@redhat.com> (raw)
In-Reply-To: <20100616152249.GB2835@localhost.localdomain>
Am 16.06.2010 17:22, schrieb Chris Lalancette:
> On 06/16/10 - 03:15:11PM, Kevin Wolf wrote:
>> Am 16.06.2010 14:59, schrieb Miguel Di Ciurcio Filho:
>>> On Wed, Jun 16, 2010 at 9:40 AM, Kevin Wolf <kwolf@redhat.com> wrote:
>>>>
>>>> If the human monitor was exactly what its name says, I'd happily apply
>>>> this one (though I think it should be made clear from which image the VM
>>>> state would be loaded). However, it isn't and I'm not sure if this
>>>> wouldn't break libvirt. Dan, can you help?
>>>>
>>>
>>> I didn't mention in the commit, but I've looked at libvirt's source
>>> and it is not using 'info snapshots' AFAIK.
>>
>> Anthony, Dan, are you okay with the change then?
>
> Right, exactly as Miguel said, libvirt doesn't use "info snapshots" at all
> at the moment. One of the reasons we don't use it at present is precisely
> because it doesn't give us information about all disks in-use.
>
> The other reason that we can't use "info snapshots" is that we need to know
> parent information about snapshots. That is, if you take a sequence of
> snapshots:
>
> A -> B -> C
>
> And then you delete B, the disk changes from B will be merged automatically
> into C to keep C a valid snapshot. However, there is currently no way to
> discover this parent/child relationship, so we can't use "info snapshots"
> for that reason as well.
Well, there is no parent/child relation in qcow2, so exposing this is
going to be really hard. We also don't really need it anywhere in qemu.
What would libvirt use this information for?
Kevin
next prev parent reply other threads:[~2010-06-16 15:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-16 1:53 [Qemu-devel] [PATCH] monitor: Really show snapshot information about all devices Miguel Di Ciurcio Filho
2010-06-16 12:40 ` [Qemu-devel] " Kevin Wolf
2010-06-16 12:59 ` Miguel Di Ciurcio Filho
2010-06-16 13:15 ` Kevin Wolf
[not found] ` <20100616152249.GB2835@localhost.localdomain>
2010-06-16 15:32 ` Kevin Wolf [this message]
[not found] ` <20100616155710.GC2835@localhost.localdomain>
2010-06-17 7:48 ` Kevin Wolf
2010-06-16 22:12 ` Miguel Di Ciurcio Filho
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=4C18EEAA.3060106@redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=clalance@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=miguel.filho@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).