Kevin Wolf writes:
> Am 25.06.2010 18:53, schrieb Markus Armbruster:
>> savevm.c keeps a pointer to the snapshot block device. If you manage
>> to get that device deleted, the pointer dangles, and the next snapshot
>> operation will crash & burn. Unplugging a guest device that uses it
>> does t
Am 25.06.2010 18:53, schrieb Markus Armbruster:
> savevm.c keeps a pointer to the snapshot block device. If you manage
> to get that device deleted, the pointer dangles, and the next snapshot
> operation will crash & burn. Unplugging a guest device that uses it
> does the trick:
>
> $ MALLOC
Christoph Hellwig writes:
> Looks good,
>
> Reviewed-by: Christoph Hellwig
>
> Of course specifying an explicit medium for snapshot, be that the
> snapshot section of a qcow2 image or just a separate flat file and
> managing that one explicitly would be even better.
Indeed.
Looks good,
Reviewed-by: Christoph Hellwig
Of course specifying an explicit medium for snapshot, be that the
snapshot section of a qcow2 image or just a separate flat file and
managing that one explicitly would be even better.
