Anthony Liguori wrote:
> 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.

I still do not get why we need clock=vm here...

> 
>> 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.
> 

...but if this case shall be covered, I'm going to respin my series and
add the config switch. (I was just hoping to get a round it.)

Jan