Arbadacarba Posted October 29, 2022 Share Posted October 29, 2022 +1 Absolutely Quote Link to comment
scorcho99 Posted November 7, 2022 Share Posted November 7, 2022 This would be a nice feature but I just link up to unraid with virt-manager (SpaceInvaderOne's tutorial) and manage snapshots with that. You could also do it commandline if you want to do it the hard way. Quote Link to comment
Evolze Posted November 23, 2022 Share Posted November 23, 2022 +1 to this feature request. Specifically, the ability to create VM snapshots and managing VM snapshots from the Unraid GUI. I recently switched over from a QNAP NAS, and having the ability to snapshot a VM either hot/on or cold/off has been an absolute lifesaver! From my current experience with Linux guests in Unraid, there is a bit more flexibility here within the guest OS itself, but being able to manage it from the Unraid GUI would save quite a bit of time, that's for sure! Quote Link to comment
DrMcNasty Posted November 27, 2022 Share Posted November 27, 2022 As I am just converting my setup to Unraid now, this is something that I will drastically miss from running under Hyper-V. I would pay extra to have this feature. Quote Link to comment
HackHome Posted November 28, 2022 Share Posted November 28, 2022 any news on that one? Quote Link to comment
thany Posted December 21, 2022 Share Posted December 21, 2022 (edited) Yes! And *online* snapshots would be a must. Snapshot should then also include persisted vRAM state and probably some devices guff. A useful feature would also be to set up a snapshot to always start a VM from, and discard any changes made afterwards. The use-case for this is something like an internet cafe, a demo OS, or a place to tinker with stuff that is otherwise impossible to undo. A discardable OS, where any damage a user may have done to a system can just go *poof* and rolls back to a known working state, would be extremely useful in a plethora of contexts. I'm thinking schools, internet cafe as mentioned, some kind of public kiosk, or even something your kid will be unable to break. It would also need a function to merge snapshots, and to "delete" snapshots (which means to merge & persist them unto the regular img file). Edited December 21, 2022 by thany Quote Link to comment
cstrassmair Posted December 25, 2022 Share Posted December 25, 2022 +1 from me for any form of snapshots Quote Link to comment
Tucubanito07 Posted December 28, 2022 Share Posted December 28, 2022 +1 Absolutely. Quote Link to comment
fwiler Posted December 29, 2022 Share Posted December 29, 2022 Just adding my support for this request. Very valuable feature. Quote Link to comment
SimonF Posted December 31, 2022 Share Posted December 31, 2022 (edited) There are two types of snapshots available in QEMU internal and external. Internal - Requires QCOW2 images, Doesn't support OVMF, but have seen a work around to change to rom, snap but you have to do a manual revert. External - Supports only diskonly, no revert or delete options at present, manual revert needs VM to be stopped. Which VM types are people looking to snapshot? Does anyone know if proxmox supports OVMF? I have asked the libvirt team if any ideas on timeline for full support for external snaps/ Testing so far. VM Seabios 2 x QCOW2 Disk files. [email protected]:~# virsh domfsinfo DebianSB Mountpoint Name Type Target -------------------------------------------- / vda1 ext4 hdc /media/snapb/disk2 vdb ext4 hdd [email protected]:~# virsh snapshot-create DebianSB Domain snapshot 1672498342 created [email protected]:~# virsh snapshot-list DebianSB Name Creation Time State --------------------------------------------------- 1672498342 2022-12-31 14:52:22 +0000 running [email protected]:~# virsh snapshot-revert DebianSB error: --snapshotname or --current is required [email protected]:~# virsh snapshot-revert DebianSB --current [email protected]:~# [email protected]:~# virsh snapshot-info DebainSB error: failed to get domain 'DebainSB' [email protected]:~# virsh snapshot-info DebianSB error: --snapshotname or --current is required [email protected]:~# virsh snapshot-list DebianSB Name Creation Time State --------------------------------------------------- 1672498342 2022-12-31 14:52:22 +0000 running [email protected]:~# virsh snapshot-revert DebianSB 1672498342 [email protected]:~# virsh snapshot-list DebianSB Name Creation Time State --------------------------------------------------- 1672498342 2022-12-31 14:52:22 +0000 running [email protected]:~# virsh snapshot-list DebianSB Name Creation Time State --------------------------------------------------- 1672498342 2022-12-31 14:52:22 +0000 running 1672498947 2022-12-31 15:02:27 +0000 running [email protected]:~# virsh snapshot-revert DebianSB 1672498947 [email protected]:~# virsh destroy DebianSB Domain 'DebianSB' destroyed [email protected]:~# virsh snapshot-create DebianSB Domain snapshot 1672500774 created [email protected]:~# virsh snapshot-list DebianSB Name Creation Time State --------------------------------------------------- 1672498342 2022-12-31 14:52:22 +0000 running 1672498947 2022-12-31 15:02:27 +0000 running 1672500774 2022-12-31 15:32:54 +0000 shutoff VM OVMF 2 x QCOW2 [email protected]:~# virsh snapshot-create DebianSO error: Operation not supported: internal snapshots of a VM with pflash based firmware are not supported [email protected]:~# # change pflash to rom [email protected]:~# virsh snapshot-create DebianSO Domain snapshot 1672502423 created [email protected]:~# virsh snapshot-list DebianSO Name Creation Time State --------------------------------------------------- 1672502423 2022-12-31 16:00:23 +0000 shutoff Edited December 31, 2022 by SimonF 1 Quote Link to comment
machineglow Posted February 1 Share Posted February 1 +1. would love UI supported snapshots Quote Link to comment
Tjlejeune Posted February 5 Share Posted February 5 +1. This should have been a feature a long time ago Quote Link to comment
DrKamp Posted February 11 Share Posted February 11 Hello everyone. I would also love this feature. That is just my single opinion, but my personnal usecase is to be able to save a working configuration before doing any kind of changes that I'm not so sure about while knowing I can always go back to a previous known working point. ie: more like a restauration point.Therefore, It's not a problem for me if I need to switch the VM down before taking the snapshot. As I'm writing this, I'm not sure it's really a "Snapshot" per say where all states (including RAM) are captured. (I don't need RAM state to be captured...) More like a "disk backup" at a given point in time. Maybe those 2 use cases are different and one can be implemented faster than the other. Especially if it covers the need of the majority of people. (Not saying we should forget users that need more elaborate functions (hot snaphshot with RAM, etc...)) That is my own 2 cents about a feature that would endeed be great Have a good day. Quote Link to comment
sjoerd Posted February 16 Share Posted February 16 (edited) Been trying today with virsh and qemu-img to try it from the cli - Using seabios (does it matter) and qcow2 but if I set current snapshot with virsh for that vm6 and do a dnf update or something else big the data still gets written to the clean base image - same goes for qemu-img.. added a image, no error but the snapshot file is not created after "[email protected]:/mnt/user/domains/ol6# qemu-img snapshot -c vdisk1_202302161020.qcow2 vdisk1.qcow2". When I check if the snapshot is created: [email protected]:/mnt/user/domains/ol6# qemu-img info --backing-chain vdisk1.qcow2 image: vdisk1.qcow2 file format: qcow2 virtual size: 12 GiB (12884901888 bytes) disk size: 4.3 GiB cluster_size: 65536 Snapshot list: ID TAG VM SIZE DATE VM CLOCK ICOUNT 1 1676537842 0 B 2023-02-16 09:57:22 00:00:00.000 0 3 vdisk1_202302161020.qcow2 0 B 2023-02-16 10:22:03 00:00:00.000 0 Format specific information: compat: 1.1 compression type: zlib lazy refcounts: false refcount bits: 16 corrupt: false extended l2: false Confused - I tried the virt manager docker but I couldn't find an option to make a snapshot in the first place. I'm not sure how virsh or qemu-img work together with unraid, but I'm using Xen at work which just snapshots an entire vm - no matter how many disk images there are attached to it.. Same goes for virtual box - which I'm using at home (on my workstation). Native support for managing snapshots is most welcome - unraid is quite complete (and when not, you can complete is yourself with plugins), but it kinda bothers me not having this feature - that's the reason why I (almost) moved to proxmox having unraid just as dfs inside it, but that would be counterproductive. I've been thinking about btrfs too but I deliberately did not format the vm cache nvme as btrfs - don't want to go that way: qemu it self can manage snapshots.. Edited February 17 by sjoerd typos, added info Quote Link to comment
kfk Posted March 5 Share Posted March 5 +1000 How come this feature does not exist in Unraid 2023? Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.