mirror of
https://github.com/retspen/webvirtcloud.git
synced 2026-04-25 23:45:56 +03:00
[GH-ISSUE #350] Support for running snapshots #225
Labels
No labels
bug
enhancement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/webvirtcloud#225
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @faburem on GitHub (Aug 3, 2020).
Original GitHub issue: https://github.com/retspen/webvirtcloud/issues/350
Hi,
first of all thanks for this great application (and releasing it open source!), it is better than the majority of proprietary VM management solutions I've worked with before. We have started to use it in our daily work routine and it covers 95% of our use cases. The only thing currently missing is support for taking snapshots of instances in running state, which is currently prevented by the web-interface:
Is there a technical reason / limitation for this? Because virt-manager supports this, I am curious if we can also get this working in webvirtcloud.
Thanks for your feedback,
Fabian
@catborise commented on GitHub (Aug 3, 2020):
thanks...
yes we can take snapshots although instance is running. but taking snapshots offline more healthy and fast.
if the ram size is big, taking live snapshot can be run out of time. to prevent that we disable it.
@catborise commented on GitHub (Aug 3, 2020):
i am waiting external snapshot support. soon libvirt will support it. external snapshots are very cool and useful, fast/instant.
@faburem commented on GitHub (Aug 3, 2020):
so are you basically saying if I fork the repo and enable the snapshot feature in the UI it should work? Could be worth to make that configureable in a setting - are you interested in a PR if I work on this?
@catborise commented on GitHub (Aug 3, 2020):
yes you can enable it. it is a simple if else statement.
yes we can make it optional... but to prevent getting “running out of time” error, there should be done something with nginx/ gunicorn , etc...