Christoph Hellwig h...@lst.de writes:
Looks good,
Reviewed-by: Christoph Hellwig h...@lst.de
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.
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:
$
Kevin Wolf kw...@redhat.com 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
Looks good,
Reviewed-by: Christoph Hellwig h...@lst.de
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.
