On 25/11/15 17:12, Boris Ostrovsky wrote: > On 11/12/2015 08:43 AM, Juergen Gross wrote: >> In case the kernel of a new pv-domU indicates it is supporting an >> unmapped initrd, don't waste precious virtual space for the initrd, >> but allocate only guest physical memory for it. > > This patch breaks 32-bit pygrub. > > I am not 100% sure yet but it may be that only 64-bit guests are affected. > > With RHEL5 I get > initrd extends beyond end of memory (0x780080eda000 > 0x40000000)
Let me summarize your findings: You are using a 32 bit dom0 to start a 64 bit RHEL5 guest via pygrub (not pvgrub). The guest then barfs about the initrd position in memory. Can you get the debug output of the domain builder? This would help to see what is really happening. Juergen _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
