Hello Daniel,
On Tuesday 17 January 2012 22:24:11 Daniel P. Berrange wrote:
On Tue, Jan 17, 2012 at 05:02:14PM +0100, Philipp Hahn wrote:
For PV, Xen implements the clock offset='utc' and clock
offset='localtime' behaviour, while for HV it implements clock
offset='variable'.
This
Hello Daniel,
Daniel P. Berrange berra...@redhat.com wrote:
On Tue, Jan 17, 2012 at 05:02:14PM +0100, Philipp Hahn wrote:
For PV, Xen implements the clock offset='utc' and clock
offset='localtime' behaviour, while for HV it implements clock
offset='variable'.
This difference is important for
For PV, Xen implements the clock offset='utc' and clock
offset='localtime' behaviour, while for HV it implements clock
offset='variable'.
This difference is important for domUs, which switch daylight saving on
there own, since the state is kept inside the VM and must be in sync
with the RTC
On Tue, Jan 17, 2012 at 05:02:14PM +0100, Philipp Hahn wrote:
For PV, Xen implements the clock offset='utc' and clock
offset='localtime' behaviour, while for HV it implements clock
offset='variable'.
This difference is important for domUs, which switch daylight saving on
there own, since the
