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

Launchpad Bug Tracker 1519836 at bugs.launchpad.net
Mon May 16 23:44:26 UTC 2016

This bug was fixed in the package grub2 - 2.02~beta2-36ubuntu6

grub2 (2.02~beta2-36ubuntu6) yakkety; urgency=medium

  * Fix booting on Hyper-V gen 2 VMs due to the lack of PIT there; we can deal
    with this by using other timers when PIT aren't available. (LP: #1519836)
    - debian/patches/git_tsc_use_alt_delay_sources_d43a5ee6.patch
    - debian/patches/git_split_pmtimer_wait_tsc_d9a3bfea.patch
    - debian/patches/git_fix_tsc_calibration_pit_a03c1034.patch

 -- Mathieu Trudel-Lapierre <cyphermox at ubuntu.com>  Fri, 13 May 2016
12:28:38 -0400

** Changed in: grub2 (Ubuntu)
       Status: In Progress => Fix Released

You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.

  MaaS fails to boot Hyper-V Generation 2 virtual machines

Status in MAAS:
Status in grub2 package in Ubuntu:
  Fix Released

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

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


  and an alternative in the discussion here:


  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?


To manage notifications about this bug go to:

More information about the foundations-bugs mailing list