Ubuntu
grub2 package

pvgrub "premature end of file" on new kernel

Bug #1780098 reported by Owen Dunn
42
This bug affects 7 people
Affects Status Importance Assigned to Milestone
grub2 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

When trying to boot 4.4.0-130.156 via pvgrub I get the following message:

error: premature end of file /boot/vmlinuz-4.4.0-130-generic.
alloc magic is broken at 0xfefb2b40: fedd3920
Aborted. Press any key to exit.

Previous kernels (e.g. 4.4.0-127.153) boot normally, as does any kernel when booted directly by specifying its kernel, ramdisk, and options in the xen domU configuration file.

Ubuntu release: Ubuntu 16.04.4 LTS

Package versions (on dom0):

grub-common 2.02~beta2-36ubuntu3.18
grub-pc 2.02~beta2-36ubuntu3.18
grub-xen-bin 2.02~beta2-36ubuntu3.18
grub-pc-bin 2.02~beta2-36ubuntu3.18
grub-xen-host 2.02~beta2-36ubuntu3.18
grub-common 2.02~beta2-36ubuntu3.18
grub2-common 2.02~beta2-36ubuntu3.18

libxen-4.6:amd64 4.6.5-0ubuntu1.4
libxenstore3.0:amd64 4.6.5-0ubuntu1.4
xen-hypervisor-4.6-amd64 4.6.5-0ubuntu1.4
xen-utils-4.6 4.6.5-0ubuntu1.4
xen-utils-common 4.6.5-0ubuntu1.4
xenstore-utils 4.6.5-0ubuntu1.4

Package versions on domU:

linux-generic 4.4.0.130.136
linux-headers-4.4.0-127-generic 4.4.0-127.153
linux-headers-4.4.0-130-generic 4.4.0-130.156
linux-headers-generic 4.4.0.130.136
linux-image-4.4.0-127-generic 4.4.0-127.153
linux-image-4.4.0-130-generic 4.4.0-130.156
linux-image-extra-4.4.0-127-generic 4.4.0-127.153
linux-image-extra-4.4.0-130-generic 4.4.0-130.156
linux-image-generic 4.4.0.130.136

The root filesystem (containing /boot) on the domU is ext4.

I've attached the xen domain configuration from the dom0 and the grub.cfg from the domU

Tags: patch
Revision history for this message
Owen Dunn (osd1000) wrote :
Revision history for this message
Owen Dunn (osd1000) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in grub2 (Ubuntu):
status: New → Confirmed
Revision history for this message
David Kowis (dkowis) wrote :

This does not occur with the version of grub-xen on 18.04

root@nosgoth:/etc/xen/auto# apt show grub-xen
Package: grub-xen
Version: 2.02-2ubuntu8

I was using a self-built version of it mounted in, and that version matched 16.04's version. After updating, I forgot to stop doing that. An upgrade to 18.04 will resolve it, or back-porting 18.04's package.

Revision history for this message
Owen Dunn (osd1000) wrote :

The relevant change that makes 18.04's version work where 16.04's doesn't seems to be 15aee573d2312ebf4aab53d07d3d30eccf1484f9 upstream.

Revision history for this message
Owen Dunn (osd1000) wrote :
Revision history for this message
Krister Bäckman (ixevix) wrote :

Can confirm that upgrading the dom0 grub and building a new pvgrub solved the problem. I have a clone of the grub git that I'm building manually on Debian Jessie.

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "fix-invalid-payload-size" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

tags: added: patch
Revision history for this message
Bjørn Skobba (bjornsk) wrote :

Just installed 4.4.0-131.157 and it seems like it is working again

Revision history for this message
Beat (beat-c) wrote :

I also just installed 4.4.0-131.157 over 4.4.0-128 (that I reinstalled that and booted on it to avoid the 4.4.0-130 bug) and it seems like it is working again in a Xen VM with PVGrub. My issue was identical, but with a different error message (bad memory access error in the very first initrd boot phase also pointing to a badly built initrd.img).

Revision history for this message
Beat (beat-c) wrote :

Btw, while cleaning up the systems, I now found that in the /boot folder of one of the 2 systems that I upgraded and both (=all) failed with 4.4.0-130, I also saw a strange file named "initrd.img-4.4.0-139" that got installed at exactly same time than "initrd.img-4.4.0-130-generic" and other normal 4.4.0-130 files. Maybe that helps find the issue ?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.