← Back to team overview

canonical-ubuntu-qa team mailing list archive

[Bug 2055342] [NEW] Google cloud t2a VMs are unable to boot arm64 generic-64k kernels

 

Public bug reported:

This is not necessarily a bug, just an unsupported configuration.
Attempts to install and boot a generic-64k kernel on t2a instances
result in a failure. The collected console log states:

UEFI: Attempting to start image.
Description: ubuntu
FilePath: HD(15,GPT,D50A4893-6539-4486-920D-921ED26E81CB,0x800,0x31801)/\EFI\ubuntu\shimaa64.efi
OptionNumber: 2.

Loading Linux 5.15.0-100-generic-64k ...

Loading initial ramdisk ...

EFI stub: ERROR: This 64 KB granular kernel is not supported by your CPU
Application failed, r = 3


  Failed to boot both default and fallback entries.


Press any key to continue...


The VM hangs at this point. This latest experiment was done with a jammy image using jammy/linux version 5.15.0-100.110.

** Affects: ubuntu-kernel-tests
     Importance: Undecided
         Status: New

** Attachment added: "t2a-standard-4-arm64-64k-console.log"
   https://bugs.launchpad.net/bugs/2055342/+attachment/5750419/+files/t2a-standard-4-arm64-64k-console.log

-- 
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
https://bugs.launchpad.net/bugs/2055342

Title:
  Google cloud t2a VMs are unable to boot arm64 generic-64k kernels

Status in ubuntu-kernel-tests:
  New

Bug description:
  This is not necessarily a bug, just an unsupported configuration.
  Attempts to install and boot a generic-64k kernel on t2a instances
  result in a failure. The collected console log states:

  UEFI: Attempting to start image.
  Description: ubuntu
  FilePath: HD(15,GPT,D50A4893-6539-4486-920D-921ED26E81CB,0x800,0x31801)/\EFI\ubuntu\shimaa64.efi
  OptionNumber: 2.

  Loading Linux 5.15.0-100-generic-64k ...

  Loading initial ramdisk ...

  EFI stub: ERROR: This 64 KB granular kernel is not supported by your CPU
  Application failed, r = 3

  
    Failed to boot both default and fallback entries.

  
  Press any key to continue...

  
  The VM hangs at this point. This latest experiment was done with a jammy image using jammy/linux version 5.15.0-100.110.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2055342/+subscriptions



Follow ups