All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>, Ian Campbell <ian.campbell@citrix.com>
Cc: Paul Durrant <paul.durrant@citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	xen-devel <xen-devel@lists.xen.org>
Subject: Re: ACPI shutdown unreliable with win7?
Date: Fri, 29 May 2015 14:14:25 +0100	[thread overview]
Message-ID: <55686631.7020606@citrix.com> (raw)
In-Reply-To: <55688018020000780007F06C@mail.emea.novell.com>

On 29/05/15 14:04, Jan Beulich wrote:
>>>> On 29.05.15 at 14:54, <ian.campbell@citrix.com> wrote:
>> On Fri, 2015-05-22 at 10:08 +0100, Ian Campbell wrote:
>>> If win7 doesn't shutdown given a power button request I'd be more
>>> inclined to remove the setting in osstest for those flights and let
>>> guest-stop go back to being never pass than to start making such changes
>>> to the VM config which I think would probably break the preceding
>>> suspend and migration tests (which aren't completely reliable, but are
>>> far more so than this shutdown one).
>> Does anyone have any ideas here or shall I propose:
> Unless we have a way to make an adjustment inside the guest for the
> power button to gain "shutdown" meaning, I think there's no alternative
> to the change below.

You can avoid advertising S3/S4 in the ACPI tables, which iirc causes
the same alteration to happen.

Hvmloader uses the platform/acpi_s{3,4} booleans to control whether the
relevant SSDTs are exposed.

~Andrew

  parent reply	other threads:[~2015-05-29 13:14 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-22  8:54 ACPI shutdown unreliable with win7? Ian Campbell
2015-05-22  8:59 ` Andrew Cooper
2015-05-22  9:08   ` Ian Campbell
2015-05-29 12:54     ` Ian Campbell
2015-05-29 13:04       ` Jan Beulich
2015-05-29 13:13         ` Ian Campbell
2015-05-29 14:25           ` Paul Durrant
2015-05-29 14:35             ` Ian Campbell
2015-05-29 15:06               ` Paul Durrant
2015-05-29 15:11                 ` Ian Campbell
2015-05-29 15:34                   ` Ross Philipson
2015-05-29 16:00                     ` Paul Durrant
2015-05-29 16:11                       ` Ross Philipson
2015-05-29 16:14                       ` Ross Philipson
2015-05-29 15:34               ` Paul Durrant
2015-05-29 15:56                 ` Jan Beulich
2015-05-29 15:51               ` Paul Durrant
2015-05-29 14:35             ` Jan Beulich
2015-05-29 13:14         ` Andrew Cooper [this message]
2015-05-29 13:19           ` Ian Campbell
2015-05-29 13:28           ` Jan Beulich
2015-05-29 14:00             ` Ian Campbell
2015-05-29 14:31               ` Andrew Cooper
2015-05-29 14:38                 ` Ian Campbell
2015-05-29 14:40               ` Jan Beulich
2015-05-29 14:49                 ` Ian Campbell
2015-05-29 18:55                   ` Don Slutz
2015-05-22  9:01 ` Jan Beulich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55686631.7020606@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=ian.campbell@citrix.com \
    --cc=paul.durrant@citrix.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.