[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] Unable to set dom0 vcpu to 1

Thanks Ryan,

We're still seeing this problem as of changeset 10333 (which I believe
includes that patch). 

It seems as if the "vcpus" value as shown by "xm list --long 0" command
is getting set to 8, even when we boot dom0 with 16procs. In fact, vcpus
is still set to 8 even if we boot hyperthreaded to a 32x. Since the
release of procs with vcpu-set seems to key off this value, we can never
release more than 7.

m0075:~ # xm list --long 0
    (domid 0)
    (uuid 00000000-0000-0000-0000-000000000000)
    (vcpus 8)
    (cpu_weight 1.0)
    (memory 2728)
    (maxmem 15016)
    (features )
    (name Domain-0)
    (on_poweroff destroy)
    (on_reboot restart)
    (on_crash restart)
    (state r-----)
    (shutdown_reason poweroff)
    (cpu_time 1254.97341823)
    (online_vcpus 16)

brian carb
unisys corporation - malvern, pa

-----Original Message-----
From: Ryan Harper [mailto:ryanh@xxxxxxxxxx] 
Sent: Monday, June 12, 2006 11:50 AM
To: Carb, Brian A
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx; McAfee, Tommie M; Krysan, Susan;
Puthiyaparambil, Aravindh; Subrahmanian, Raj; Vessey, Bruce A
Subject: Re: [Xen-devel] Unable to set dom0 vcpu to 1

* Carb, Brian A <Brian.Carb@xxxxxxxxxx> [2006-06-12 10:44]:
> Thanks Ryan. We've experienced the wait as well (we contributed the 
> timeout loop in changeset 10043 for xm-test 
> 01_enforce_dom0_cpus_basic_pos). For some reason, though, vcpu-set is 
> not releasing procs above #7, even when we wait a long time.

There was a recent patch dealing with hotplug cpu and rcu sent to the
list by Harry Butterworth.  I think it has been committed yet but you
will probably want to try again with that patch.

Ryan Harper
Software Engineer; Linux Technology Center IBM Corp., Austin, Tx
(512) 838-9253   T/L: 678-9253

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.