Option 4 is almost as good as Option 3 (my ideal) ... AND works like a charm!
And seeing that Windows even has this option almost raises my opinion of it...Thank you @tomservo! And compliments on the username!
Last edited:
[SOLVED] Some Windows VMs start with incorrect clock
- Thread starter SteveITS
- Start date
-
- Tags
- clock clock skew windows
Option 4 is almost as good as Option 3 (my ideal) ... AND works like a charm!
And seeing that Windows even has this option almost raises my opinion of it...Thank you @tomservo! And compliments on the username!
FWIW I’ve not yet found a way to have PVE honor its own VM clock setting (sure seems like a bug).
Thanks for the registry pointer.
Thanks for the registry pointer.
I just tried it with my usual combination of bios+q35 and for better coverage efi+i440fx. Both worked fine.
First thing is making sure the hosts have the right time and timezone. Using "ssh" "cat /etc/timezone" should give you the local timezone and "date" should produce the right time and date.
My hosts RTC is running UTC and PVE is configured to assume so. Useing localtime on the host might make a difference LATER ON. I don't have an easy way to try.
To exclude interference from the guest OS I bootet a VM into grub, pressed "c" and entered the "date" command. This shows the time from the RTC. Setting "use local time for RTC" to yes indeed produced local time and "no" UTC. Both as expected.
I suggests you try the same to narrow down your problem.
First thing is making sure the hosts have the right time and timezone. Using "ssh" "cat /etc/timezone" should give you the local timezone and "date" should produce the right time and date.
My hosts RTC is running UTC and PVE is configured to assume so. Useing localtime on the host might make a difference LATER ON. I don't have an easy way to try.
To exclude interference from the guest OS I bootet a VM into grub, pressed "c" and entered the "date" command. This shows the time from the RTC. Setting "use local time for RTC" to yes indeed produced local time and "no" UTC. Both as expected.
I suggests you try the same to narrow down your problem.
If you boot a Windows VM using grub I don't think that counts...
I did try I think all combinations back then, and ended up depending on the Windows time service, hence the solved tag. Time zone is correct on the hosts.
https://pve.proxmox.com/pve-docs/chapter-qm.html#:~:text=localtime
...are you saying localtime is still false if the OS is set to Windows? (and the docs are wrong)
I did try I think all combinations back then, and ended up depending on the Windows time service, hence the solved tag. Time zone is correct on the hosts.
https://pve.proxmox.com/pve-docs/chapter-qm.html#:~:text=localtime
...are you saying localtime is still false if the OS is set to Windows? (and the docs are wrong)
No, I'm not saying that. Before I didn't actually try "default" at all, instead using the explicit "yes" and "no" options.
But I just tried and "default" produced localtime with the OS set to Windows and UTC when set to Linux. Exactly as the docs say.
The point of only booting into grub is loacting the error. If the time is wrong there the error has to be before it (i.e. with your host or proxmox), if it is right then after (i.e. in Windows)
EDIT: I tried your exact combination of "default" RTC, "i440fx"+ bios HW and OS set to windows 2019. As expected, grub shows localtime.
But I just tried and "default" produced localtime with the OS set to Windows and UTC when set to Linux. Exactly as the docs say.
The point of only booting into grub is loacting the error. If the time is wrong there the error has to be before it (i.e. with your host or proxmox), if it is right then after (i.e. in Windows)
EDIT: I tried your exact combination of "default" RTC, "i440fx"+ bios HW and OS set to windows 2019. As expected, grub shows localtime.
Last edited: