<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Mar 17, 2016 at 7:59 AM, Arik Hadas <span dir="ltr"><<a href="mailto:ahadas@redhat.com" target="_blank">ahadas@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Hi Matt,<br>
<br>
When creating a snapshot with memory, 2 additional images are created:<br>
1. for the VM configuration/metadata<br>
2. for the memory dump<br>
<br>
In oVirt 3.6 and below you'll notice a field called memory_vol_handle in the snapshots table that points to these images. It is of the follow format:<br>
<storage_domain_id>,<storage_pool_id>,<memory_dump_disk_id>,<memory_dump_volume_id>,<memory_conf_disk_id>,<memory_conf_volume_id><br>
<br>
In master branch, you'll find two fields in the snapshots table called memory_dump_disk_id and memory_metadata_disk_id that contain the disk IDs.<br>
We plan to remove the memory_vol_handle field from the snapshots table soon, so please do not rely on it.<br>
<br>
Regards,<br>
Arik</blockquote><div><br></div>Thanks Arik! Has any of this been added to the Python SDK, by chance?<div><br></div><div> Regards, </div><div><br></div><div> --Matt</div></div></div></div>