docs: update virt/vm
This commit is contained in:
parent
13ed1d266b
commit
770a342e61
@ -2,7 +2,7 @@
|
||||
title: Machine definition
|
||||
description: Virtual machine hardware
|
||||
published: true
|
||||
date: 2025-06-03T18:37:54.590Z
|
||||
date: 2025-06-03T18:45:30.585Z
|
||||
tags:
|
||||
editor: markdown
|
||||
dateCreated: 2025-06-01T17:37:29.262Z
|
||||
@ -231,6 +231,8 @@ The *KVM clock* timer has a catchup policy, which means that a paused guest whos
|
||||
> On non realtime kernel, the KVM clock is updated every 5 minutes for all vCPUs, which may not be enough for accurate timekeeping. For that reason, "[Red Hat recommends running NTP in the virtual machine if accurate timekeeping is required](https://access.redhat.com/solutions/27865)"
|
||||
{.is-info}
|
||||
|
||||
- [Timekeeping Virtualization for X86-Based Architectures](https://docs.kernel.org/virt/kvm/x86/timekeeping.html)
|
||||
### Resources
|
||||
|
||||
- Linux Kernel documentation: [Timekeeping Virtualization for X86-Based Architectures](https://docs.kernel.org/virt/kvm/x86/timekeeping.html)
|
||||
- SUSE documentation: [VM Guest clock settings](https://documentation.suse.com/sles/15-SP3/html/SLES-all/sec-kvm-managing-clock.html#)
|
||||
- [Best practices for accurate timekeeping for Red Hat Enterprise Linux running on Red Hat Virtualization](https://access.redhat.com/solutions/27865)
|
Loading…
x
Reference in New Issue
Block a user