From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: Xen4.2 S3 regression? Date: Tue, 25 Sep 2012 16:52:46 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ben Guthro , Jan Beulich Cc: John Baboval , xen-devel List-Id: xen-devel@lists.xenproject.org On 25/09/2012 16:45, "Ben Guthro" wrote: > Which is one of the reasons I brought it up again. > =A0 >> = >> However, I don't see yet how this is connected to you having >> a problem only with pinned vCPU-s. > = > Well - when the command line parameter dom0_vcpu_pin exists -=A0 > it crashes without this change. It does not crash with it, or without=A0 > the command line parameter. > = > Perhaps they are unrelated. Of course they're related. Dom0 kernel is fixing itself up after S3, while hypervisor is still bringing CPUs back online. It's a race for one of dom0 kernel's running VCPUs to do a hypercall that observes that one of its other VCPUs is unschedulable (because there are no currently-online CPUs in its cpu affinity mask!). -- Keir