Features/QED: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
= Overview = | |||
QED is an image format (like qcow2, vmdk, etc) that supports backing files and sparse images. | |||
= Status = | = Status = | ||
* '''Base QED is in qemu.git''' since [http://git.qemu.org/qemu.git/commit/?id=75411d236d93d79d8052e0116c3eeebe23e2778b 2010-12-17] and will form part of QEMU 0.14. | * '''Base QED is in qemu.git''' since [http://git.qemu.org/qemu.git/commit/?id=75411d236d93d79d8052e0116c3eeebe23e2778b 2010-12-17] and will form part of QEMU 0.14. | ||
* Zero | * Merge plan for additional features: | ||
* | ** Zero clusters [submitted]. | ||
** Periodic dirty flag flush [submitted]. | |||
** Image streaming [in preparation]. | |||
= Features = | = Features = | ||
Revision as of 10:35, 11 April 2011
Overview
QED is an image format (like qcow2, vmdk, etc) that supports backing files and sparse images.
Status
- Base QED is in qemu.git since 2010-12-17 and will form part of QEMU 0.14.
- Merge plan for additional features:
- Zero clusters [submitted].
- Periodic dirty flag flush [submitted].
- Image streaming [in preparation].
Features
- Open specification
- Fully asynchronous I/O path
- Strong data integrity due to simple design
- Backing files
- Backing files may be smaller than the QED image
- Sparse files
- Retains sparseness over non-sparse channels (e.g. HTTP)