[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] Xen Hypervisor start fail when system memory more than 64GB
- To: Pasi Kärkkäinen <pasik@xxxxxx>
- From: benian <bestwish.happiness@xxxxxxxxx>
- Date: Mon, 16 Aug 2010 17:46:24 +0800
- Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
- Delivery-date: Mon, 16 Aug 2010 02:47:33 -0700
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=BUVFniQOHf2LvEiyb14RpngieM/4pO23TAzj7LL5jakLRaGIp0SEq0aGd8OXXXgTwE Ixo15brHL6qUb4ouFFrL7T4gJtAigVyG5uinLUqxiU8ubFi6dkivvI17TLshfeejLQGg 2GluXpPxT3SYoVE7cEKTxcWDtaBwNxIHvspdg=
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
Hi PasiI finally boot up successfully by simply modified the kernel config item CONFIG_XEN_MAX_DOMAIN_MEMORY=32 to CONFIG_XEN_MAX_DOMAIN_MEMORY=128 (just choose a random value >72 ),
then rebuild the kernel-2.6.32 , and everything is ok.
By the way, i 've done many test and i finally found that
if unallocated memory(total - dom0 ) >32GB, boot up would be failed in my environment.
for example, after I modified the kernel config, hypervisor boot normally and dom0 get 72GB.
If i add dom0_mem= 32G(unallocated 40G) to grub option, hypervisor boot fail again, and if dom0_mem= 41G(unallocated 31G), hypervisor boot normally again.
So , might it be a problem of xen-4.0 that unable to handle unallocated memory >32GB?
Regards, Ben
2010/8/12 Pasi Kärkkäinen <pasik@xxxxxx>
On Thu, Aug 12, 2010 at 03:08:25PM +0800, benian wrote:
>
>
> My environment is xen-4.0.0 + pvops2.6.32 kernel + fedora12
>
> I can run xen hypervisor smoothly when system memory below 64G
>
> But if I plug 4GB more memory to my server, XEN hypervisor start fail then
> crash and restart automatically.
>
> The final screen is some message about memory address which will not be
> displayed in normal process
>
>
>
> I read from XEN 4.0.0 features that Xen support 1 TB of RAM per host, so I
> am not sure what *s wrong with this situation.
>
>
>
> Any idea is appreciated and welcome
>
>
Have you tried different values? ie. 2GB, 4GB, 8GB?
Also setup a serial console so you can figure out if it's the Xen hypervisor or dom0 kernel crashing:
http://wiki.xensource.com/xenwiki/XenSerialConsole
and more info about troubleshooting pvops dom0 kernels (also an example about serial console with pvops dom0):
http://wiki.xensource.com/xenwiki/XenParavirtOps
Those should help.
-- Pasi
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
