From: Alex Bligh <alex@alex.org.uk>
To: Ian Campbell <ian.campbell@citrix.com>,
Diana Crisan <dcrisan@flexiant.com>
Cc: Anthony Perard <anthony.perard@citrix.com>,
Stefano Stabellini <stefano.stabellini@citrix.com>,
Alex Bligh <alex@alex.org.uk>,
xen-devel@lists.xen.org
Subject: Re: Early ACPI events prevent subsequent ACPI functionality on xen 4.3 + HVM domU
Date: Sat, 18 May 2013 10:55:56 +0100 [thread overview]
Message-ID: <71194FD00ABB7415DD6106AA@nimrod.local> (raw)
In-Reply-To: <1368812151.24012.66.camel@hastur.hellion.org.uk>
Ian,
--On 17 May 2013 18:35:51 +0100 Ian Campbell <ian.campbell@citrix.com>
wrote:
>> We are using Xen-4.3-rc1 with dom0 running Ubuntu Precise and
>> 3.5.0-23-generic kernel, and domU running Ubuntu Precise (12.04) cloud
>> images running 3.2.0-39-virtual. We are using the xl.conf below on
>> qemu-upstream-dm and HVM and two identical sending and receiving
>> machines (hardware and software)
>>
>> If a dom-U HVM server is started with ACPI enabled, and an ACPI event
>> (such as shutdown or reboot) is sent to domU before the BIOS and/or
>> operating system in the dom-U has initialised ACPI, then all
>> subsequent ACPI events are ignored.
>
> I suppose something must be getting latched and since no one was around
> at the time to clear it no further events are possible. Not sure if this
> is a qemu or a guest issue though.
I can confirm it does not happen with KVM with the same guest, and it
happens with multiple Linux guests on Xen. Our test suite triggers it
every time.
It's a pain because if someone starts a server by accident and immediately
goes to shut it down, they have to do an ungraceful destroy rather than
a clean shutdown.
--
Alex Bligh
next prev parent reply other threads:[~2013-05-18 9:55 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1052133728.8634452.1368537175372.JavaMail.root@zimbra002>
2013-05-14 13:13 ` Early ACPI events prevent subsequent ACPI functionality on xen 4.3 + HVM domU Diana Crisan
2013-05-17 17:35 ` Ian Campbell
2013-05-18 9:55 ` Alex Bligh [this message]
2013-05-21 13:39 ` George Dunlap
2013-05-21 14:16 ` George Dunlap
2013-05-21 14:20 ` Ian Campbell
2013-05-21 14:34 ` George Dunlap
2013-05-21 14:42 ` Ian Campbell
2013-05-21 16:51 ` Dave Scott
2013-05-21 19:58 ` Ian Campbell
2013-05-21 15:17 ` Alex Bligh
2013-05-21 15:36 ` George Dunlap
2013-05-21 15:51 ` George Dunlap
2013-05-21 16:22 ` Alex Bligh
2013-05-21 16:45 ` Konrad Rzeszutek Wilk
2013-05-21 17:48 ` Alex Bligh
2013-05-21 19:33 ` Konrad Rzeszutek Wilk
2013-05-21 19:46 ` Alex Bligh
2013-05-22 9:57 ` Ian Campbell
2013-05-22 9:21 ` George Dunlap
2013-05-22 10:08 ` Alex Bligh
2013-05-22 10:45 ` Diana Crisan
2013-05-22 10:55 ` George Dunlap
2013-05-22 11:16 ` Alex Bligh
2013-05-22 11:50 ` George Dunlap
2013-05-22 14:43 ` Konrad Rzeszutek Wilk
2013-11-06 16:05 ` Konrad Rzeszutek Wilk
2013-11-06 16:14 ` Ian Campbell
2013-11-06 20:16 ` Konrad Rzeszutek Wilk
2013-11-07 11:24 ` Ian Campbell
2013-11-08 14:27 ` Konrad Rzeszutek Wilk
2013-11-06 16:18 ` Jan Beulich
2013-05-21 15:16 ` Alex Bligh
2013-05-21 15:23 ` George Dunlap
2013-05-21 15:59 ` Alex Bligh
2013-05-21 16:09 ` George Dunlap
2013-05-21 16:25 ` Alex Bligh
2013-05-21 16:48 ` Diana Crisan
2013-05-21 17:31 ` Sander Eikelenboom
2013-06-27 14:04 ` George Dunlap
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=71194FD00ABB7415DD6106AA@nimrod.local \
--to=alex@alex.org.uk \
--cc=anthony.perard@citrix.com \
--cc=dcrisan@flexiant.com \
--cc=ian.campbell@citrix.com \
--cc=stefano.stabellini@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).