Comment # 48 on bug 1018741 from Mike Latimer

(In reply to lists dev from comment #47)
> There's something obviously unhealthy about in-chroot, 'just' `mkinitrd`.

I believe this is likely due to the logic in mkinitrd which detects the driver
used by the root disk. In the chroot environment, this is probably failing, and
then failing to add xen-blkfront into the initrd, or failing to setup the root
device properly. The `mkinitrd -A` just adds everything and it gets around the
problem.

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.