← Back to team overview

group.of.nepali.translators team mailing list archive

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

 

This bug was fixed in the package grub2-signed - 1.66.6

---------------
grub2-signed (1.66.6) xenial; urgency=medium

  * Rebuild against grub2 2.02~beta2-36ubuntu3.6. (LP: #1229458,
#1519836)

 -- Mathieu Trudel-Lapierre <cyphermox@xxxxxxxxxx>  Mon, 19 Dec 2016
21:12:45 -0500

** Changed in: grub2-signed (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
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:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in grub2 source package in Xenial:
  Fix Released
Status in grub2-signed source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  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.

  [Test case]
  Attempt to boot a Generation 2 Hyper-V system from MAAS.

  [Regression potential]
  Since this changes the way timers are picked and used in grub, this may cause things depending on timers (timeout for various features, timeout for the GRUB menu, waiting for keyboard input to get in the menu) may be affected. Any wrong behavior in keyboard input validation for getting into the grub menu on boot should be considered a regression on this patch.

  ---

  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