benian
2010-Aug-12 06:39 UTC
[Xen-devel] Xen Hypervisor start fail when system memory more than 64GB
Hi everyone, 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 Thanks very much Ben _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
benian
2010-Aug-12 07:08 UTC
[Xen-devel] Xen Hypervisor start fail when system memory more than 64GB
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 Thanks very much Ben _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2010-Aug-12 11:36 UTC
Re: [Xen-devel] Xen Hypervisor start fail when system memory more than 64GB
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: 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@lists.xensource.com http://lists.xensource.com/xen-devel
benian
2010-Aug-16 09:46 UTC
Re: [Xen-devel] Xen Hypervisor start fail when system memory more than 64GB
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? Regards, Ben 2010/8/12 Pasi Kärkkäinen <pasik@iki.fi>> 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: > 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@lists.xensource.com http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2010-Aug-16 09:55 UTC
Re: [Xen-devel] Xen Hypervisor start fail when system memory more than 64GB, and free xen memory over 32 GB
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? http://wiki.xensource.com/xenwiki/XenSerialConsole -- Pasi> Regards, > Ben > 2010/8/12 Pasi Kärkkäinen <[1]pasik@iki.fi> > > 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]http://wiki.xensource.com/xenwiki/XenSerialConsole > > and more info about troubleshooting pvops dom0 kernels (also an example > about serial console with pvops dom0): > [3]http://wiki.xensource.com/xenwiki/XenParavirtOps > > Those should help. > -- Pasi > > References > > Visible links > 1. mailto:pasik@iki.fi > 2. http://wiki.xensource.com/xenwiki/XenSerialConsole > 3. http://wiki.xensource.com/xenwiki/XenParavirtOps_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2010-Aug-16 10:15 UTC
Re: [Xen-devel] Xen Hypervisor start fail when system memory more than 64GB, and free xen memory over 32 GB
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? > http://wiki.xensource.com/xenwiki/XenSerialConsole >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]pasik@iki.fi> > > > > 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]http://wiki.xensource.com/xenwiki/XenSerialConsole > > > > and more info about troubleshooting pvops dom0 kernels (also an example > > about serial console with pvops dom0): > > [3]http://wiki.xensource.com/xenwiki/XenParavirtOps > > > > Those should help. > > -- Pasi > > > > References > > > > Visible links > > 1. mailto:pasik@iki.fi > > 2. http://wiki.xensource.com/xenwiki/XenSerialConsole > > 3. http://wiki.xensource.com/xenwiki/XenParavirtOps > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2010-Aug-16 10:47 UTC
Re: [Xen-devel] Xen Hypervisor start fail when system memory more than 64GB, and free xen memory over 32 GB
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@iki.fi> > > 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? > > [2]http://wiki.xensource.com/xenwiki/XenSerialConsole > > > > 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@iki.fi> > > > > > >    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@iki.fi > > >   2. [7]http://wiki.xensource.com/xenwiki/XenSerialConsole > > >   3. [8]http://wiki.xensource.com/xenwiki/XenParavirtOps > > > > _______________________________________________ > > Xen-devel mailing list > > [9]Xen-devel@lists.xensource.com > > [10]http://lists.xensource.com/xen-devel > > References > > Visible links > 1. mailto:pasik@iki.fi > 2. http://wiki.xensource.com/xenwiki/XenSerialConsole > 3. mailto:pasik@iki.fi > 4. http://wiki.xensource.com/xenwiki/XenSerialConsole > 5. http://wiki.xensource.com/xenwiki/XenParavirtOps > 6. mailto:pasik@iki.fi > 7. http://wiki.xensource.com/xenwiki/XenSerialConsole > 8. http://wiki.xensource.com/xenwiki/XenParavirtOps > 9. mailto:Xen-devel@lists.xensource.com > 10. http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
benian
2010-Aug-17 08:19 UTC
Re: [Xen-devel] Xen Hypervisor start fail when system memory more than 64GB, and free xen memory over 32 GB
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@iki.fi>> 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@iki.fi> > > > > 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? > > > [2]http://wiki.xensource.com/xenwiki/XenSerialConsole > > > > > > > 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@iki.fi> > > > > > > > >    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@iki.fi > > > >   2. [7]http://wiki.xensource.com/xenwiki/XenSerialConsole > > > >   3. [8]http://wiki.xensource.com/xenwiki/XenParavirtOps > > > > > > _______________________________________________ > > > Xen-devel mailing list > > > [9]Xen-devel@lists.xensource.com > > > [10]http://lists.xensource.com/xen-devel > > > > References > > > > Visible links > > 1. mailto:pasik@iki.fi > > 2. http://wiki.xensource.com/xenwiki/XenSerialConsole > > 3. mailto:pasik@iki.fi > > 4. http://wiki.xensource.com/xenwiki/XenSerialConsole > > 5. http://wiki.xensource.com/xenwiki/XenParavirtOps > > 6. mailto:pasik@iki.fi > > 7. http://wiki.xensource.com/xenwiki/XenSerialConsole > > 8. http://wiki.xensource.com/xenwiki/XenParavirtOps > > 9. mailto:Xen-devel@lists.xensource.com > > 10. http://lists.xensource.com/xen-devel >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
benian
2010-Aug-17 08:23 UTC
Re: [Xen-devel] Xen Hypervisor start fail when system memory more than 64GB, and free xen memory over 32 GB
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@iki.fi> > > 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@iki.fi> >> > >> > 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? >> > > [2]http://wiki.xensource.com/xenwiki/XenSerialConsole >> > > >> > >> > 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@iki.fi> >> > > > >> > > >    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@iki.fi >> > > >   2. [7]http://wiki.xensource.com/xenwiki/XenSerialConsole >> > > >   3. [8]http://wiki.xensource.com/xenwiki/XenParavirtOps >> > > >> > > _______________________________________________ >> > > Xen-devel mailing list >> > > [9]Xen-devel@lists.xensource.com >> > > [10]http://lists.xensource.com/xen-devel >> > >> > References >> > >> > Visible links >> > 1. mailto:pasik@iki.fi >> > 2. http://wiki.xensource.com/xenwiki/XenSerialConsole >> > 3. mailto:pasik@iki.fi >> > 4. http://wiki.xensource.com/xenwiki/XenSerialConsole >> > 5. http://wiki.xensource.com/xenwiki/XenParavirtOps >> > 6. mailto:pasik@iki.fi >> > 7. http://wiki.xensource.com/xenwiki/XenSerialConsole >> > 8. http://wiki.xensource.com/xenwiki/XenParavirtOps >> > 9. mailto:Xen-devel@lists.xensource.com >> > 10. http://lists.xensource.com/xen-devel >> > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2010-Aug-17 08:34 UTC
Re: [Xen-devel] Xen Hypervisor start fail when system memory more than 64GB, and free xen memory over 32 GB
On Tue, Aug 17, 2010 at 04:23:23PM +0800, benian wrote:> 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ÂSo if you have dom0_mem=32G the boot fails (when using xen 4.0.1-rc4). When you don''t have dom0_mem at all, then the boot succeeds. I assume this is the the log called "ERROR-32G.txt". Based on the log it seems the problem is in dom0 kernel, not in Xen hypervisor. I notice you use old version of the dom0 kernel: 2.6.32.11-1.2.97.xendom0.fc12.x86_64. Can you try with a newer version? There have been many bugs fixed after that. You should try the latest version from xen.git xen/stable-2.6.32.x branch (2.6.32.19), instruction to get it here: http://wiki.xensource.com/xenwiki/XenParavirtOps . or the latest fedora rpms from: http://koji.fedoraproject.org/koji/taskinfo?taskID=2387081 http://repos.fedorapeople.org/repos/myoung/dom0-kernel/ I''d recommend using the xen/stable-2.6.32.x git repo, since it''s newer version.> Besides, xen-4.0.1-rc6 keep fail no matter what the grub setting is.Ok, so for 4.0.1-rc6 the boot always fails. We need to debug this more. 1) Please paste your grub.conf 2) Please try again by adding "sync_console console_to_ring" option to grub.conf to xen.gz line, and post the new bootlog with xen 4.0.1-rc6. Thanks! -- Pasi> regards, > Ben > 2010/8/16 Pasi KÀrkkÀinen <[1]pasik@iki.fi> > > 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][2]pasik@iki.fi> > > > >    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? > >    > [2][3]http://wiki.xensource.com/xenwiki/XenSerialConsole > >    > > > > >    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][4]pasik@iki.fi> > >    > > > >    > > Ã*  Ã*  Ã* 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][5]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][6]http://wiki.xensource.com/xenwiki/XenParavirtOps > >    > > > >    > > Ã*  Ã*  Ã* Those should help. > >    > > Ã*  Ã*  Ã* -- Pasi > >    > > > >    > > References > >    > > > >    > > Ã*  Ã* Visible links > >    > > Ã*  Ã* 1. mailto:[6][7]pasik@iki.fi > >    > > Ã*  Ã* 2. > [7][8]http://wiki.xensource.com/xenwiki/XenSerialConsole > >    > > Ã*  Ã* 3. > [8][9]http://wiki.xensource.com/xenwiki/XenParavirtOps > >    > > >    > _______________________________________________ > >    > Xen-devel mailing list > >    > [9][10]Xen-devel@lists.xensource.com > >    > [10][11]http://lists.xensource.com/xen-devel > > > > References > > > >   Visible links > >   1. mailto:[12]pasik@iki.fi > >   2. [13]http://wiki.xensource.com/xenwiki/XenSerialConsole > >   3. mailto:[14]pasik@iki.fi > >   4. [15]http://wiki.xensource.com/xenwiki/XenSerialConsole > >   5. [16]http://wiki.xensource.com/xenwiki/XenParavirtOps > >   6. mailto:[17]pasik@iki.fi > >   7. [18]http://wiki.xensource.com/xenwiki/XenSerialConsole > >   8. [19]http://wiki.xensource.com/xenwiki/XenParavirtOps > >   9. mailto:[20]Xen-devel@lists.xensource.com > >  10. [21]http://lists.xensource.com/xen-devel > > References > > Visible links > 1. mailto:pasik@iki.fi > 2. mailto:pasik@iki.fi > 3. http://wiki.xensource.com/xenwiki/XenSerialConsole > 4. mailto:pasik@iki.fi > 5. http://wiki.xensource.com/xenwiki/XenSerialConsole > 6. http://wiki.xensource.com/xenwiki/XenParavirtOps > 7. mailto:pasik@iki.fi > 8. http://wiki.xensource.com/xenwiki/XenSerialConsole > 9. http://wiki.xensource.com/xenwiki/XenParavirtOps > 10. mailto:Xen-devel@lists.xensource.com > 11. http://lists.xensource.com/xen-devel > 12. mailto:pasik@iki.fi > 13. http://wiki.xensource.com/xenwiki/XenSerialConsole > 14. mailto:pasik@iki.fi > 15. http://wiki.xensource.com/xenwiki/XenSerialConsole > 16. http://wiki.xensource.com/xenwiki/XenParavirtOps > 17. mailto:pasik@iki.fi > 18. http://wiki.xensource.com/xenwiki/XenSerialConsole > 19. http://wiki.xensource.com/xenwiki/XenParavirtOps > 20. mailto:Xen-devel@lists.xensource.com > 21. http://lists.xensource.com/xen-devel> __ __ _ _ ___ _ __ > \ \/ /___ _ __ | || | / _ \ / | _ __ ___ / /_ _ __ _ __ ___ > \ // _ \ ''_ \ | || |_| | | || |__| ''__/ __| ''_ \ __| ''_ \| ''__/ _ \ > / \ __/ | | | |__ _| |_| || |__| | | (__| (_) |__| |_) | | | __/ > /_/\_\___|_| |_| |_|(_)___(_)_| |_| \___|\___/ | .__/|_| \___| > |_| > (XEN) Xen version 4.0.1-rc6-pre (root@) (gcc version 4.4.4 20100630 (Red Hat 4.4.4-10) (GCC) ) Tue Aug 17 14:38:30 CST 2010 > (XEN) Latest ChangeSet: Wed Aug 11 16:44:03 2010 +0100 21307:8e8dd38374e9 > (XEN) Bootloader: GNU GRUB 0.97 > (XEN) Command line: loglvl=all guest_loglvl=all com1=38400,8n1 console=com1 > (XEN) Video information: > (XEN) VGA is text mode 80x25, font 8x16 > (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds > (XEN) Disc information: > (XEN) Found 4 MBR signatures > (XEN) Found 4 EDD information structures > (XEN) Xen-e820 RAM map: > (XEN) 0000000000000000 - 00000000000a0000 (usable) > (XEN) 0000000000100000 - 00000000bf679000 (usable) > (XEN) 00000000bf679000 - 00000000bf68f000 (reserved) > (XEN) 00000000bf68f000 - 00000000bf6ce000 (ACPI data) > (XEN) 00000000bf6ce000 - 00000000c0000000 (reserved) > (XEN) 00000000e0000000 - 00000000f0000000 (reserved) > (XEN) 00000000fe000000 - 0000000100000000 (reserved) > (XEN) 0000000100000000 - 0000001240000000 (usable) > (XEN) ACPI: RSDP 000F0A90, 0024 (r2 DELL ) > (XEN) ACPI: XSDT 000F0B94, 009C (r1 DELL PE_SC3 1 DELL 1) > (XEN) ACPI: FACP BF6B3F9C, 00F4 (r3 DELL PE_SC3 1 DELL 1) > (XEN) ACPI: DSDT BF68F000, 3D5A (r1 DELL PE_SC3 1 INTL 20050624) > (XEN) ACPI: FACS BF6B6000, 0040 > (XEN) ACPI: APIC BF6B3478, 015E (r1 DELL PE_SC3 1 DELL 1) > (XEN) ACPI: SPCR BF6B35D8, 0050 (r1 DELL PE_SC3 1 DELL 1) > (XEN) ACPI: HPET BF6B362C, 0038 (r1 DELL PE_SC3 1 DELL 1) > (XEN) ACPI: DMAR BF6B3668, 01C0 (r1 DELL PE_SC3 1 DELL 1) > (XEN) ACPI: MCFG BF6B38C4, 003C (r1 DELL PE_SC3 1 DELL 1) > (XEN) ACPI: WD__ BF6B3904, 0134 (r1 DELL PE_SC3 1 DELL 1) > (XEN) ACPI: SLIC BF6B3A3C, 0024 (r1 DELL PE_SC3 1 DELL 1) > (XEN) ACPI: ERST BF692EDC, 0270 (r1 DELL PE_SC3 1 DELL 1) > (XEN) ACPI: HEST BF69314C, 03A8 (r1 DELL PE_SC3 1 DELL 1) > (XEN) ACPI: BERT BF692D5C, 0030 (r1 DELL PE_SC3 1 DELL 1) > (XEN) ACPI: EINJ BF692D8C, 0150 (r1 DELL PE_SC3 1 DELL 1) > (XEN) ACPI: SRAT BF6B3BC0, 0370 (r1 DELL PE_SC3 1 DELL 1) > (XEN) ACPI: TCPA BF6B3F34, 0064 (r2 DELL PE_SC3 1 DELL 1) > (XEN) ACPI: SSDT BF6B7000, 43F4 (r1 INTEL PPM RCM 80000001 INTL 20061109) > (XEN) System RAM: 73718MB (75487332kB) > (XEN) SRAT: PXM 1 -> APIC 32 -> Node 0 > (XEN) SRAT: PXM 2 -> APIC 0 -> Node 1 > (XEN) SRAT: PXM 1 -> APIC 34 -> Node 0 > (XEN) SRAT: PXM 2 -> APIC 2 -> Node 1 > (XEN) SRAT: PXM 1 -> APIC 50 -> Node 0 > (XEN) SRAT: PXM 2 -> APIC 18 -> Node 1 > (XEN) SRAT: PXM 1 -> APIC 52 -> Node 0 > (XEN) SRAT: PXM 2 -> APIC 20 -> Node 1 > (XEN) SRAT: PXM 1 -> APIC 33 -> Node 0 > (XEN) SRAT: PXM 2 -> APIC 1 -> Node 1 > (XEN) SRAT: PXM 1 -> APIC 35 -> Node 0 > (XEN) SRAT: PXM 2 -> APIC 3 -> Node 1 > (XEN) SRAT: PXM 1 -> APIC 51 -> Node 0 > (XEN) SRAT: PXM 2 -> APIC 19 -> Node 1 > (XEN) SRAT: PXM 1 -> APIC 53 -> Node 0 > (XEN) SRAT: PXM 2 -> APIC 21 -> Node 1 > (XEN) SRAT: Node 1 PXM 2 0-c0000000 > (XEN) SRAT: Node 1 PXM 2 100000000-940000000 > (XEN) SRAT: Node 0 PXM 1 940000000-1240000000 > (XEN) NUMA: Allocated memnodemap from 123fdfe000 - 123fdff000 > (XEN) NUMA: Using 18 for the hash shift. > (XEN) Domain heap initialised DMA width 32 bits > (XEN) found SMP MP-table at 000fe710 > (XEN) DMI 2.6 present. > (XEN) Using APIC driver default > (XEN) ACPI: PM-Timer IO Port: 0x808 > (XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[804,0], pm1x_evt[800,0] > (XEN) ACPI: wakeup_vec[bf6b600c], vec_size[20] > (XEN) ACPI: Local APIC address 0xfee00000 > (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x20] enabled) > (XEN) Processor #32 6:12 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x00] enabled) > (XEN) Processor #0 6:12 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x22] enabled) > (XEN) Processor #34 6:12 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x02] enabled) > (XEN) Processor #2 6:12 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x32] enabled) > (XEN) Processor #50 6:12 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x12] enabled) > (XEN) Processor #18 6:12 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x34] enabled) > (XEN) Processor #52 6:12 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x14] enabled) > (XEN) Processor #20 6:12 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x09] lapic_id[0x21] enabled) > (XEN) Processor #33 6:12 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x01] enabled) > (XEN) Processor #1 6:12 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x23] enabled) > (XEN) Processor #35 6:12 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x03] enabled) > (XEN) Processor #3 6:12 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x33] enabled) > (XEN) Processor #51 6:12 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x13] enabled) > (XEN) Processor #19 6:12 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x35] enabled) > (XEN) Processor #53 6:12 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x10] lapic_id[0x15] enabled) > (XEN) Processor #21 6:12 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x11] lapic_id[0x30] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x12] lapic_id[0x31] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x13] lapic_id[0x32] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x14] lapic_id[0x33] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x15] lapic_id[0x34] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x16] lapic_id[0x35] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x17] lapic_id[0x36] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x18] lapic_id[0x37] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x19] lapic_id[0x38] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x39] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x3a] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x1c] lapic_id[0x3b] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x1d] lapic_id[0x3c] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x1e] lapic_id[0x3d] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x1f] lapic_id[0x3e] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x20] lapic_id[0x3f] disabled) > (XEN) ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1]) > (XEN) Overriding APIC driver with bigsmp > (XEN) ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0]) > (XEN) IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23 > (XEN) ACPI: IOAPIC (id[0x01] address[0xfec80000] gsi_base[32]) > (XEN) IOAPIC[1]: apic_id 1, version 32, address 0xfec80000, GSI 32-55 > (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) > (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) > (XEN) ACPI: IRQ0 used by override. > (XEN) ACPI: IRQ2 used by override. > (XEN) ACPI: IRQ9 used by override. > (XEN) Enabling APIC mode: Phys. Using 2 I/O APICs > (XEN) ACPI: HPET id: 0x8086a301 base: 0xfed00000 > (XEN) PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255 > (XEN) PCI: MCFG area at e0000000 reserved in E820 > (XEN) Using ACPI (MADT) for SMP configuration information > (XEN) Using scheduler: SMP Credit Scheduler (credit) > (XEN) Detected 2394.061 MHz processor. > (XEN) Initing memory sharing. > (XEN) VMX: Supported advanced features: > (XEN) - APIC MMIO access virtualisation > (XEN) - APIC TPR shadow > (XEN) - Extended Page Tables (EPT) > (XEN) - Virtual-Processor Identifiers (VPID) > (XEN) - Virtual NMI > (XEN) - MSR direct-access bitmap > (XEN) - Unrestricted Guest > (XEN) EPT supports 2MB super page. > (XEN) HVM: ASIDs enabled. > (XEN) HVM: VMX enabled > (XEN) HVM: Hardware Assisted Paging detected. > (XEN) Intel machine check reporting enabled > (XEN) Intel VT-d Snoop Control supported. > (XEN) Intel VT-d DMA Passthrough not supported. > (XEN) Intel VT-d Queued Invalidation supported. > (XEN) Intel VT-d Interrupt Remapping supported. > (XEN) I/O virtualisation enabled > (XEN) - Dom0 mode: Relaxed > (XEN) Enabled directed EOI with ioapic_ack_old on! > (XEN) Total of 16 processors activated. > (XEN) ENABLING IO-APIC IRQs > (XEN) -> Using old ACK method > (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1 > (XEN) TSC is reliable, synchronization unnecessary > (XEN) Platform timer is 14.318MHz HPET > ?(XEN) Allocated console ring of 128 KiB. > (XEN) microcode.c:73:d32767 microcode: CPU1 resumed > (XEN) microcode.c:73:d32767 microcode: CPU2 resumed > (XEN) microcode.c:73:d32767 microcode: CPU3 resumed > (XEN) microcode.c:73:d32767 microcode: CPU4 resumed > (XEN) microcode.c:73:d32767 microcode: CPU5 resumed > (XEN) microcode.c:73:d32767 microcode: CPU6 resumed > (XEN) microcode.c:73:d32767 microcode: CPU7 resumed > (XEN) microcode.c:73:d32767 microcode: CPU8 resumed > (XEN) microcode.c:73:d32767 microcode: CPU9 resumed > (XEN) microcode.c:73:d32767 microcode: CPU10 resumed > (XEN) microcode.c:73:d32767 microcode: CPU11 resumed > (XEN) microcode.c:73:d32767 microcode: CPU12 resumed > (XEN) microcode.c:73:d32767 microcode: CPU13 resumed > (XEN) microcode.c:73:d32767 microcode: CPU14 resumed > (XEN) Brought up 16 CPUs > (XEN) microcode.c:73:d32767 microcode: CPU15 resumed > (XEN) Turbo Mode detected! > (XEN) ACPI sleep modes: S3 > (XEN) mcheck_poll: Machine check polling timer started. > (XEN) *** LOADING DOMAIN 0 *** > (XEN) Xen kernel: 64-bit, lsb, compat32 > (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x1b4b000 > (XEN) PHYSICAL MEMORY ARRANGEMENT: > (XEN) Dom0 alloc.: 0000001200000000->0000001210000000 (18568714 pages to be allocated) > (XEN) VIRTUAL MEMORY ARRANGEMENT: > (XEN) Loaded kernel: ffffffff81000000->ffffffff81b4b000 > (XEN) Init. ramdisk: ffffffff81b4b000->ffffffff83a2a400 > (XEN) Phys-Mach map: ffffffff83a2b000->ffffffff8c856050 > (XEN) Start info: ffffffff8c857000->ffffffff8c8574b4 > (XEN) Page tables: ffffffff8c858000->ffffffff8c8c1000 > (XEN) Boot stack: ffffffff8c8c1000->ffffffff8c8c2000 > (XEN) TOTAL: ffffffff80000000->ffffffff8cc00000 > (XEN) ENTRY ADDRESS: ffffffff81882200 > (XEN) Dom0 has maximum 16 VCPUs >> > > __ __ _ _ ___ _ _ _ > \ \/ /___ _ __ | || | / _ \ / | _ __ ___| || | _ __ _ __ ___ > \ // _ \ ''_ \ | || |_| | | || |__| ''__/ __| || |_ __| ''_ \| ''__/ _ \ > / \ __/ | | | |__ _| |_| || |__| | | (__|__ _|__| |_) | | | __/ > /_/\_\___|_| |_| |_|(_)___(_)_| |_| \___| |_| | .__/|_| \___| > |_| > (XEN) Xen version 4.0.1-rc4-pre (root@) (gcc version 4.4.4 20100630 (Red Hat 4.4.4-10) (GCC) ) Wed Jul 14 13:50:23 CST 2010 > (XEN) Latest ChangeSet: Fri Jul 09 12:44:53 2010 +0100 21263:57859775f88f > (XEN) Command line: dom0_mem=32G loglvl=all guest_loglvl=all com1=38400,8n1 console=com1 > (XEN) Video information: > (XEN) VGA is text mode 80x25, font 8x16 > (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds > (XEN) Disc information: > (XEN) Found 4 MBR signatures > (XEN) Found 4 EDD information structures > (XEN) Xen-e820 RAM map: > (XEN) 0000000000000000 - 00000000000a0000 (usable) > (XEN) 0000000000100000 - 00000000bf679000 (usable) > (XEN) 00000000bf679000 - 00000000bf68f000 (reserved) > (XEN) 00000000bf68f000 - 00000000bf6ce000 (ACPI data) > (XEN) 00000000bf6ce000 - 00000000c0000000 (reserved) > (XEN) 00000000e0000000 - 00000000f0000000 (reserved) > (XEN) 00000000fe000000 - 0000000100000000 (reserved) > (XEN) 0000000100000000 - 0000001240000000 (usable) > (XEN) ACPI: RSDP 000F0A90, 0024 (r2 DELL ) > (XEN) ACPI: XSDT 000F0B94, 009C (r1 DELL PE_SC3 1 DELL 1) > (XEN) ACPI: FACP BF6B3F9C, 00F4 (r3 DELL PE_SC3 1 DELL 1) > (XEN) ACPI: DSDT BF68F000, 3D5A (r1 DELL PE_SC3 1 INTL 20050624) > (XEN) ACPI: FACS BF6B6000, 0040 > (XEN) ACPI: APIC BF6B3478, 015E (r1 DELL PE_SC3 1 DELL 1) > (XEN) ACPI: SPCR BF6B35D8, 0050 (r1 DELL PE_SC3 1 DELL 1) > (XEN) ACPI: HPET BF6B362C, 0038 (r1 DELL PE_SC3 1 DELL 1) > (XEN) ACPI: DMAR BF6B3668, 01C0 (r1 DELL PE_SC3 1 DELL 1) > (XEN) ACPI: MCFG BF6B38C4, 003C (r1 DELL PE_SC3 1 DELL 1) > (XEN) ACPI: WD__ BF6B3904, 0134 (r1 DELL PE_SC3 1 DELL 1) > (XEN) ACPI: SLIC BF6B3A3C, 0024 (r1 DELL PE_SC3 1 DELL 1) > (XEN) ACPI: ERST BF692EDC, 0270 (r1 DELL PE_SC3 1 DELL 1) > (XEN) ACPI: HEST BF69314C, 03A8 (r1 DELL PE_SC3 1 DELL 1) > (XEN) ACPI: BERT BF692D5C, 0030 (r1 DELL PE_SC3 1 DELL 1) > (XEN) ACPI: EINJ BF692D8C, 0150 (r1 DELL PE_SC3 1 DELL 1) > (XEN) ACPI: SRAT BF6B3BC0, 0370 (r1 DELL PE_SC3 1 DELL 1) > (XEN) ACPI: TCPA BF6B3F34, 0064 (r2 DELL PE_SC3 1 DELL 1) > (XEN) ACPI: SSDT BF6B7000, 43F4 (r1 INTEL PPM RCM 80000001 INTL 20061109) > (XEN) System RAM: 73718MB (75487332kB) > (XEN) SRAT: PXM 1 -> APIC 32 -> Node 0 > (XEN) SRAT: PXM 2 -> APIC 0 -> Node 1 > (XEN) SRAT: PXM 1 -> APIC 34 -> Node 0 > (XEN) SRAT: PXM 2 -> APIC 2 -> Node 1 > (XEN) SRAT: PXM 1 -> APIC 50 -> Node 0 > (XEN) SRAT: PXM 2 -> APIC 18 -> Node 1 > (XEN) SRAT: PXM 1 -> APIC 52 -> Node 0 > (XEN) SRAT: PXM 2 -> APIC 20 -> Node 1 > (XEN) SRAT: PXM 1 -> APIC 33 -> Node 0 > (XEN) SRAT: PXM 2 -> APIC 1 -> Node 1 > (XEN) SRAT: PXM 1 -> APIC 35 -> Node 0 > (XEN) SRAT: PXM 2 -> APIC 3 -> Node 1 > (XEN) SRAT: PXM 1 -> APIC 51 -> Node 0 > (XEN) SRAT: PXM 2 -> APIC 19 -> Node 1 > (XEN) SRAT: PXM 1 -> APIC 53 -> Node 0 > (XEN) SRAT: PXM 2 -> APIC 21 -> Node 1 > (XEN) SRAT: Node 1 PXM 2 0-c0000000 > (XEN) SRAT: Node 1 PXM 2 100000000-940000000 > (XEN) SRAT: Node 0 PXM 1 940000000-1240000000 > (XEN) NUMA: Allocated memnodemap from 123fdfe000 - 123fdff000 > (XEN) NUMA: Using 18 for the hash shift. > (XEN) Domain heap initialised DMA width 32 bits > (XEN) found SMP MP-table at 000fe710 > (XEN) DMI 2.6 present. > (XEN) Using APIC driver default > (XEN) ACPI: PM-Timer IO Port: 0x808 > (XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[804,0], pm1x_evt[800,0] > (XEN) ACPI: wakeup_vec[bf6b600c], vec_size[20] > (XEN) ACPI: Local APIC address 0xfee00000 > (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x20] enabled) > (XEN) Processor #32 6:12 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x00] enabled) > (XEN) Processor #0 6:12 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x22] enabled) > (XEN) Processor #34 6:12 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x02] enabled) > (XEN) Processor #2 6:12 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x32] enabled) > (XEN) Processor #50 6:12 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x12] enabled) > (XEN) Processor #18 6:12 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x34] enabled) > (XEN) Processor #52 6:12 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x14] enabled) > (XEN) Processor #20 6:12 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x09] lapic_id[0x21] enabled) > (XEN) Processor #33 6:12 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x01] enabled) > (XEN) Processor #1 6:12 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x23] enabled) > (XEN) Processor #35 6:12 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x03] enabled) > (XEN) Processor #3 6:12 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x33] enabled) > (XEN) Processor #51 6:12 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x13] enabled) > (XEN) Processor #19 6:12 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x35] enabled) > (XEN) Processor #53 6:12 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x10] lapic_id[0x15] enabled) > (XEN) Processor #21 6:12 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x11] lapic_id[0x30] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x12] lapic_id[0x31] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x13] lapic_id[0x32] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x14] lapic_id[0x33] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x15] lapic_id[0x34] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x16] lapic_id[0x35] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x17] lapic_id[0x36] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x18] lapic_id[0x37] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x19] lapic_id[0x38] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x39] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x3a] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x1c] lapic_id[0x3b] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x1d] lapic_id[0x3c] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x1e] lapic_id[0x3d] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x1f] lapic_id[0x3e] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x20] lapic_id[0x3f] disabled) > (XEN) ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1]) > (XEN) Overriding APIC driver with bigsmp > (XEN) ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0]) > (XEN) IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23 > (XEN) ACPI: IOAPIC (id[0x01] address[0xfec80000] gsi_base[32]) > (XEN) IOAPIC[1]: apic_id 1, version 32, address 0xfec80000, GSI 32-55 > (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) > (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) > (XEN) ACPI: IRQ0 used by override. > (XEN) ACPI: IRQ2 used by override. > (XEN) ACPI: IRQ9 used by override. > (XEN) Enabling APIC mode: Phys. Using 2 I/O APICs > (XEN) ACPI: HPET id: 0x8086a301 base: 0xfed00000 > (XEN) PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255 > (XEN) PCI: MCFG area at e0000000 reserved in E820 > (XEN) Using ACPI (MADT) for SMP configuration information > (XEN) Using scheduler: SMP Credit Scheduler (credit) > (XEN) Detected 2394.049 MHz processor. > (XEN) Initing memory sharing. > (XEN) VMX: Supported advanced features: > (XEN) - APIC MMIO access virtualisation > (XEN) - APIC TPR shadow > (XEN) - Extended Page Tables (EPT) > (XEN) - Virtual-Processor Identifiers (VPID) > (XEN) - Virtual NMI > (XEN) - MSR direct-access bitmap > (XEN) - Unrestricted Guest > (XEN) EPT supports 2MB super page. > (XEN) HVM: ASIDs enabled. > (XEN) HVM: VMX enabled > (XEN) HVM: Hardware Assisted Paging detected. > (XEN) Intel machine check reporting enabled > (XEN) Intel VT-d Snoop Control supported. > (XEN) Intel VT-d DMA Passthrough not supported. > (XEN) Intel VT-d Queued Invalidation supported. > (XEN) Intel VT-d Interrupt Remapping supported. > (XEN) I/O virtualisation enabled > (XEN) I/O virtualisation for PV guests disabled > (XEN) Enabled directed EOI with ioapic_ack_old on! > (XEN) Total of 16 processors activated. > (XEN) ENABLING IO-APIC IRQs > (XEN) -> Using old ACK method > (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1 > (XEN) TSC is reliable, synchronization unnecessary > (XEN) Platform timer is 14.318MHz HPET > ?(XEN) Allocated console ring of 128 KiB. > (XEN) microcode.c:73:d32767 microcode: CPU1 resumed > (XEN) microcode.c:73:d32767 microcode: CPU2 resumed > (XEN) microcode.c:73:d32767 microcode: CPU3 resumed > (XEN) microcode.c:73:d32767 microcode: CPU4 resumed > (XEN) microcode.c:73:d32767 microcode: CPU5 resumed > (XEN) microcode.c:73:d32767 microcode: CPU6 resumed > (XEN) microcode.c:73:d32767 microcode: CPU7 resumed > (XEN) microcode.c:73:d32767 microcode: CPU8 resumed > (XEN) microcode.c:73:d32767 microcode: CPU9 resumed > (XEN) microcode.c:73:d32767 microcode: CPU10 resumed > (XEN) microcode.c:73:d32767 microcode: CPU11 resumed > (XEN) microcode.c:73:d32767 microcode: CPU12 resumed > (XEN) microcode.c:73:d32767 microcode: CPU13 resumed > (XEN) microcode.c:73:d32767 microcode: CPU14 resumed > (XEN) Brought up 16 CPUs > (XEN) microcode.c:73:d32767 microcode: CPU15 resumed > (XEN) Turbo Mode detected! > (XEN) ACPI sleep modes: S3 > (XEN) mcheck_poll: Machine check polling timer started. > (XEN) *** LOADING DOMAIN 0 *** > (XEN) Xen kernel: 64-bit, lsb, compat32 > (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x1b4b000 > (XEN) PHYSICAL MEMORY ARRANGEMENT: > (XEN) Dom0 alloc.: 0000001200000000->0000001208000000 (8355840 pages to be allocated) > (XEN) VIRTUAL MEMORY ARRANGEMENT: > (XEN) Loaded kernel: ffffffff81000000->ffffffff81b4b000 > (XEN) Init. ramdisk: ffffffff81b4b000->ffffffff83a2a400 > (XEN) Phys-Mach map: ffffffff83a2b000->ffffffff87a2b000 > (XEN) Start info: ffffffff87a2b000->ffffffff87a2b4b4 > (XEN) Page tables: ffffffff87a2c000->ffffffff87a6d000 > (XEN) Boot stack: ffffffff87a6d000->ffffffff87a6e000 > (XEN) TOTAL: ffffffff80000000->ffffffff87c00000 > (XEN) ENTRY ADDRESS: ffffffff81882200 > (XEN) Dom0 has maximum 16 VCPUs > (XEN) Scrubbing Free RAM: ................................................................................................................................................................................................................................................................................................................................................................................................................done. > (XEN) trace.c:89:d32767 calc_tinfo_first_offset: NR_CPUs 128, offset_in_bytes 258, t_info_first_offset 65 > (XEN) Xen trace buffers: disabled > (XEN) Std. Loglevel: All > (XEN) Guest Loglevel: All > (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input to Xen) > (XEN) Freed 184kB init memory. > mapping kernel into physical memory > Xen: setup ISA identity maps > about to get started... > Initializing cgroup subsys cpuset > Initializing cgroup subsys cpu > Linux version 2.6.32.11-1.2.97.xendom0.fc12.x86_64 (benian@R710) (gcc version 4.4.4 20100630 (Red Hat 4.4.4-10) (GCC) ) #1 SMP Fri Aug 13 14:11:37 CST 2010 > Command line: ro root=UUID=23dec242-9269-4f57-8433-2e7b5c468cf1 LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us console=hvc0 earlyprintk=xen > KERNEL supported cpus: > Intel GenuineIntel > AMD AuthenticAMD > Centaur CentaurHauls > xen_release_chunk: looking at area pfn c0000-e0000: 131072 pages freed > xen_release_chunk: looking at area pfn f0000-fe000: 57344 pages freed > released 188416 pages of unused memory > BIOS-provided physical RAM map: > Xen: 0000000000000000 - 00000000000a0000 (usable) > Xen: 00000000000a0000 - 0000000000100000 (reserved) > Xen: 0000000000100000 - 00000000bf679000 (usable) > Xen: 00000000bf679000 - 00000000bf68f000 (reserved) > Xen: 00000000bf68f000 - 00000000bf6ce000 (ACPI data) > Xen: 00000000bf6ce000 - 00000000c0000000 (reserved) > Xen: 00000000e0000000 - 00000000f0000000 (reserved) > Xen: 00000000fe000000 - 0000000100000000 (reserved) > Xen: 0000000100000000 - 0000000800000000 (usable) > bootconsole [xenboot0] enabled > DMI 2.6 present. > last_pfn = 0x800000 max_arch_pfn = 0x400000000 > x86 PAT enabled: cpu 0, old 0x50100070406, new 0x7010600070106 > last_pfn = 0xbf679 max_arch_pfn = 0x400000000 > init_memory_mapping: 0000000000000000-00000000bf679000 > init_memory_mapping: 0000000100000000-0000000800000000 > RAMDISK: 01b4b000 - 03a2a400 > ACPI: RSDP 00000000000f0a90 00024 (v02 DELL ) > ACPI: XSDT 00000000000f0b94 0009C (v01 DELL PE_SC3 00000001 DELL 00000001) > ACPI: FACP 00000000bf6b3f9c 000F4 (v03 DELL PE_SC3 00000001 DELL 00000001) > ACPI: DSDT 00000000bf68f000 03D5A (v01 DELL PE_SC3 00000001 INTL 20050624) > ACPI: FACS 00000000bf6b6000 00040 > ACPI: APIC 00000000bf6b3478 0015E (v01 DELL PE_SC3 00000001 DELL 00000001) > ACPI: SPCR 00000000bf6b35d8 00050 (v01 DELL PE_SC3 00000001 DELL 00000001) > ACPI: HPET 00000000bf6b362c 00038 (v01 DELL PE_SC3 00000001 DELL 00000001) > ACPI: 00000000bf6b3668 001C0 (v01 DELL PE_SC3 00000001 DELL 00000001) > ACPI: MCFG 00000000bf6b38c4 0003C (v01 DELL PE_SC3 00000001 DELL 00000001) > ACPI: WD__ 00000000bf6b3904 00134 (v01 DELL PE_SC3 00000001 DELL 00000001) > ACPI: SLIC 00000000bf6b3a3c 00024 (v01 DELL PE_SC3 00000001 DELL 00000001) > ACPI: ERST 00000000bf692edc 00270 (v01 DELL PE_SC3 00000001 DELL 00000001) > ACPI: HEST 00000000bf69314c 003A8 (v01 DELL PE_SC3 00000001 DELL 00000001) > ACPI: BERT 00000000bf692d5c 00030 (v01 DELL PE_SC3 00000001 DELL 00000001) > ACPI: EINJ 00000000bf692d8c 00150 (v01 DELL PE_SC3 00000001 DELL 00000001) > ACPI: SRAT 00000000bf6b3bc0 00370 (v01 DELL PE_SC3 00000001 DELL 00000001) > ACPI: TCPA 00000000bf6b3f34 00064 (v02 DELL PE_SC3 00000001 DELL 00000001) > ACPI: SSDT 00000000bf6b7000 043F4 (v01 INTEL PPM RCM 80000001 INTL 20061109) > SRAT: PXM 1 -> APIC 32 -> Node 0 > SRAT: PXM 2 -> APIC 0 -> Node 1 > SRAT: PXM 1 -> APIC 34 -> Node 0 > SRAT: PXM 2 -> APIC 2 -> Node 1 > SRAT: PXM 1 -> APIC 50 -> Node 0 > SRAT: PXM 2 -> APIC 18 -> Node 1 > SRAT: PXM 1 -> APIC 52 -> Node 0 > SRAT: PXM 2 -> APIC 20 -> Node 1 > SRAT: PXM 1 -> APIC 33 -> Node 0 > SRAT: PXM 2 -> APIC 1 -> Node 1 > SRAT: PXM 1 -> APIC 35 -> Node 0 > SRAT: PXM 2 -> APIC 3 -> Node 1 > SRAT: PXM 1 -> APIC 51 -> Node 0 > SRAT: PXM 2 -> APIC 19 -> Node 1 > SRAT: PXM 1 -> APIC 53 -> Node 0 > SRAT: PXM 2 -> APIC 21 -> Node 1 > SRAT: Node 1 PXM 2 0-c0000000 > SRAT: Node 1 PXM 2 100000000-940000000 > SRAT: Node 0 PXM 1 940000000-1240000000 > Bootmem setup node 1 0000000000000000-0000000800000000 > NODE_DATA [00000000000080c0 - 000000000001e0bf] > bootmap [00000000006bc000 - 00000000007bbfff] pages 100 > (10 early reservations) ==> bootmem [0000000000 - 0800000000] > #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000] > #1 [0007a2c000 - 0007a6d000] XEN PAGETABLES ==> [0007a2c000 - 0007a6d000] > #2 [0000006000 - 0000008000] TRAMPOLINE ==> [0000006000 - 0000008000] > #3 [0001000000 - 0001b2a0e8] TEXT DATA BSS ==> [0001000000 - 0001b2a0e8] > #4 [0001b4b000 - 0003a2a400] RAMDISK ==> [0001b4b000 - 0003a2a400] > #5 [0003a2b000 - 0007a2c000] XEN START INFO ==> [0003a2b000 - 0007a2c000] > #6 [0001b2b000 - 0001b2b4fd] BRK ==> [0001b2b000 - 0001b2b4fd] > #7 [0000100000 - 00006bc000] PGTABLE ==> [0000100000 - 00006bc000] > #8 [0007a6d000 - 000b289000] PGTABLE ==> [0007a6d000 - 000b289000] > #9 [0000008000 - 00000080c0] MEMNODEMAP ==> [0000008000 - 00000080c0] > found SMP MP-table at [ffff8800000fe710] fe710 > Zone PFN ranges: > DMA 0x00000000 -> 0x00001000 > DMA32 0x00001000 -> 0x00100000 > Normal 0x00100000 -> 0x00800000 > Movable zone start PFN for each node > early_node_map[3] active PFN ranges > 1: 0x00000000 -> 0x000000a0 > 1: 0x00000100 -> 0x000bf679 > 1: 0x00100000 -> 0x00800000 > ACPI: PM-Timer IO Port: 0x808 > ACPI: LAPIC (acpi_id[0x01] lapic_id[0x20] enabled) > ACPI: LAPIC (acpi_id[0x02] lapic_id[0x00] enabled) > ACPI: LAPIC (acpi_id[0x03] lapic_id[0x22] enabled) > ACPI: LAPIC (acpi_id[0x04] lapic_id[0x02] enabled) > ACPI: LAPIC (acpi_id[0x05] lapic_id[0x32] enabled) > ACPI: LAPIC (acpi_id[0x06] lapic_id[0x12] enabled) > ACPI: LAPIC (acpi_id[0x07] lapic_id[0x34] enabled) > ACPI: LAPIC (acpi_id[0x08] lapic_id[0x14] enabled) > ACPI: LAPIC (acpi_id[0x09] lapic_id[0x21] enabled) > ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x01] enabled) > ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x23] enabled) > ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x03] enabled) > ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x33] enabled) > ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x13] enabled) > ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x35] enabled) > ACPI: LAPIC (acpi_id[0x10] lapic_id[0x15] enabled) > ACPI: LAPIC (acpi_id[0x11] lapic_id[0x30] disabled) > ACPI: LAPIC (acpi_id[0x12] lapic_id[0x31] disabled) > ACPI: LAPIC (acpi_id[0x13] lapic_id[0x32] disabled) > ACPI: LAPIC (acpi_id[0x14] lapic_id[0x33] disabled) > ACPI: LAPIC (acpi_id[0x15] lapic_id[0x34] disabled) > ACPI: LAPIC (acpi_id[0x16] lapic_id[0x35] disabled) > ACPI: LAPIC (acpi_id[0x17] lapic_id[0x36] disabled) > ACPI: LAPIC (acpi_id[0x18] lapic_id[0x37] disabled) > ACPI: LAPIC (acpi_id[0x19] lapic_id[0x38] disabled) > ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x39] disabled) > ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x3a] disabled) > ACPI: LAPIC (acpi_id[0x1c] lapic_id[0x3b] disabled) > ACPI: LAPIC (acpi_id[0x1d] lapic_id[0x3c] disabled) > ACPI: LAPIC (acpi_id[0x1e] lapic_id[0x3d] disabled) > ACPI: LAPIC (acpi_id[0x1f] lapic_id[0x3e] disabled) > ACPI: LAPIC (acpi_id[0x20] lapic_id[0x3f] disabled) > ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1]) > ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0]) > IOAPIC[0]: apic_id 0, version 0, address 0xfec00000, GSI 0-0 > ACPI: IOAPIC (id[0x01] address[0xfec80000] gsi_base[32]) > IOAPIC[1]: apic_id 1, version 0, address 0xfec80000, GSI 32-32 > ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) > ERROR: Unable to locate IOAPIC for GSI 2 > ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) > ERROR: Unable to locate IOAPIC for GSI 9 > Using ACPI (MADT) for SMP configuration information > ACPI: HPET id: 0x8086a301 base: 0xfed00000 > SMP: Allowing 16 CPUs, 0 hotplug CPUs > PM: Registered nosave memory: 00000000000a0000 - 0000000000100000 > PM: Registered nosave memory: 00000000bf679000 - 00000000bf68f000 > PM: Registered nosave memory: 00000000bf68f000 - 00000000bf6ce000 > PM: Registered nosave memory: 00000000bf6ce000 - 00000000c0000000 > PM: Registered nosave memory: 00000000c0000000 - 00000000e0000000 > PM: Registered nosave memory: 00000000e0000000 - 00000000f0000000 > PM: Registered nosave memory: 00000000f0000000 - 00000000fe000000 > PM: Registered nosave memory: 00000000fe000000 - 0000000100000000 > Allocating PCI resources starting at c0000000 (gap: c0000000:20000000) > Booting paravirtualized kernel on Xen > Xen version: 4.0.1-rc4-pre (preserve-AD) (dom0) > NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2 > PERCPU: Embedded 30 pages/cpu @ffff880028050000 s90392 r8192 d24296 u122880 > pcpu-alloc: s90392 r8192 d24296 u122880 alloc=30*4096 > pcpu-alloc: [0] 00 [0] 01 [0] 02 [0] 03 [0] 04 [0] 05 [0] 06 [0] 07 > pcpu-alloc: [0] 08 [0] 09 [0] 10 [0] 11 [0] 12 [0] 13 [0] 14 [0] 15 > Xen: using vcpu_info placement > Built 1 zonelists in Zone order, mobility grouping on. Total pages: 8007770 > Policy zone: Normal > Kernel command line: ro root=UUID=23dec242-9269-4f57-8433-2e7b5c468cf1 LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us console=hvc0 earlyprintk=xen > PID hash table entries: 4096 (order: 3, 32768 bytes) > Initializing CPU#0 > DMA: Placing 64MB software IO TLB between ffff880020000000 - ffff880024000000 > DMA: software IO TLB at phys 0x20000000 - 0x24000000 > xen_swiotlb_fixup: buf=ffff880020000000 size=67108864 > xen_swiotlb_fixup: buf=ffff880024060000 size=32768 > Memory: 31809872k/33554432k available (4508k kernel code, 1058716k absent, 685844k reserved, 4106k data, 940k init) > SLUB: Genslabs=14, HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2 > Hierarchical RCU implementation. > NR_IRQS:4352 nr_irqs:4352 > ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) > ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) > xen: sci override: source_irq=9 global_irq=9 trigger=c polarity=1 > xen_allocate_pirq: returning irq 9 for gsi 9 > xen: acpi sci 9 > Console: colour VGA+ 80x25 > console [hvc0] enabled, bootconsole disabled > console [hvc0] enabled, bootconsole disabled > allocated 325058560 bytes of page_cgroup > please try ''cgroup_disable=memory'' option if you don''t want memory cgroups > installing Xen timer for CPU 0 > BUG: unable to handle kernel paging request at 0000000000003908 > IP: [<ffffffff810dd2b3>] __alloc_pages_nodemask+0x9b/0x630 > PGD 0 > Thread overran stack, or stack corrupted > Oops: 0000 [#1] SMP > last sysfs file: > CPU 0 > Modules linked in: > Pid: 0, comm: swapper Not tainted 2.6.32.11-1.2.97.xendom0.fc12.x86_64 #1 PowerEdge R710 > RIP: e030:[<ffffffff810dd2b3>] [<ffffffff810dd2b3>] __alloc_pages_nodemask+0x9b/0x630 > RSP: e02b:ffffffff81689be8 EFLAGS: 00010046 > RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000 > RDX: 0000000000003900 RSI: 0000000000000001 RDI: 0000000000005220 > RBP: ffffffff81689cc8 R08: 0000000000000200 R09: ffff8807ffc2c048 > R10: 0000000000000000 R11: ffffea001bff2900 R12: 0000000000005220 > R13: 0000000000005220 R14: 0000000000000001 R15: 0000000000003900 > FS: 0000000000000000(0000) GS:ffff880028050000(0000) knlGS:0000000000000000 > CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b > CR2: 0000000000003908 CR3: 0000000001001000 CR4: 0000000000002660 > DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 > DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 > Process swapper (pid: 0, threadinfo ffffffff81688000, task ffffffff817221f0) > Stack: > 0000000000000000 ffff88000000b9c0 ffffffff81689ce8 ffffffff810dd33a > <0> ffff880000009d40 ffff880000000000 0000000000000001 0000000000000000 > <0> 0000000000000000 0000000000000000 0000000000000000 ffff88000000b9c0 > Call Trace: > [<ffffffff810dd33a>] ? __alloc_pages_nodemask+0x122/0x630 > [<ffffffff8100eaf9>] ? xen_force_evtchn_callback+0xd/0xf > [<ffffffff8100f282>] ? check_events+0x12/0x20 > [<ffffffff8110d564>] alloc_slab_page+0x59/0x5b > [<ffffffff8110d5ba>] new_slab+0x54/0x1d3 > [<ffffffff8110e072>] __slab_alloc+0x1e2/0x373 > [<ffffffff810adffe>] ? kzalloc_node+0x14/0x16 > [<ffffffff8110efe6>] __kmalloc_node+0xff/0x15b > [<ffffffff810adffe>] kzalloc_node+0x14/0x16 > [<ffffffff8144acbc>] irq_to_desc_alloc_node+0xa0/0x188 > [<ffffffff812a1127>] find_unbound_irq+0x48/0x81 > [<ffffffff812a11dd>] bind_virq_to_irq+0x7d/0x128 > [<ffffffff8100ee54>] ? xen_timer_interrupt+0x0/0x17b > [<ffffffff812a1636>] bind_virq_to_irqhandler+0x24/0x5a > [<ffffffff8100ee08>] xen_setup_timer+0x59/0xa5 > [<ffffffff81887150>] xen_time_init+0xb7/0xc0 > [<ffffffff81887948>] x86_late_time_init+0xa/0x11 > [<ffffffff81882d43>] start_kernel+0x367/0x40b > [<ffffffff818822c1>] x86_64_start_reservations+0xac/0xb0 > [<ffffffff81885fea>] xen_start_kernel+0x64f/0x656 > Code: 78 00 45 21 ec 44 89 e0 83 e0 10 89 85 60 ff ff ff 74 18 31 d2 be a0 07 00 00 48 c7 c7 c0 fc 5d 81 e8 0a 98 f6 ff e8 29 22 38 00 <49> 83 7f 08 00 0f 84 50 05 00 00 41 83 e5 0f c7 45 ac 22 01 32 > RIP [<ffffffff810dd2b3>] __alloc_pages_nodemask+0x9b/0x630 > RSP <ffffffff81689be8> > CR2: 0000000000003908 > ---[ end trace a7919e7f17c0a725 ]--- > Kernel panic - not syncing: Attempted to kill the idle task! > Pid: 0, comm: swapper Tainted: G D 2.6.32.11-1.2.97.xendom0.fc12.x86_64 #1 > Call Trace: > [<ffffffff8145e7fb>] panic+0x7a/0x133 > [<ffffffff8105b0af>] do_exit+0x7b/0x6f9 > [<ffffffff81461b6f>] oops_end+0xbf/0xc7 > [<ffffffff81037804>] no_context+0x1f3/0x202 > [<ffffffff81037990>] __bad_area_nosemaphore+0x17d/0x1a0 > [<ffffffff810379c6>] bad_area_nosemaphore+0x13/0x15 > [<ffffffff81463058>] do_page_fault+0x1a1/0x2f2 > [<ffffffff81461005>] page_fault+0x25/0x30 > [<ffffffff810dd2b3>] ? __alloc_pages_nodemask+0x9b/0x630 > [<ffffffff810dd231>] ? __alloc_pages_nodemask+0x19/0x630 > [<ffffffff810dd33a>] ? __alloc_pages_nodemask+0x122/0x630 > [<ffffffff8100eaf9>] ? xen_force_evtchn_callback+0xd/0xf > [<ffffffff8100f282>] ? check_events+0x12/0x20 > [<ffffffff8110d564>] alloc_slab_page+0x59/0x5b > [<ffffffff8110d5ba>] new_slab+0x54/0x1d3 > [<ffffffff8110e072>] __slab_alloc+0x1e2/0x373 > [<ffffffff810adffe>] ? kzalloc_node+0x14/0x16 > [<ffffffff8110efe6>] __kmalloc_node+0xff/0x15b > [<ffffffff810adffe>] kzalloc_node+0x14/0x16 > [<ffffffff8144acbc>] irq_to_desc_alloc_node+0xa0/0x188 > [<ffffffff812a1127>] find_unbound_irq+0x48/0x81 > [<ffffffff812a11dd>] bind_virq_to_irq+0x7d/0x128 > [<ffffffff8100ee54>] ? xen_timer_interrupt+0x0/0x17b > [<ffffffff812a1636>] bind_virq_to_irqhandler+0x24/0x5a > [<ffffffff8100ee08>] xen_setup_timer+0x59/0xa5 > [<ffffffff81887150>] xen_time_init+0xb7/0xc0 > [<ffffffff81887948>] x86_late_time_init+0xa/0x11 > [<ffffffff81882d43>] start_kernel+0x367/0x40b > [<ffffffff818822c1>] x86_64_start_reservations+0xac/0xb0 > [<ffffffff81885fea>] xen_start_kernel+0x64f/0x656 >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel