Activity log for bug #1826453

Date Who What changed Old value New value Message
2019-04-25 20:26:44 Dexuan Cui bug added bug
2019-04-25 20:47:41 Joseph Salisbury bug added subscriber Joseph Salisbury
2019-04-26 19:30:19 Mathieu Trudel-Lapierre nominated for series Ubuntu Trusty
2019-04-26 19:30:19 Mathieu Trudel-Lapierre bug task added grub2 (Ubuntu Trusty)
2019-04-26 19:30:19 Mathieu Trudel-Lapierre nominated for series Ubuntu Xenial
2019-04-26 19:30:19 Mathieu Trudel-Lapierre bug task added grub2 (Ubuntu Xenial)
2019-04-26 19:30:27 Mathieu Trudel-Lapierre grub2 (Ubuntu): status New Fix Released
2019-04-26 19:30:33 Mathieu Trudel-Lapierre grub2 (Ubuntu Xenial): status New In Progress
2019-04-26 19:30:36 Mathieu Trudel-Lapierre grub2 (Ubuntu Xenial): assignee Mathieu Trudel-Lapierre (cyphermox)
2019-04-26 19:30:39 Mathieu Trudel-Lapierre grub2 (Ubuntu Xenial): importance Undecided Medium
2019-04-27 12:36:28 Francis Ginther tags id-5cc33192fdf0ba69633c3a45
2019-04-29 18:12:45 Mathieu Trudel-Lapierre description In a Ubuntu 16.04.6 VM, which runs as a Gen2 VM on Hyper-V, I add GRUB_GFXPAYLOAD_LINUX="text" into /etc/default/grub and run update-grub; next, grub2 prints the below error: error: invalid video mode specification `text'. Booting in blind mode This means grub2 passes a zero value for the "lfb_base" to Linux kernel, which then fails to reserve the framebuffer MMIO range in drivers/hv/vmbus_drv.c: vmbus_reserve_fb(); as a result, when we pass through a PCIe device to the VM, the PCIe device may get a PCI MMIO BAR in the FB MMIO range, causing a conflict, and the PCIe device can not work in the VM. The issue can not reproduce with Ubuntu 18.04. It turns out the grub2 in Ubuntu 18.04 has the below fix: video: skip 'text' gfxpayload if not supported, to fallback to default (https://git.launchpad.net/~ubuntu-core-dev/grub/+git/ubuntu/commit/?id=38d9e2f862a96a039ae8ca8b87b8615d154ceda4). I'm asking the patch author (Mathieu Trudel-Lapierre) to submit the patch to the upstream grub and this is the upstream bug link: https://savannah.gnu.org/bugs/?56217 . Here this launchpad bug is for Ubuntu 16.04 and 14.04. [Impact] UEFI users booting VMs on Hyper-V [Test case] 1) Install Ubuntu 16.04 in a Gen2 VM on Hyper-V (Windows) 2) After install; edit /etc/default/grub to add: GRUB_GFXPAYLOAD_LINUX="text" 3) Run 'sudo update-grub' 4) Reboot Verify whether the system writes an error/warning on console during boot (this shows up and disappears quickly, one must watch the console attentively): error: invalid video mode specification `text'. Booting in blind mode [Regression potential] There is minimal risk of regression; this is a patch that has been succesfully used in other releases to address the same issue (see bug 1711452). It only affects graphical payload selection in grub to avoid a value that is clearly invalid, thus skipping the error value and falling back to the default text-mode. Care should be taking while testing to identify any possible issues with displaying the grub menu or outputting information from the kernel at console as the system boots (if applicable). --- In a Ubuntu 16.04.6 VM, which runs as a Gen2 VM on Hyper-V, I add GRUB_GFXPAYLOAD_LINUX="text" into /etc/default/grub and run update-grub; next, grub2 prints the below error: error: invalid video mode specification `text'. Booting in blind mode This means grub2 passes a zero value for the "lfb_base" to Linux kernel, which then fails to reserve the framebuffer MMIO range in drivers/hv/vmbus_drv.c: vmbus_reserve_fb(); as a result, when we pass through a PCIe device to the VM, the PCIe device may get a PCI MMIO BAR in the FB MMIO range, causing a conflict, and the PCIe device can not work in the VM. The issue can not reproduce with Ubuntu 18.04. It turns out the grub2 in Ubuntu 18.04 has the below fix: video: skip 'text' gfxpayload if not supported, to fallback to default (https://git.launchpad.net/~ubuntu-core-dev/grub/+git/ubuntu/commit/?id=38d9e2f862a96a039ae8ca8b87b8615d154ceda4). I'm asking the patch author (Mathieu Trudel-Lapierre) to submit the patch to the upstream grub and this is the upstream bug link: https://savannah.gnu.org/bugs/?56217 . Here this launchpad bug is for Ubuntu 16.04 and 14.04.
2019-04-29 18:48:10 Brian Murray grub2 (Ubuntu Xenial): status In Progress Fix Committed
2019-04-29 18:48:11 Brian Murray bug added subscriber Ubuntu Stable Release Updates Team
2019-04-29 18:48:12 Brian Murray bug added subscriber SRU Verification
2019-04-29 18:48:16 Brian Murray tags id-5cc33192fdf0ba69633c3a45 id-5cc33192fdf0ba69633c3a45 verification-needed verification-needed-xenial
2019-04-30 17:52:18 Brian Murray bug task added grub2-signed (Ubuntu)
2019-04-30 20:15:11 Brian Murray grub2-signed (Ubuntu Xenial): status New Fix Committed
2019-04-30 20:15:15 Brian Murray grub2-signed (Ubuntu): status New Fix Released
2019-05-02 14:29:20 Mathieu Trudel-Lapierre tags id-5cc33192fdf0ba69633c3a45 verification-needed verification-needed-xenial id-5cc33192fdf0ba69633c3a45 verification-done-xenial
2019-05-06 08:49:39 Launchpad Janitor grub2 (Ubuntu Xenial): status Fix Committed Fix Released
2019-05-06 08:49:47 Ɓukasz Zemczak removed subscriber Ubuntu Stable Release Updates Team
2019-05-06 08:49:50 Launchpad Janitor grub2-signed (Ubuntu Xenial): status Fix Committed Fix Released