[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

On 22/05/13 11:45, Diana Crisan wrote:
--On 22 May 2013 10:21:44 +0100 George Dunlap <George.Dunlap@xxxxxxxxxxxxx>
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?
I believe Diana has tried both. Diana?
I have tested both cases with Ubuntu.
Sending the trigger is reliable if you wait for boot to fully complete.
However, if I issue it during boot it does not get executed. Any subsequent 
triggers do not get executed as well until one is sent when the vm has fully 

Right -- so what I hear you saying is, "ACPI commands issued before the OS is paying attention are ignored." I think that's expected behavior.

I can see that "Shut this vm down as soon as possible" is a useful thing to have. The problem at the moment guest OSes can ignore signals sent too early, it doesn't really seem within the scope of libxl to work around that.

You could hold off issuing shutdown commands until the guest responds to a ping; here is a rune I use for that in my test harness:

ping -c 1 -i 5 -q -w ${timeout} ${host}

This will ping ${host} every 5 seconds until it receives 1 ping back, failing with an error after ${timeout} seconds.

Alternately, you could find another xenstore key that indicates that the guest is ready to receive a shutdown command; or you could add a line to /etc/rc.local to write a xenstore key once the system is done booting.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.