On 11/25/2015 11:18 AM, Wei Liu wrote:
On Wed, Nov 25, 2015 at 11:12:12AM -0500, 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.
This particular patch?
We discovered a bug in mini-os that caused 32-bit pygrub to break withi
this series. It's now fixed in mini-os upstream. Check Config.mk for
mini-os commit that fixes the bug.
Yes, I was waiting for that patch because somehow I thought it was going
to fix this. And it was unrelated.
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)
But this is different from what we found. We need more information.
My wild guess is RHEL5 advertise it supports unmapped initrd but it was
buggy in some way.
Maybe. Unfortunately RHEL5 is the only guest I have available to me
right now that I can test with pygrub on 32 bit. I have others and they
also fail but I am not convinced they fail because of this issue.
I was going to look some more at this but I am not sure how much I will
be able to do before next Monday (it's Thanksgiving 4-day weekend in US)
so I figured I'd post this now.
-boris
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
