From 770a342e617e9e5d16740a987e91aa80414749c0 Mon Sep 17 00:00:00 2001 From: lukas Date: Tue, 3 Jun 2025 18:45:32 +0000 Subject: [PATCH] docs: update virt/vm --- virt/vm.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/virt/vm.md b/virt/vm.md index 323d612..29fbb9e 100644 --- a/virt/vm.md +++ b/virt/vm.md @@ -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) \ No newline at end of file