The legacy 'file' storage driver just doesn't implement the required
functionality for 'qvm-volume revert' - one of the many reasons it
will be deprecated:
https://github.com/QubesOS/qubes-issues/issues/6399
Awesome! Thank yu for that hint. When/how will it be changed ?? That
seems quite tr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Stickstoff:
> [dom0] qvm-volume revert vmname:private old
> > Got empty response from qubesd. See journalctl in dom0 for details.
>
> Journal says:
> > unhandled exception while calling src=b' dom0' meth=b' \
> > admin.vm.volume.Revert' dest=b'vmnam
Thank you David and haaber for your help, it is much appreciated!
On 4/18/21 11:23 AM, David Hobach wrote:
> Use `qvm-volume revert` to go back to previous snapshots for a VM.
Oh, I saw that page [1] at some point, but didn't try it before. Thanks
for the reminder.
[dom0] qvm-volume info vmname
I lost a somewhat important file from a software crash in an appvm.
However, '-cow.img' files contain no filesystem, but "binary patch"
data, thus can't be mounted or read directly or without their
corresponding'.img' files.
These are real disc-image files! There is a filesystem, but it is no
On 4/17/21 11:03 PM, Stickstoff wrote:
Hello everyone,
I lost a somewhat important file from a software crash in an appvm.
Within the VM, I couldn't find a way to recover it. I copied the appvm
filesystem containers ('private.img', 'private-cow.img',
'private-cow.img.old').
As I understand it,
Hello everyone,
I lost a somewhat important file from a software crash in an appvm.
Within the VM, I couldn't find a way to recover it. I copied the appvm
filesystem containers ('private.img', 'private-cow.img',
'private-cow.img.old').
As I understand it, 'private-cow.img' contains the old version
