@@ -23,30 +23,29 @@ Furthermore, this file is based on the following code published by Intel under A
23
23
/*
24
24
Package imagefile contains code to create a file with the following content:
25
25
26
- .-----------.----------.---------------.
27
- | 0 - 512 B | 4 - 8 Kb | 2M - ... |
28
- |-----------+----------+---------------+
29
- | MBR #1 | DAX | FS |
30
- '-----------'----------'---------------'
31
- | | ^
32
- | '-data-'
33
- | |
34
- '--fs-partition--'
35
-
36
- ^ ^
37
- daxHeaderOffset |
38
- HeaderSize
39
-
26
+ .-----------.----------.---------------.
27
+ | 0 - 512 B | 4 - 8 Kb | 2M - ... |
28
+ |-----------+----------+---------------+
29
+ | MBR #1 | DAX | FS |
30
+ '-----------'----------'---------------'
31
+ | | ^
32
+ | '-data-'
33
+ | |
34
+ '--fs-partition--'
35
+
36
+ ^ ^
37
+ daxHeaderOffset |
38
+ HeaderSize
40
39
41
40
MBR: Master boot record.
42
41
DAX: Metadata required by the NVDIMM driver to enable DAX in the guest (struct nd_pfn_sb).
43
42
FS: partition that contains a filesystem.
44
43
45
44
The MBR is useful for working with the image file:
46
- - the `file` utility uses it to determine what the file contains
47
- - when binding the entire file to /dev/loop0, /dev/loop0p1 will be
48
- the file system (beware that partprobe /dev/loop0 might be needed);
49
- alternatively one could bind the file system directly by specifying an offset
45
+ - the `file` utility uses it to determine what the file contains
46
+ - when binding the entire file to /dev/loop0, /dev/loop0p1 will be
47
+ the file system (beware that partprobe /dev/loop0 might be needed);
48
+ alternatively one could bind the file system directly by specifying an offset
50
49
51
50
When such a file is created on a dax-capable filesystem, then it can
52
51
be used as backing store for a [QEMU nvdimm
0 commit comments