[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH v5 6/9] libxc: create unmapped initrd in domain builder if supported

On 11/25/2015 11:29 AM, Ian Campbell wrote:
On Wed, 2015-11-25 at 16:18 +0000, 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.
Are we really talking about pygrub here, or pvgrub? (the former is
unaffected by mini-os).

That's exactly what confused me into thinking earlier that the fix that Wei is talking about would resolve my problem.

It's pYgrub.

If we are really talking about pygrub then we are _actually_ talking about
the domain builder when operating on the RHEL5 kernel+initrd -- the fact
ithat they were extracted from the guest filesystem by pygrub is

With RHEL5 I get
      initrd extends beyond end of memory (0x780080eda000 > 0x40000000)
This is reported within the guest, right?

Right. I don't have RHEL5 sources to see what exactly the code is doing but if it prints what it says it does ;-) then the address looks pretty bogus.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.