Follow-up Comment #7, bug #46014 (project grub):
I downloaded grub-2.02~rc1.tar.xz, debianized it based on
grub2_2.02~beta3-4.debian.tar.xz (two patches dropped as they are included in
rc1), and applied commit 8a96fc409373fffda99e18a8438ddfc6bb787bc8 on top of it
all. I did not include the "xen: Fix parsing of XZ kernel" patch; I take your
question about git master to mean that I should. Built .deb packages using
pbuilder and the Debian "stretch" repositories; the source and binary
packages, and the build log, are all available at
https://ttt.astro.su.se/~gelato/noIo7WNwqA/ . The guest has grub-common,
grub2-common, grub-xen and grub-xen-bin installed, then "grub-install
--target=i386-xen /dev/xvda" was run.
I had initially updated only the guest's GRUB but have now tested with the new
grub-i386-xen.bin (same build as above, package grub-xen-host) on the dom0
side; no difference in behaviour when booting a guest with
/boot/xen/pvboot-i386.elf.
(Aside: there are differences in behaviour in circumstances beyond the scope
of this bug; e.g., the new grub-i386-xen.bin doesn't like Debian 8 guests
built with grub-install --target=i386-pc, complains about the initrd; maybe
the old guest grub.cfg isn't quite compatible?)
The host runs Debian 8.7 "jessie" and its Xen 4.4.1-9+deb8u8 packages. x86_64
of course: this version of Xen does not support 32-bit dom0.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?46014>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-grub mailing list
Bug-grub@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-grub
