search for: rtc_no_ack

...is that the domain falls into a tight loop reading RTC RegC, whoes value is always 0xc0. I have confirmed that switching Xen back to RTC strict mode fixes the regression, but I am presuming that this alone would be an unpopular fix upstream. At the moment, HVMloader unconditionally advertises the RTC_NO_ACK bit in the WAET table, and Xen unconditionally decides that the domain has been informed that it should not ack RTC interrupts as per the specification. This logic is broken. There is no guarantee that the domain has read the WAET table, but even if it has, there is no guarantee that it will act...