Re: [Xen-devel] kernel bootup slow issue on ovm3.1.1

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 09.08.12 at 11:42, "zhenzhong.duan" <zhenzhong.duan@xxxxxxxxxx> wrote:
> ä 2012-08-08 23:01, Jan Beulich åé:
>>>>> On 08.08.12 at 11:48, "zhenzhong.duan"<zhenzhong.duan@xxxxxxxxxx>  wrote:
>>> ä 2012-08-07 16:37, Jan Beulich åé:
>>> Some spin at stop_machine after finish their job.
>> And here you'd need to find out what they're waiting for,
>> and what those CPUs are doing.
> They are waiting the vcpu calling generic_set_all and those spin at 
> set_atomicity_lock.
> In fact, all are waiting generic_set_all

I think we're moving in circles - what is the vCPU currently
generic_set_all() then doing?

>> There's not that much being done in generic_set_all(), so the
>> code should finish reasonably quickly. Are you perhaps having
>> more vCPU-s in the guest than pCPU-s they can run on?
> System env is an exalogic node with 24 cores + 100G mem (2 socket , 6 
> cores per socket, 2 HT threads per core).
> Bootup a pvhvm with 12vpcus (or 24) + 90 GB + pci passthroughed device.

So you're indeed over-committing the system. How many vCPU-s
does you Dom0 have? Are there any other VMs? Is there any
vCPU pinning in effect?

>>   Does
>> your hardware support Pause-Loop-Exiting (or the AMD
>> equivalent, don't recall their term right now)?
> I have no access to serial line, could I get the info by a command?

"xl dmesg" run early enough (i.e. before the log buffer wraps).

Jan

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel