Re: [Qemu-discuss] qemu and -snapshot - Solved

[Frans de Boer]

Sorry, I have made a mistake in parameter passing which causes this 
behavior. Hope that nobody have yet spent too much time to tackle this.

Still, there is an ambiguity in the manual text: In explaining the 
arguments to the file directive, snapshot=snapshot is mentioned. Later 
to be explained as on of off - snapshot=<on|off> would be more clear - 
and that it works in conjunction with the -snapshot command line 
directive. I read this that when file=....,snapshot=on and -snapshot is 
used, the snapshot functionality is activated. The truth is that 
snapshot=on activates this also.

Frans.

----------------------------------
I do not understand: with the -snapshot option it is reading the image
correctly, but without it it is corrupted?

The image worked for years, once I started using the -snapshot option it
can no longer be used without it.

Frans.


On 06/17/2014 04:17 PM, Dale R. Morley wrote:
> > From: Frans de Boer <address@hidden>
> >
> > After having run qemu with the -snapshot option, I tried to run another
> > time without the -snapshot option, only to see that qemu reported that
> > the device is empty.
> >
> > Each time running again with that option, brings back a working system,
> > but never again without that option.
> >
> > I like to know what went wrong and how I can use qemu again without that
> > option.
> >
> > I am using qemu-2.0 and am using an image file.
>
> Most likely the image file is incorrect in some way.
>
> Try attaching it to a loopback device (losetup -P -f --show <file>)
> and examining the image file to see if it's a correctly formatted disk
> image.
>
> Most likely, if it was damaged, it was not damaged by Qemu but by some
> other action.
>
> Dale