R4 Debian-9 / Whonix-14 Templates do not start on Qubes 3.2

[entr0py]

qubes-template-debian-9-4.0.0-201711030329
qubes-template-whonix-gw-4.0.0-201710200209
fail to start on Qubes 3.2 with: cannot execute qrexec-daemon

Is this expected behavior? Do these templates need to be built specifically for 3.2?

[    1.137089] blkfront: xvda: flush diskcache: enabled; persistent grants: enabled; indirect descriptors: enabled;
[    1.138230] random: fast init done
[    1.157058]  xvda: xvda1 xvda2 xvda3
[    1.183743] blkfront: xvdb: flush diskcache: enabled; persistent grants: enabled; indirect descriptors: enabled;
[    1.197403] blkfront: xvdc: flush diskcache: enabled; persistent grants: enabled; indirect descriptors: enabled;
[    1.204163]  xvdc: xvdc1
[    1.238083] blkfront: xvdd: barrier or flush: disabled; persistent grants: enabled; indirect descriptors: enabled;
Waiting for /dev/xvda* devices...
Qubes: Doing R/W setup for TemplateVM...
[    1.253947]  xvdc: xvdc1
[    1.254705]  xvdc: xvdc1
Setting up swapspace version 1, size = 1073737728 bytes
UUID=xxxx
Qubes: done.
modprobe: module ext4 not found in modules.dep
mount: mounting /dev/mapper/dmroot on /sysroot failed: Invalid argument
Waiting for /dev/xvdd device...
[    1.284169] EXT4-fs (xvdd): mounting ext3 file system using the ext4 subsystem
[    1.285457] EXT4-fs (xvdd): mounted filesystem with ordered data mode. Opts: (null)
mount: can't find /sysroot in /proc/mounts
mount: can't find /sysroot in /proc/mounts

[marmarek]

Is this expected behavior? Do these templates need to be built specifically for 3.2?

Yes, you can start 3.2 template on 4.0 (with some limited functionality), but not the other way around.

[marmarek]

Is this expected behavior? Do these templates need to be built specifically for 3.2?

Yes, you can start 3.2 template on 4.0 (with some limited functionality), but not the other way around.