-----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@xxxxxxxxxx
-----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-----
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel