On 03/28/2017 01:56 PM, Patrick O'Callaghan wrote:
On Tue, 2017-03-28 at 12:38 -0500, Robert Nichols wrote:
What you have is not a snapshot. A snapshot is created with "qemu-img snapshot -c <snapshot-name> <imagename>", and that is _not_ a separate file. That "<snapshot-name>" is not a file name but just a tag to identify one of possibly several snapshots within that "<imagename>" file.
I did create it with the above line. Clearly I didn't understand where
it was, or perhaps I inadvertently deleted it.
That output from "qemu-img info ..." says otherwise. That /var/lib/libvirt/images/Windows10.qcow2 file was created with "qemu-img create -b /home/poc/Win10/win10.qcow2 /var/lib/libvirt/images/Windows10.qcow2". There is no other way that "backing file: /home/poc/Win10/win10.qcow2" could appear in the output.
I can only say I have no recollection of typing that, and that I did
want to create a snapshot as a test. But it was a few days ago so I may
be wrong.
In order for the .../Windows10.qcow2 file to be valid, that backing file _must_ exist and be unchanged since that new file was created.
OK, though I can't guarantee it hasn't changed since I did run the VM
afterwards.
Did you really run the VM from the file in /home/poc/Win10/ ? It would be unusual to run a VM from a file in your home directory and not from one in the /var/lib/libvirt/images/ directory. Check the modification times on the files. If /home/poc/Win10/win10.qcow2 really has changed, then the /var/lib/libvirt/images/Windows10.qcow2 file is pretty much worthless.
If you want to test that backing file, create _another_ file using /home/poc/Win10/win10.qcow2 as a backing file and see if that new file can run or be made to run. You can do that safely and know that the backing file is not being affected.
--
Bob Nichols "NOSPAM" is really part of my email address.
Do NOT delete it.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
