[GitHub] [cloudstack] DaanHoogland commented on issue #3584: Unexpected Error when creating VM Snapshot on Stopped VM
DaanHoogland commented on issue #3584: URL: https://github.com/apache/cloudstack/issues/3584#issuecomment-738624570 I don't agree (obviously) with @weizhouapache (not sure if @ustcweizhou is still prefered in use?) but lets give researching it a place in next cycle. In my personal opinion a stopped VM is nothing more than a set of volumes, and a machine difinition, there is no state to snapshot, but saving the machine definition might make sense. At least the failure should be graceful with a sensible error or warning message. 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: us...@infra.apache.org
[GitHub] [cloudstack] DaanHoogland commented on issue #3584: Unexpected Error when creating VM Snapshot on Stopped VM
DaanHoogland commented on issue #3584: Unexpected Error when creating VM Snapshot on Stopped VM URL: https://github.com/apache/cloudstack/issues/3584#issuecomment-530362480 @mihle @luhaijiao What is the use of a VM snapshot when a VM is stopped? The only tangible thing is the disk image as a stopped VM does not have memory state. Isn't it completely appropriate to be not be able to take a VM snapshot (irrespective of the unclear error output)? 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: us...@infra.apache.org With regards, Apache Git Services
