[Bug 1272664] Re: Installing UEFI boot entry on Hyper-V gen 2 corrupts VM configuration, making the VM unuseable

[Abhishek Gupta]

There are two bugs here:

a) The UEFI boot entry seems to be created incorrectly. It appears that
there are 6 extra zeroes in the Hard Drive Media Device Path as shown in
Red (See attached picture). We suspect that the structure related to the
hard drive media device path is not packed because of which it's size is
coming out to be 0x30 bytes instead of the expected 0x2A as per UEFI
specifications.

As of now we are examining the files in the Linux kernel that may be
relevant to the hard drive media device path and will shortly post the
names of the files that might be containing this issue.

b) Hyper-V is unable to deal with improperly formatted hard drive media
device paths. The problem has been reported to the Hyper-V team and will
be addressed in future.

I have added the relevant Ubuntu people to this issue. Please take note and fix the problem.
Thanks,
Abhishek

** Attachment added: "UEFI Boot Entry.PNG"
   https://bugs.launchpad.net/ubuntu/+source/efibootmgr/+bug/1272664/+attachment/4010618/+files/UEFI%20Boot%20Entry.PNG

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to efibootmgr in Ubuntu.
https://bugs.launchpad.net/bugs/1272664

Title:
  Installing UEFI boot entry on Hyper-V gen 2 corrupts VM configuration,
  making the VM unuseable

Status in “efibootmgr” package in Ubuntu:
  Confirmed

Bug description:
  Installing Ubuntu on a generation 2 Hyper-V VM corrupts the
  configuration of said VM, so the VM cannot be loaded by the VM manager
  any more and the VMs settings are no longer accessable.

  I narrowed the cause of the bug down to the creation of the boot
  loader entry in the VMs UEFI.

  Steps to repoduce:
  * Create a new generation 2 VM in Hyper-V
  * Use a Alpha 2 (or newer) image of 14.04 to install (X-)Ubuntu (Kernel 3.13 or newer is required for the generation 2)
  * After the successful installation try to access the VMs settings menu -> No longer accessaible, Hyper-V returns an error
  * Check the Hyper-V Manager -> The corrupted VM is no longer in the list of VMs.

  Additional it can be confirmed afterwards by doing:
  * Create a new generation 2 VM using the same virtual hard drive file (*.vhdx) used before.
  * Boot into the live session.
  * Create the UEFI boot entry again
  -> VM is again corrupted and shows the same symptoms as above.

  This bug breaks Ubuntu on Hyper-V generation 2. That is a serious
  issue, as the generation 2 offers a lot of improvements over the
  generation 1.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: grub-efi-amd64-signed 1.27+2.00-22
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.336ubuntu1
  Date: Sat Jan 25 12:25:12 2014
  LiveMediaBuild: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140121.1)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: grub2-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/efibootmgr/+bug/1272664/+subscriptions