On Sat, Jan 24, 2026 at 7:25 PM <[email protected]> wrote: > I now get the time of last shutdown, which can be days in the past, until > ntp sorts it out. > Is there a way to ensure the guest clock is initialized from the host > before the guest boot starts?
If you create a VM using a Fedora installer you probably got chronyd so need: % systemctl status chronyd % sudo systemctl stop chronyd % sudo systemctl disable chronyd My experience (a decade ago) was that VM's should be configured to use the system clock, not NTP. This was a use-case where the VM was used to process files and moving data back and forth between host and VM, so we didn't want files with times in the future. There are use-cases that require special timing -- see < https://airbus-seclab.github.io/qemu_blog/timers.html> -- George N. White III
-- _______________________________________________ users mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
