From: "zhenzhong.duan" <zhenzhong.duan@oracle.com>
To: xen-devel@lists.xensource.com,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Feng Jin <joe.jin@oracle.com>
Subject: kernel bootup slow issue on ovm3.1.1
Date: Tue, 07 Aug 2012 15:22:50 +0800 [thread overview]
Message-ID: <5020C24A.3060604@oracle.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1101 bytes --]
Hi maintainers,
We meet a uek2 bootup slow issue on our ovm product(ovm3.0.3 and ovm3.1.1).
The system env is an exalogic node with 24 cores + 100G mem (2 socket ,
6 cores per socket, 2 HT threads per core).
After boot up this node with all cores enabled,
We boot a pvhvm with 12vpcus (or 24) + 90 GB + pci passthroughed device,
it takes 30+ mins to boot.
If we remove passthrough device from vm.cfg, bootup takes about 2 mins.
If we use a small mem(eg. 10G + 24 vcpus), bootup takes about 3 mins.
So a big mem + passthrough device made the worst case.
If we boot this node with HT disabled from BIOS. Now only 12 cores are
available.
OVM on same node, same config with 12vpcus+90GB boots in 1.5 mins!
After some debug, we found it's in kernel mtrr init that make this delay.
mtrr_aps_init()
\-> set_mtrr()
\-> mtrr_work_handler()
kernel spin in mtrr_work_handler.
But we don't know the scene hide in the hypervisor. Why big mem +
passthrough made the worst case.
Is this already fixed in xen upstream?
Any comments are welcome, I'll upload all data depend on your need.
thanks
zduan
[-- Attachment #1.2: Type: text/html, Size: 1707 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next reply other threads:[~2012-08-07 7:22 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 7:22 zhenzhong.duan [this message]
2012-08-07 8:37 ` kernel bootup slow issue on ovm3.1.1 Jan Beulich
2012-08-08 9:48 ` zhenzhong.duan
2012-08-08 14:47 ` Jan Beulich
2012-08-08 15:01 ` Jan Beulich
2012-08-09 9:42 ` zhenzhong.duan
2012-08-09 10:35 ` Jan Beulich
2012-08-10 4:40 ` zhenzhong.duan
2012-08-10 14:22 ` Jan Beulich
2012-08-13 7:58 ` zhenzhong.duan
2012-08-13 9:29 ` Jan Beulich
2012-08-13 11:08 ` Stefano Stabellini
2012-08-29 5:19 ` zhenzhong.duan
2012-08-29 18:28 ` Stefano Stabellini
2012-08-29 5:36 ` zhenzhong.duan
2012-08-30 9:03 ` Tim Deegan
2012-09-19 2:39 ` zhenzhong.duan
2012-09-19 10:29 ` Jan Beulich
2013-04-29 17:55 ` Konrad Rzeszutek Wilk
2013-04-30 10:37 ` George Dunlap
2012-08-31 9:07 ` Jan Beulich
2012-08-13 9:07 ` Tim Deegan
2012-08-07 16:26 ` Konrad Rzeszutek Wilk
2012-08-08 9:23 ` zhenzhong.duan
2012-08-08 14:43 ` Jan Beulich
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=5020C24A.3060604@oracle.com \
--to=zhenzhong.duan@oracle.com \
--cc=joe.jin@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@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).