slavkap commented on issue #3724: Storage-based Snapshots for KVM VMs URL: https://github.com/apache/cloudstack/pull/3724#issuecomment-582300981 Hello @andrijapanicsb, sorry for the late response! Bellow you can find answers of your questions > I see "lots" of dependency which has to be documented properly in upstream documentation (preferably) but also I would like to see it documented in the description of the global setting - "...requires qemu 1.6+ and the qemu-guest-agent installed inside a VM" We'll document the functionality, but could you please tell me what should be included? Also I will update the global setting with: >I would like to see it documented in the description of the global setting - "...requires qemu 1.6+ and the qemu-guest-agent installed inside a VM" > Do you know how well qemu-guest-agent is supported/possible on Windows guests - lot's of people will be running Windows VMs as well - covering just Linux workloads would be suboptimal. For Windows freeze/thaw of guest agent is included in versions from 2013 > You are mentioning QCOW format and behaviour about it. Ceph uses RAW format from Qemu/Libvirt perspective, but possibly is marked as QCOW2 in DB (I recall some hassle around DB format in past) - can you please elaborate about this - how does it work with Ceph vs other "real" QCOW2 formats? Store Ceph is marked in DB as RAW format, but this doesn't affect snapshot and revert of Ceph's volumes, because we are using its implementation for this. For each primary storage we are using appropriate plugin with take/revert snapshot implementation. Did you guys test this on the busy VMs (IO and CPU heavy workloads)? We've completed our tests including on busy VMs with different primary storages. They've been successfully reverted and it works as expected. > moving to 4.15, I'm afraid we won't be able to test in time. Unfortunately we'll need time to implement qemu-agent and qemu-monitor commands functionality in libvirt java api, and don't know when it will be accepted.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
