提交 1cdaebf2 编写于 作者: M Martin Kletzander

Properly detect VMDK with internal version 2

Initially proposed as [1], but then changed to comment fix only.  VMDK
can have internal version set to 2 when there are few features added
which do not affect us.  Thanks to Jan's commit a1ee8e18 this can be
easily fixed by adding it to list of supported versions.

[1] http://www.redhat.com/archives/libvir-list/2013-June/msg00419.html

Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=836676
上级 1e503ee5
...@@ -213,7 +213,7 @@ static struct FileTypeInfo const fileTypeInfo[] = { ...@@ -213,7 +213,7 @@ static struct FileTypeInfo const fileTypeInfo[] = {
}, },
[VIR_STORAGE_FILE_VMDK] = { [VIR_STORAGE_FILE_VMDK] = {
0, "KDMV", NULL, 0, "KDMV", NULL,
LV_LITTLE_ENDIAN, 4, {1}, LV_LITTLE_ENDIAN, 4, {1, 2},
4+4+4, 8, 512, -1, vmdk4GetBackingStore, NULL 4+4+4, 8, 512, -1, vmdk4GetBackingStore, NULL
}, },
[VIR_STORAGE_FILE_VPC] = { [VIR_STORAGE_FILE_VPC] = {
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册