From: Scott Garron <xen-devel@sce.pridelands.org>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
xen-devel@lists.xensource.com,
Konrad Wilk <konrad.wilk@oracle.com>
Subject: Re: BUG: unable to handle kernel paging request - balloon_init - xen-4.1.0 - 2.6.32.39
Date: Fri, 29 Apr 2011 19:08:29 -0400 [thread overview]
Message-ID: <4DBB44ED.2020701@sce.pridelands.org> (raw)
In-Reply-To: <4ebbb8ac-77a5-4525-b69e-273c177c05e2@default>
On 04/29/2011 03:38 PM, Dan Magenheimer wrote:
> Since you are using dom0_mem, there really should be no reason why
> the balloon driver needs to get initialized. For the balloon driver
> to work properly, it needs a correct E820 map and there have been
> recent upstream changes in the balloon driver involving E820. If we
> assume that your E820 map is indeed broken, the easiest fix for your
> machine might be just to modify balloon_init in dom0 to immediately
> fail (and return -ENODEV).
Returning -ENODEV at the beginning of balloon_init() did allow the
machine to boot, but something is definitely still amiss:
Trying to start any domUs yields:
simba@hailstorm:~$ sudo xm create test.cfg
Using config file "/etc/xen/test.cfg".
Error: Failed to query current memory allocation of dom0.
Oddly enough, xencommons and xend started and xm list and xm info
show everything correctly.
And this is just bizarre...
simba@hailstorm:~$ free
total used free shared buffers cached
Mem: 552 18014398509158460 324076 0 11428
34656
-/+ buffers/cache: 18014398509112376 370160
Swap: 0 0 0
I just tried grabbing the most recent BIOS revision from Tyan for
this motherboard (was running 2882_306, flashed it to 2882_309). Same
results.
--
Scott Garron
next prev parent reply other threads:[~2011-04-29 23:08 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 0:04 BUG: unable to handle kernel paging request - balloon_init - xen-4.1.0 - 2.6.32.39 Scott Garron
2011-04-26 3:15 ` Konrad Rzeszutek Wilk
2011-04-26 5:03 ` Scott Garron
2011-04-27 20:09 ` Konrad Rzeszutek Wilk
2011-04-27 23:45 ` Scott Garron
[not found] ` <20110428183019.GA9852@dumpdata.com4DBA1EA4.5010004@sce.pridelands.org>
2011-04-28 18:30 ` Konrad Rzeszutek Wilk
2011-04-29 0:15 ` Scott Garron
2011-04-29 2:12 ` Scott Garron
2011-04-29 14:43 ` Dan Magenheimer
2011-04-29 16:56 ` Scott Garron
2011-04-29 19:38 ` Dan Magenheimer
2011-04-29 23:08 ` Scott Garron [this message]
2011-05-04 15:58 ` Konrad Rzeszutek Wilk
2011-05-04 19:19 ` Scott Garron
2011-05-04 19:35 ` Konrad Rzeszutek Wilk
2011-05-04 20:17 ` Scott Garron
2011-05-04 20:23 ` Konrad Rzeszutek Wilk
2011-05-04 21:55 ` Scott Garron
2011-05-04 22:16 ` Konrad Rzeszutek Wilk
2011-05-04 23:23 ` Scott Garron
2011-05-05 18:34 ` Konrad Rzeszutek Wilk
2011-05-05 20:48 ` Scott Garron
2011-05-05 21:06 ` Konrad Rzeszutek Wilk
2011-06-06 18:00 ` Scott Garron
2011-06-06 19:17 ` Pasi Kärkkäinen
2011-06-06 21:33 ` Scott Garron
2011-06-07 19:19 ` Konrad Rzeszutek Wilk
2011-06-08 18:25 ` Scott Garron
2011-06-08 19:29 ` Konrad Rzeszutek Wilk
2011-06-09 20:04 ` Scott Garron
2011-06-10 12:59 ` Konrad Rzeszutek Wilk
2011-06-10 16:51 ` Scott Garron
2011-06-13 22:03 ` Konrad Rzeszutek Wilk
2011-06-13 23:20 ` Scott Garron
2011-06-14 13:55 ` BUG: unable to handle kernel NULL pointer dereference at IP: [<ffffffff8105ae4c>] process_one_work+ Konrad Rzeszutek Wilk
2011-06-14 21:55 ` Scott Garron
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=4DBB44ED.2020701@sce.pridelands.org \
--to=xen-devel@sce.pridelands.org \
--cc=dan.magenheimer@oracle.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--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.