xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Arno Toell <at@wavecon.de>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	"xen-users@lists.xensource.com" <xen-users@lists.xensource.com>
Subject: Re: [Xen-devel] Re: Hypervisor hangs on startup, 2.6.32-5-xen dom0 kernel panic
Date: Thu, 23 Dec 2010 12:13:27 +0100	[thread overview]
Message-ID: <4D132ED7.9050800@wavecon.de> (raw)
In-Reply-To: <1292937209.4500.1852.camel@zakaz.uk.xensource.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 21.12.2010 14:13, Ian Campbell wrote:
> Might be worth trying the dom0_mem hypervisor parameter to limit the
> initial size of dom0, perhaps to 32G.

Following Ians suggestion I will summarize again, what I've written in
the bug report.

Passing dom0_mem=max:4GB to the hypervisor works around the issue. That
is, the dom0 with underlying hypervisor does boot. Please see
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1698#c4 for a
full dmesg/xm info output.

The relevant part is:

node_to_cpu            : node0:0,2,4,6,8,10,12,14
                         node1:1,3,5,7,9,11,13,15
node_to_memory         : node0:21765
                         node1:24425
node_to_dma32_mem      : node0:0
                         node1:1969



Moreover my company is willing to pay anyone who fixes this bug a
symbolic fee of 1000 EUR as thank-you for letting us making use of Xen;
either personally to the contributor or to a (non-profit) organization
of the contributor's choice.

- -- 
mit freundlichen Grüßen,
Arno Töll, BSc.
GnuPG Key-ID: 0x8408D4C4

Wavecon GmbH | Frankenstrasse 9 | 90762 Fuerth
Web: wavecon.de | Mail + Jabber at@wavecon.de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk0TLtYACgkQBWM6U4QI1MTMPwCg1x3YaBWRgoEiB9SU24AvM2Ze
N2kAoJWUP7KLX5zWDQ+RtYRoD7xjVVR3
=7heG
-----END PGP SIGNATURE-----

  reply	other threads:[~2010-12-23 11:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4D0AD782.8030204@wavecon.de>
     [not found] ` <4D0B3DF2.5000100@wavecon.de>
     [not found]   ` <20101217115132.GG2754@reaktio.net>
     [not found]     ` <4D0B7E79.4010106@wavecon.de>
2010-12-20 20:18       ` [Xen-users] Hypervisor hangs on startup, 2.6.32-5-xen dom0 kernel panic Pasi Kärkkäinen
2010-12-20 20:20         ` Arno Toell
2010-12-21 13:13         ` Re: [Xen-users] " Ian Campbell
2010-12-23 11:13           ` Arno Toell [this message]
2010-12-27 15:28           ` Konrad Rzeszutek Wilk
2011-01-05 10:58             ` [Xen-devel] " Pasi Kärkkäinen
2011-01-05 16:05           ` Arno Toell
2011-01-05 16:16             ` Re: [Xen-users] " Ian Campbell
2011-01-11 16:38             ` Konrad Rzeszutek Wilk
2011-01-11 17:03               ` [Xen-devel] " Arno Toell
2011-01-11 17:20                 ` Konrad Rzeszutek Wilk
2011-01-11 18:39                   ` andrew thomas
2011-01-12 11:55                     ` Arno Toell
2011-01-13 12:11                     ` Arno Toell

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=4D132ED7.9050800@wavecon.de \
    --to=at@wavecon.de \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-users@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).