[Bug 1918265] Re: Random boot failure with Ubuntu 20.04 / grub 2.04 and Hyper-V 2012r2

[ben]

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

** Attachment added: "2021-03-18 23-26-47.00_00_09_21.Still001.png"
   https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1918265/+attachment/5478015/+files/2021-03-18%2023-26-47.00_00_09_21.Still001.png

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/1918265

Title:
  Random boot failure with Ubuntu 20.04 / grub 2.04 and Hyper-V 2012r2

Status in grub2 package in Ubuntu:
  New

Bug description:
  Hi,

  We are experiencing some weird boot issues with Ubuntu 20.04 and
  Hyper-V 2012r2.

  In two cases the installation started successfully, as did the VM
  initial boot and then issues started to arise, where the boot process
  started to fail.

  grub start, the menu pop-up and then just after loading kernel and
  initrd (tried to put some echo(es) in the config the VM somehow reset
  and the menu pop-up back again.

  After a few of thoses either the VM shut-down or the boot is
  successfull, It seems completly random..

  Here it is captured on video:
    https://www.youtube.com/watch?v=5Bk3S-YGDZk

  If i setup a direct EFI-STUB boot of the kernel+initrd the boot
  process works every times.

  I suspected the "save_env/load_env" for a while but a stripped down
  grub.cfg give the same result..

  > insmod gzio
  > insmod part_gpt
  > insmod ext2
  > set root='hd0,gpt2'
  > if [ x$feature_platform_search_hint = xy ]; then
  >  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2  94ebc17e-6aca-4e42-b489-b3eaa8a32d90
  > else
  >  search --no-floppy --fs-uuid --set=root 94ebc17e-6aca-4e42-b489-b3eaa8a32d90
  > fi
  > linux	/vmlinuz-5.8.0-44-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro nosplash elevator=noop 
  > initrd	/initrd.img-5.8.0-44-generic
  > boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1918265/+subscriptions