From mboxrd@z Thu Jan 1 00:00:00 1970 From: "zhenzhong.duan" Subject: kernel bootup slow issue on ovm3.1.1 Date: Tue, 07 Aug 2012 15:22:50 +0800 Message-ID: <5020C24A.3060604@oracle.com> Reply-To: zhenzhong.duan@oracle.com Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4630480789698147875==" Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: xen-devel@lists.xensource.com, Konrad Rzeszutek Wilk , Feng Jin List-Id: xen-devel@lists.xenproject.org This is a multi-part message in MIME format. --===============4630480789698147875== Content-Type: multipart/alternative; boundary="------------060807030108080608060303" This is a multi-part message in MIME format. --------------060807030108080608060303 Content-Type: text/plain; charset=GB2312 Content-Transfer-Encoding: 7bit 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 --------------060807030108080608060303 Content-Type: text/html; charset=GB2312 Content-Transfer-Encoding: 7bit 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
--------------060807030108080608060303-- --===============4630480789698147875== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============4630480789698147875==--