WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Xen Hypervisor start fail when system memory more than 6

To: Pasi Kärkkäinen <pasik@xxxxxx>
Subject: Re: [Xen-devel] Xen Hypervisor start fail when system memory more than 64GB, and free xen memory over 32 GB
From: benian <bestwish.happiness@xxxxxxxxx>
Date: Tue, 17 Aug 2010 16:23:23 +0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 17 Aug 2010 01:24:41 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=5PPu+ejtPU3nBhquQIWZGbGFdePSNERuwosnHK4vcXI=; b=R1/kXGTGq0ufuCZNYbMLVclvOujxdB2ojwfb/mtbEenS4O4P5UHuP8UUEu6i0tZnzk IV54Pst7P9c6DzYFMILM7Bg/Oj5qrNO0H3iunJXN19mt7Kn+2w6LJdlXmM0bxSiXaH0g PSF1ACTeRGN0F6AZMQYElwvp5IrAEcYxuaGhE=
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=UplAzP5IJBUOROBLfm2i6eQ+ecEuSZ6pVqY4Cx4eMPjO3avDWfHJT8sHLXMsJMxA7A rQclpSIva555jtdmjiXtYQfsFIKlxYFrD2/vI9AxpSKkDiNe4/sffOuWa9oYdlii7lEX JZFDFLPDQxvw43Elv3bItR0VuPj9Px0lCxRy0=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AANLkTi=RXgMQuHhkF0OHOEZTbf_-zpZEY8cj8qWLjAE_@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AANLkTinbHKTc+bFVNSjTi35RJt=7_YvjVZGK=jzdza+-@xxxxxxxxxxxxxx> <20100812113642.GO2804@xxxxxxxxxxx> <AANLkTike_HdzN=y9gwxCGLmVCE_0cH_1_U4FTKt82-Zo@xxxxxxxxxxxxxx> <20100816095555.GB2804@xxxxxxxxxxx> <20100816101522.GC2804@xxxxxxxxxxx> <AANLkTim43SHAX1A-JRXCC5DGZRbOA6xgfQ9MrhaaPrmo@xxxxxxxxxxxxxx> <20100816104713.GF2804@xxxxxxxxxxx> <AANLkTi=RXgMQuHhkF0OHOEZTbf_-zpZEY8cj8qWLjAE_@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Sorry, the attachment disappear in the last mail @@"
 
hi Pasi,
the attachments are the boot log i just dumped

my testing environment  is   72GB ram + Xen-4.0.1-rc4(rc6)+2.6.32-xendom0-kernel 
where i modified  CONFIG_XEN_MAX_DOMAIN_MEMORY=32 to =128 in xendom0-kernel

using xen-4.0.1-rc4, it can boot smoothly if the grub option dom0_mem=32G is removed
or modify to >41G 

Besides, xen-4.0.1-rc6 keep fail no matter what the grub setting is.


regards,
Ben

2010/8/16 Pasi Kärkkäinen <pasik@xxxxxx>

On Mon, Aug 16, 2010 at 06:41:03PM +0800, benian wrote:
>    hi Pasi,
>    I 've tried it before, but 4.0.1-rc6 and 4.0.1-rc5  also boot fail, but
>    different from the previous problem  error occur after XEN startup
>    äž«close to finish and all XEN message is cleared , Â these two version
>    hang on during  XEN is still starting , and the final message is "(XEN)
>    Dom0 Â has maximum 16 vcpus " Â
>    On the other hand, Â 4.0.1-rc4 and 4.0.0 boot smoothlyÂ
>    Moreover, i found that  4.0.1-rc4 and 4.0.0  takes much time on this
>    message  "(XEN) brought up 16cpu"  , where 4.0.1-rc6 and 4.0.1-rc5
>    just fleet.Â
>

Can you please post the full/complete bootlogs with Xen 4.0.1-rc6
so we can figure it out.. Thanks!

-- Pasi


>    Regards,
>    Ben
>    2010/8/16 Pasi KÀrkkÀinen <[1]pasik@xxxxxx>
>
>      On Mon, Aug 16, 2010 at 12:55:55PM +0300, Pasi KÀrkkÀinen wrote:
>      > On Mon, Aug 16, 2010 at 05:46:24PM +0800, benian wrote:
>      > > Â  Â Hi Pasi
>      > >   Â I 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?
>      > >
>      >
>      > Sounds like a bug yeah.. How does it fail in the dom0_mem=32G case?
>      What's the error?
>      >
>      > Can you please paste the full bootlog of the failing boot from a
>      serial console?
>      Oh, one more thing, could you also try with Xen 4.0.1-rc6?
>
>      Thanks!
>      -- Pasi
>
>      >
>      >
>      > > Â  Â Regards,
>      > > Â  Â Ben
>      > >   Â 2010/8/12 Pasi KÀrkkÀinen <[1][3]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
>      > > Â  Â  Â >
>      > > Â  Â  Â >
>      > >
>      > > Â  Â  Â How much memory does your dom0 have? ie. what's your
>      dom0_mem= option
>      > > Â  Â  Â for xen.gz in grub.conf.
>      > > Â  Â  Â 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:
>      > > Â  Â  Â [2][4]http://wiki.xensource.com/xenwiki/XenSerialConsole
>      > >
>      > > Â  Â  Â and more info about troubleshooting pvops dom0 kernels (also
>      an example
>      > > Â  Â  Â about serial console with pvops dom0):
>      > > Â  Â  Â [3][5]http://wiki.xensource.com/xenwiki/XenParavirtOps
>      > >
>      > > Â  Â  Â Those should help.
>      > > Â  Â  Â -- Pasi
>      > >
>      > > References
>      > >
>      > > Â  Â Visible links
>      > > Â  Â 1. mailto:[6]pasik@xxxxxx
>      > > Â  Â 2. [7]http://wiki.xensource.com/xenwiki/XenSerialConsole
>      > > Â  Â 3. [8]http://wiki.xensource.com/xenwiki/XenParavirtOps
>      >
>      > _______________________________________________
>      > Xen-devel mailing list
>      > [9]Xen-devel@xxxxxxxxxxxxxxxxxxx
>      > [10]http://lists.xensource.com/xen-devel
>
> References
>
>    Visible links
>    1. mailto:pasik@xxxxxx
>    2. http://wiki.xensource.com/xenwiki/XenSerialConsole
>    3. mailto:pasik@xxxxxx
>    4. http://wiki.xensource.com/xenwiki/XenSerialConsole
>    5. http://wiki.xensource.com/xenwiki/XenParavirtOps
>    6. mailto:pasik@xxxxxx
>    7. http://wiki.xensource.com/xenwiki/XenSerialConsole
>    8. http://wiki.xensource.com/xenwiki/XenParavirtOps
>    9. mailto:Xen-devel@xxxxxxxxxxxxxxxxxxx
>   10. http://lists.xensource.com/xen-devel


Attachment: ERROR-4.0.1-rc6.txt
Description: Text document

Attachment: ERROR-32G.txt
Description: Text document

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel