Am 21.03.2016 um 15:11 hat Daniel P. Berrange geschrieben: > This series is just the block layer parts needed to add > a LUKS driver to QEMU. It was previously posted as part > of the larger series > > v1: https://lists.gnu.org/archive/html/qemu-devel/2015-11/msg04748.html > v2: https://lists.gnu.org/archive/html/qemu-block/2016-01/msg00534.html > v3: https://lists.gnu.org/archive/html/qemu-devel/2016-02/msg03176.html > v4: https://lists.gnu.org/archive/html/qemu-devel/2016-02/msg06552.html > v5: https://lists.gnu.org/archive/html/qemu-devel/2016-03/msg04397.html > > The crypto subsystem pieces that this series depends on have now > all been merged. > > In this posting I am only proposing merge of the generic LUKS > driver. This can be added as a layer above any of the existing > drivers for accessing LUKS formatted volumes. > > When creating new volumes, however, only the file backend can > be used, since the block driver API doesn't allow for arbitrary > stacking of protocols when creating images. > > The integration with the qcow2 driver to replace the existing > built-in AES-CBC code is dropped from this series, postponed > until the 2.7 development cycle. > > There is a QEMU I/O test 149 that exercises the LUKS driver > and checks for compatibility with the dm-crypt/cryptsetup > impl.
Reviewed-by: Kevin Wolf <kw...@redhat.com> I can't seem to test this, however, as long as git master doesn't compile on RHEL 7 without --disable-nettle. Any news on that? Kevin
