search for: rtc_mode_no_ack

Hello, In what we believe is now the final regression discovered when upgrading XenServer from Xen 4.1 to 4.3, there is an issue with RTC emulation. Win2003 SP2 is a WAET unaware operating system, whose RTC access pattern triggers Xen''s rtc_mode_no_ack logic. The result 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 uncondition...