Here it merely tells the hypervisor that the wall clock changed (soOn 05/14/2013 12:57 AM, Jan Beulich wrote:On 14.05.13 at 17:59, John Stultz <john.stultz@xxxxxxxxxx> wrote:Huh. So what does calling HYPERVISOR_dom0_op do then?Thy hypervisor tries to control as little system and peripheral devicesHonestly, it seems a little strange to me. If you're running as dom0,On 14.05.13 at 02:52, John Stultz <john.stultz@xxxxxxxxxx> wrote:
why does HYPERVISOR_dom0_op() not cause the hypervisor to set the cmos
its virtualizing? This seems to mess with the proper virtualization
layering.
as possible, and the CMOS (including the clock) is among those not
controlled by it, but by Dom0.
it can propagate this on to DomU-s).