From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: domains being migrated state message improvements Date: Fri, 2 May 2014 14:40:15 +0100 Message-ID: <5363A03F.3050109@citrix.com> References: <1399036605.3861.14.camel@nereid> <53639C78.2050603@citrix.com> <1399037350.6043.9.camel@kazak.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1399037350.6043.9.camel@kazak.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell Cc: sparvu@systemdatarecorder.org, xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On 02/05/14 14:29, Ian Campbell wrote: > >> I would agree that it is a little confusing. '------' means runnable >> but not running, in this case due to vcpu over subscription. > Is that not "blocked"? Blocked is any vcpu/domain pause count. For healthy domains, this is usually a yielded timeslice, which is why idle domains are almost always '-b----'. > > BTW, the "migration" referred to here is VCPU migration to another PCPU > rather than domain migration. (It came up because that's another one of > the VCPU pause flags alongside blocked et al) I do not think vcpu motion around the system is actually relevant to the problem described. ~Andrew > >> However, the information is stale by the time it is displayed. It is >> not really appropriate to be consumed by anything other than an eyeball. > Agreed. And even if someone disagrees I think it is up to those tools to > accept whatever the output is, even if that includes "nonsensical" > results. > > Ian. >