Hi, I have an image build here: osc rbl Virtualization:Appliances:Images:Testing_x86:debian test-image-live-disk -M Disk images x86_64 It starts Qemu with [ 18s] /usr/bin/qemu-kvm ... -kernel /boot/kernel.obs.guest -initrd /boot/initrd.obs.guest I assume it does this because there is no kernel-obs-build or any other kernel (linux-generic) installed when building the test for debian I wanted to extend the testing matrix and add a test for luks (I plan to add support for luks2 in kiwi and wanted to have it really tested everywhere) When I do this the build ends with: [ 317s] [ DEBUG ]: 08:33:34 | EXEC: [cryptsetup --key-file /var/tmp/kiwi_9teoanif luksOpen /dev/mapper/loop0p2 luksRoot] [ 319s] [ 300.670200] device-mapper: table: 254:3: crypt: unknown target type Device mapper complains because the kernel or the initrd did not offer support for dm_crypt. Now the question is where does kernel.obs.guest and initrd.obs.guest come from ? How can I influence them, e.g providing an initrd that has dm_crypt as module, or a kernel that has it compiled in ... or any other solution suggestion :) Thanks much Regards, Marcus -- Public Key available via: https://keybase.io/marcus_schaefer/key.asc keybase search marcus_schaefer ------------------------------------------------------- Marcus Schäfer Am Unterösch 9 Tel: +49 7562 905437 D-88316 Isny / Rohrdorf Germany -------------------------------------------------------