Re: [Xen-devel] Early ACPI events prevent subsequent ACPI functionality on xen 4.3 + HVM domU

[George Dunlap <George.Dunlap@xxxxxxxxxxxxx>]

On Tue, May 21, 2013 at 6:48 PM, Alex Bligh <alex@xxxxxxxxxxx> wrote:
> The problem isn't that a shutdown doesn't work if there are no drivers
> for it. The problem is that if you issue a shutdown when there are
> no drivers, then later issue a shutdown when there are drivers, it
> still doesn't work.

Just to be clear, the issue is if you issue a shutdown when the
drivers are partially initialized, but before the whole system has
come up.  If you issue a shutdown command in BIOS or GRUB, for
example, the toolstack returns an error and doesn't cause the "wedge".

(From the other thread of the discussion, it's not 100% clear whether
the problem is that the kernel driver isn't getting the shutdown
signal, or whether it has sent the signal but it's too early for the
rest of the kernel to heed it.)

> The second problem is that ACPI shutdown appears not to work reliably
> either (whenever issued).

I'll have another look today, but it seemed fairly reliable to me.
Just to double-check -- you are issuing the ACPI commands after the VM
has come all the way up, right?  Or are you issuing them early during
boot, like you were for the xl shutdown commands?

The other thing is that I'm using Wheezy, not Ubuntu, which may cause
a difference.

 -George

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel