Re: Early ACPI events prevent subsequent ACPI functionality on xen 4.3 + HVM domU

[Alex Bligh <alex@alex.org.uk>]

George,

> xl/libxl is working as designed. xl tried libxl_domain_shutdown() first.
> libxl saw that there were PV drivers available, so it sent the PV
> shutdown signal over xenstore and returned success.  libxl and xl have no
> way of knowing that the signal was never received, so it never falls back
> to ACPI.
>
> "xl trigger power" is a work-around because when you detect that a guest
> is stuck, you should be able to issue an ACPI shutdown and get a clean
> shutdown, even when the PV shutdown path is stuck.
>
> (In fact, as a short-term solution, you might consider just replacing "xl
> shutdown $d" with "xl trigger $d power" in your control framework.)

Yup. I think this is the best option, save for the fact that 'xl trigger
power' itself appears unreliable. We apparently need to send it multiple
times. Diana will send more details.

>> Does xl trigger reset do the same thing (i.e. a graceful shutdown)?
>> If not we'd also (I think) have to recode reboots to do a power trigger
>> then a restart.
>
> Hmm, this is what I get:
>
># xl trigger h0 reset
> libxl: error: libxl.c:4639:libxl_send_trigger: Send trigger 'reset'
> failed: Function not implemented
>
> YMMV...

Indeed. So presumably 'xl trigger power' (+/- repeats to get it
to work), wait until the domain is dead, then power it back up
again.

-- 
Alex Bligh