without the
-n | --no-name flag, which lead to the xen.gz file having
non-deterministric bytes (the timestamp) in the compressed file.
Signed-off-by: Trammell Hudson
---
xen/Makefile| 2 +-
xen/arch/x86/boot/mkelf32.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff
The xen/arch/x86/boot/mkelf32 executable is preventing Xen hypervisors
from being reproducibly built. It is using an uninitialized stack
buffer for padding after the ehdr and phdr are written to the xen file,
which leads to non-deterministic bytes in the binary.
Additionally, the file is then com
This is in reply to an ancient post to the xen-devel list:
http://ward.vandewege.net/blog/2008/08/kexecing-into-a-xen-kernel/
http://old-list-archives.xenproject.org/archives/html/xen-devel/2008-08/msg00298.html
Ward Vandewege wrote (in 2008):
> There seems to be a regression with regard to kexe
