On Fri, Jul 9, 2021 at 1:03 AM Alex K <[email protected]> wrote:
> > > On Thu, Jul 8, 2021, 20:19 <[email protected]> wrote: > >> Hello, >> I am trying to export a bunch o VM from oVirt version 3.5 >> The problem is that there is no OVA support for exporting them. I also >> tryed to export VMs into OVA format using ovirtsdk4 which anyway won't work >> on oVirt 3.5. >> I can successfully export to a NFS partition but for each VM there are >> several qcow v2 files which I suppose to be the VM image and its snapshots. >> How to identify the correct file to represent the current VM status ? >> > When exporting you should get only one image file with the current status > of the vm. > > If you want to hack with the vm images, you can commit all the chain of > the snapshot files to your own single qcow2 copy using qemu-img commands. > >> You can easily get the disk ID of the current active snapshot (vm -> > snapshots) then you can view the full chain with: > qemu-img info --backing-chain $FILENAME > You need to know what you are doing though to avoid any data loss. > > If I delete all the snapshots, will I end up with only one valid qcow v2 >> image that I can use ? >> > Yes, you should. You can try if the snapshots are not needed. > You can alternatively ask to discard (collapse) snapshots during export in order to get a single volume on the export domain [0] There's an example for how to do that in the latest documentation of the API [1] This option seems to exist also in the API of oVirt 3.5 [2] [0] It will not necessarily be a qcow2 volume - that depends on the format of the base volume of the VM you export [1] https://github.com/oVirt/ovirt-engine-api-model/blob/4.4.31/src/main/java/services/VmService.java#L174-L189 [2] https://github.com/oVirt/ovirt-engine/blob/ovirt-engine-3.5/backend/manager/modules/restapi/jaxrs/src/main/java/org/ovirt/engine/api/restapi/resource/BackendVmResource.java#L432-L434 > _______________________________________________ >> Users mailing list -- [email protected] >> To unsubscribe send an email to [email protected] >> Privacy Statement: https://www.ovirt.org/privacy-policy.html >> oVirt Code of Conduct: >> https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: >> https://lists.ovirt.org/archives/list/[email protected]/message/FCCK7HSIVMXAH2D7F2DWLHR4J2XSSTPP/ >> > _______________________________________________ > Users mailing list -- [email protected] > To unsubscribe send an email to [email protected] > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/[email protected]/message/4J3HIIWUCVHJBMCL5TP7VR46J42MO2ED/ >
_______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/AH5ASGPMDESX2XI37R5W27EKUW6YNULO/
