[Bug 1519836] Re: MaaS fails to boot Hyper-V Generation 2 virtual machines
Adrian Vladu
avladu at cloudbasesolutions.com
Thu Sep 29 10:04:38 UTC 2016
Hello,
I have tried the grub2 efi version from here:
http://archive.ubuntu.com/ubuntu/dists/yakkety/main/uefi/grub2-amd64/2.02~beta2-36ubuntu11/grubnetx64.efi
and it did not work for Hyper-V gen 2 vms to boot from pxe.
On the other hand, on a yakkety, I have manually built grub2 with the
following commands:
sudo apt-get source grub-efi-amd64
cd grub2-2.02~beta2/
sudo apt-get install fakeroot
dpkg-buildpackage -b # Wait for like an hour
I have used the grub file from debian/grub2-images/2.02~beta2-36ubuntu11/grubnetx64.efi and the pxe boot was successful.
It seems the yakkety builds on archive.ubuntu.com are not working. Can
someone take a look into it?
Thank you,
Adrian Vladu
--
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:
Fix Released
Status in grub2-signed package in Ubuntu:
Fix Released
Status in grub2 source package in Xenial:
In Progress
Status in grub2-signed source package in Xenial:
In Progress
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
More information about the foundations-bugs
mailing list