From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Shriram Rajagopalan <rshriram@cs.ubc.ca>
Cc: xen-devel@lists.xensource.com
Subject: Re: 2.6.38 PV Guest boot failure - error while pinning mfn..
Date: Sun, 20 Mar 2011 16:45:13 -0400 [thread overview]
Message-ID: <20110320204512.GF3948@dumpdata.com> (raw)
In-Reply-To: <20110320200543.GA3447@dumpdata.com>
On Sun, Mar 20, 2011 at 04:05:43PM -0400, Konrad Rzeszutek Wilk wrote:
> On Sat, Mar 19, 2011 at 06:22:17PM -0700, Shriram Rajagopalan wrote:
> > The kernel is built from konrad's tree, devel/next-2.6.39
> > commit:f4ddaaf4338999227b3f724615d8aecbe88d3f04
Ok. So you got Stefano's latest goodies:
* devel/bootup-fixes.v3:
watchdog, SP5100: Check if firmware has set correct value in tcobase.
xen: update mask_rw_pte after kernel page tables init changes
xen: set max_pfn_mapped to the last pfn mapped
x86: Cleanup highmap after brk is concluded
> >
> > 64 bit PV guest, 64 bit dom0, xen 4.1.0-rc7-pre
Is the 64-bit dom0 kernel == 64-bit domu kernel?
> > I have not been able to boot a pv domU, with the above kernel.
>
> You might need this git commit:
> 31fd38842ab07b95440f24c6180d9a2c14b35111
>
> tc/cmos: Check if ACPI is disabled, and if so don't attempt
>
> If you pull my tree, you should be able to cherrypick.
Also do 'earlyprintk=xenboot' in your PV guest and see what it tells you
(if anything).
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-03-20 20:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-20 1:22 2.6.38 PV Guest boot failure - error while pinning mfn Shriram Rajagopalan
2011-03-20 20:05 ` Konrad Rzeszutek Wilk
2011-03-20 20:45 ` Konrad Rzeszutek Wilk [this message]
2011-03-20 21:05 ` Shriram Rajagopalan
2011-03-20 21:19 ` Shriram Rajagopalan
2011-03-21 11:30 ` Konrad Rzeszutek Wilk
2011-03-21 14:50 ` Shriram Rajagopalan
2011-03-22 17:00 ` Konrad Rzeszutek Wilk
2011-03-22 17:16 ` Shriram Rajagopalan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110320204512.GF3948@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=rshriram@cs.ubc.ca \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.