From mboxrd@z Thu Jan  1 00:00:00 1970
From: George Dunlap <george.dunlap@eu.citrix.com>
Subject: Re: Early ACPI events prevent subsequent ACPI
 functionality on xen 4.3 + HVM domU
Date: Tue, 21 May 2013 16:36:29 +0100
Message-ID: <519B947D.8030607@eu.citrix.com>
References: <752956577.8634488.1368537190555.JavaMail.root@zimbra002>
	<1368812151.24012.66.camel@hastur.hellion.org.uk>
	<71194FD00ABB7415DD6106AA@nimrod.local>
	<CAFLBxZYpXV5noq3pM=O-6BtbfOD765c6k_wP_x720Wz7d1jabg@mail.gmail.com>
	<CAFLBxZYCQdPU3_iTj_j-OAcXy2q0e=3-V32=xb-sXdEC4-T=6Q@mail.gmail.com>
	<1369146037.21246.89.camel@zakaz.uk.xensource.com>
	<519B85FA.6060809@eu.citrix.com>
	<86B77960F7BEC777A3C5C339@Ximines.local>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <86B77960F7BEC777A3C5C339@Ximines.local>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Alex Bligh <alex@alex.org.uk>
Cc: Ian Campbell <Ian.Campbell@citrix.com>, Konrad Wilk <konrad.wilk@oracle.com>, xen-devel@lists.xen.org, Paul Durrant <paul.durrant@citrix.com>, Stefano Stabellini <stefano.stabellini@citrix.com>, Anthony Perard <anthony.perard@citrix.com>, Diana Crisan <dcrisan@flexiant.com>, Dave Scott <Dave.Scott@eu.citrix.com>
List-Id: xen-devel@lists.xenproject.org

On 05/21/2013 04:17 PM, Alex Bligh wrote:
>
>
> --On 21 May 2013 15:34:34 +0100 George Dunlap
> <george.dunlap@eu.citrix.com> wrote:
>
>> But the problem actually has nothing to do with ACPI -- it's the PV
>> shutdown command that is getting lost after the driver registers
>> HVM_PARAM_CALLBACK_IRQ but before something else comes up that starts
>> watching ../control/shutdown.
>
> I'm puzzled as to why you say that as the problem does not appear
> without ACPI in the xl.conf file.

I can still get the same effect -- the only difference for me seems to 
be that the "window" in which I can send a shutdown with no effect it is 
shorter.  Maybe ACPI causes the extra few seconds at boot which makes it 
more likely you're going to hit it?

  -George