I installed a basic text install of 12.2 on hyperv and all went well. The only problem is that the guest clock is gaining time.
I thought that the hyperv timesync service would sort this but it doesnt seem to be working. Its is enabled by default I checked.
Not sure where to go from here.
I know I could do a fudge with ntp but hyperv timesync should be doing sync from host to guest shouldnt it?
In the openSUSE guest I am thinking I would go into YaST / System / Date & Time / Change (button) / Check 'Run NTP as daemon" / Configure (Button) / Delete Undisciplined Clock & Add a couple of sync servers that test OK then select buttons for OK / Accept / OK and maybe another OK till complete. See if this then works as you wish.
Well, I suppose the software clock in openSUSE 12.2 has a problem, though no one else has complained of this issue outside of a VM. None the less, I am not sure why I would lose any sleep over a software clock that runs fast in a VM. You could always update the kernel version to see if it helps in any way I guess. I have a blog and bash script that can do that for you.
The point is that the guest clock should be synced to the hyperv host via timesync component in the kernel.It should just work. Timesync for guests is very important for Kerberos Authentication.I guess I could start setting up ntp on the host but this is all more config when the whole point of the hyper timesync service is that it just works.ThanksMike
> Thank You,The point is that the guest clock should be synced to the hyperv host
> via timesync component in the kernel.It should just work. Timesync for
> guests is very important for Kerberos Authentication.I guess I could
> start setting up ntp to the host and enable sntp service on the host but
> this is all more config when the whole point of the hyper timesync
> service is that it just works.ThanksMike
You are right, ntp in a guest is a no-no.
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
This is now a confirmed issue in openSUSE 12.2 as well as sles11sp2 and the hyperv maintainers are looking into it.
Since it is repro in enteprise level product I have hopes that this will be fixed.
Will post back when this is resolved.