@@ -496,7 +496,17 @@ sub setupboot_grub2 ($$$$) {
" kernel $entry->{KernVer}, not $want_kernver)");
} elsif ($want_xsm && !defined $entry->{Xenpolicy}) {
logm("(skipping entry at $entry->{StartLine}..$.;".
- " XSM policy file not present)");
+ " XSM policy file not mentioned)");
+ } elsif ($ho->{Suite} =~ m/buster/ &&
+ defined $entry->{Xenpolicy} &&
+ !$bootfiles{
+ $entry->{Xenpolicy} =~ m{^/?} ? $' : die
+ }) {
+ # Our 20_linux_xen bodge with buster's update-grub
+ # generates entries which mention /boot/xenpolicy-xen
+ # even though that file doesn't exist on ARM64.
+ logm("(skipping entry at $entry->{StartLine}..$.;".
+ " XSM policy file not on disk!)");
} else {
# yes!
last;
This is a complex interaction between update-grub and the Xen build system on ARM64. Not sure exactly who to blame but since we have our own 20_linux_xen bodge, let's wait until we don't. Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com> --- Osstest/Debian.pm | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-)