[Bug 1519836] Re: MaaS fails to boot Hyper-V Generation 2 virtual machines

[Chris Valean]

The suggested patch from comment #5 has been merged in the 2.02 beta3
code.

We've built grub2 from sources and used the compiled grubx64.efi in MAAS
1.9 to attempt to boot a Gen2 VM.

However,  the boot process failed to load the kernel and perform a PXE boot, exactly because of the timer not allowing for the transfers to occur.
So from our tests this patch doesn't resolve the problem.

The original patch mentioned has been used numerous times with Ubuntu,
as we even have a wiki article published at http://wiki.cloudbase.it
/hyperv-uefi-grub as a reference for MAAS deployments if Generation 2
VMs are to be used.

-- 
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/1519836

Title:
  MaaS fails to boot Hyper-V Generation 2 virtual machines

Status in MAAS:
  Invalid
Status in grub2 package in Ubuntu:
  Incomplete

Bug description:
  When trying to deploy a "Generation 2" virtual machine on Hyper-V,
  grub fails to fetch the linux kernel and initrd from MaaS. The
  operation times out immediately, because the Generation 2 VMs are
  missing the Programmable Interval Timer (PIT). The current version of
  grub still requires this interface to exist, in order to calculate
  time.

  There is a patch that uses the EFI SetTimer() available here:

  http://savannah.gnu.org/bugs/?42944

  and an alternative in the discussion here:

  https://lists.gnu.org/archive/html/grub-devel/2014-10/msg00016.html

  that uses pmtimer instead. I am aware that grub is a critical package.
  What is the official/proper way to fix this issue? Can a patched
  grubnetx64.efi be packaged with MaaS? Do we have to wait for this fix
  to merge?

  Gabriel

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1519836/+subscriptions