|
From: | Anthony Liguori |
Subject: | [Qemu-devel] Re: [PATCH 0/5] Refactor and enhance RTC configuration |
Date: | Mon, 14 Sep 2009 08:36:31 -0500 |
User-agent: | Thunderbird 2.0.0.23 (X11/20090825) |
Jan Kiszka wrote:
Dor Laor wrote:I'm in favor of sticking to clock=vm as a default. Most chances that the guest will have internet connect and the host (ala rom hypervisor) won't have.
Default behaviors only really matter for unmanaged environments. An isolated hypervisor in a rom is most certainly a managed environment. As long as there is the ability to do clock=vm, setting clock=host by default should be fine.
Except for Jamie's case of extending some license runtime, I really see no real use for RTC based on vm_clock anymore. There is some reason why other RTCs are already based on the host clock.
In general, behaving like real hardware by default and supporting odd use-cases with additional options seems like a good policy to me.
Jan
-- Regards, Anthony Liguori
[Prev in Thread] | Current Thread | [Next in Thread] |