diff options
author | Jeff Cody <jcody@redhat.com> | 2013-10-30 10:44:45 -0400 |
---|---|---|
committer | Stefan Hajnoczi <stefanha@redhat.com> | 2013-11-07 13:58:58 +0100 |
commit | 0a43a1b5d7c33208120eeb2d98ebb9ab15dc2c87 (patch) | |
tree | 9167c27dbc1f182482aa3fd645962aefa3f0b3c9 /savevm.c | |
parent | c46415afc2c99ea052f52f9d68ed9a78799f2c10 (diff) | |
download | hqemu-0a43a1b5d7c33208120eeb2d98ebb9ab15dc2c87.zip hqemu-0a43a1b5d7c33208120eeb2d98ebb9ab15dc2c87.tar.gz |
block: vhdx - log parsing, replay, and flush support
This adds support for VHDX v0 logs, as specified in Microsoft's
VHDX Specification Format v1.00:
https://www.microsoft.com/en-us/download/details.aspx?id=34750
The following support is added:
* Log parsing, and validation - validate that an existing log
is correct.
* Log search - search through an existing log, to find any valid
sequence of entries.
* Log replay and flush - replay an existing log, and flush/clear
the log when complete.
The VHDX log is a circular buffer, with elements (sectors) of 4KB.
A log entry is a variably-length number of sectors, that is
comprised of a header and 'descriptors', that describe each sector.
A log may contain multiple entries, know as a log sequence. In a log
sequence, each log entry immediately follows the previous entry, with an
incrementing sequence number. There can only ever be one active and
valid sequence in the log.
Each log entry must match the file log GUID in order to be valid (along
with other criteria). Once we have flushed all valid log entries, we
marked the file log GUID to be zero, which indicates a buffer with no
valid entries.
Signed-off-by: Jeff Cody <jcody@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Diffstat (limited to 'savevm.c')
0 files changed, 0 insertions, 0 deletions