On 06/11/2010 07:55 AM, Luiz Capitulino wrote:
On Thu, 10 Jun 2010 09:27:34 -0500
Anthony Liguori<anthony@xxxxxxxxxxxxx> wrote:
On 06/10/2010 08:08 AM, Kevin Wolf wrote:
Am 10.06.2010 14:53, schrieb Anthony Liguori:
On 06/10/2010 04:43 AM, Kevin Wolf wrote:
Huh, why this? Seems I still haven't understood all of qcow2 then... I
always thought that there's just a specific offset where VM state
starts, but no explicit end.
A live snapshot can last for a very long time. What happens if you need
to allocate a new block for disk I/O while saving a snapshot?
You allocate it, I guess?
Note that VM state must be virtually contiguous, but not necessarily
physically (virtually = on the virtual hard disk as seen by the guest;
physically = in the image file). It's just not seen by the guest because
it's saved at a high offset that is after the end of the real disk
content, but otherwise it should behave the same as guest data.
I guess you could just start writing and then once your finished, you
could update the snapshot information. So yeah, I think your right that
it's doable with the current format.
No more issues on having them in QMP for 0.13 then?
I still think it's wrong to expose a broken command with no way for a
user to detect whether it works or not. The fact that no other commands
can run during it and the command may run for many minutes is still part
of the protocol ABI IMHO.
Regards,
Anthony Liguori
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
