Comment 2 for bug 1918265

Hi,

So for secureboot it's off, the system doesn't boot with it on (compatible key not included with 2012R2's Hyper-V i suppose.

The shim used was the one setup from 20.04.2 install image, technically it's not the same as the one in the "shim" package:

78415fb8fb9b909f8029858113f1335f /boot/efi/EFI/ubuntu/shimx64.efi
9bdc83ad343e8745e1f3d55c36cf2df6 /usr/lib/shim/shimx64.efi

But some build information extracted from the binary seem to say otherwise :

$Version: 15 $
$BuildMachine: Linux x86_64 x86_64 x86_64 GNU/Linux $
$Commit: a4a1fbe728c9545fc5647129df0cf1593b953bec $

$Version: 15 $
$BuildMachine: Linux x86_64 x86_64 x86_64 GNU/Linux $
$Commit: a4a1fbe728c9545fc5647129df0cf1593b953bec $

I have attached a still frame captured from grub boot with "set debug=all". It's the frame just before the VM reboot.

As for the linux-azure kernel, i see no differences on the boot process in any of the three following kernels:
  vmlinuz-5.8.0-44-generic
  vmlinuz-5.4.0-1041-azure
  vmlinuz-5.4.0-67-generic

It may be interesting to know however that when the linux-azure-5.4.0.1041.21 kernel was introduced into Ubuntu 18.04 i started to experience weird boot issues causing me to un-install it and fall back to the 5.0.0-1036-azure kernel.

There might be some commun issue here