(In reply to Mike Latimer from comment #48) > I think the 'mkinitrd in chroot' problem is a secondary issue as there > really should be no reason to do that step (under normal circumstances). We > need to fix the problem before it gets to that point. Yes, and there should be a well-understood procedure for when-not-if a Xen DomU &/or UEFI "lose their mind" again. Which happens more frequently that it should, simply because there are still too many new AND moving parts involved.