Installing UEFI boot entry on Hyper-V gen 2 corrupts VM configuration, making the VM unuseable
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
efibootmgr (Debian) |
Fix Released
|
Unknown
|
|||
efibootmgr (Ubuntu) |
Fix Released
|
High
|
Colin Watson |
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-
ProcVersionSign
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)
Related branches
Changed in efibootmgr (Debian): | |
status: | Unknown → New |
Changed in efibootmgr (Debian): | |
status: | New → Fix Released |
Status changed to 'Confirmed' because the bug affects multiple users.