From 8b2b26134e5ced7ec727be8f60eb75886cfb7846 Mon Sep 17 00:00:00 2001 From: Rusty Bird Date: Mon, 27 Aug 2018 23:31:16 +0000 Subject: [PATCH] tools/qvm-sync-clock: don't start clockvm Since bda9264, a qubes.GetDate call from a VM will not cause clockvm startup. Also avoid causing it with /etc/cron.d/qubes-sync-clock.cron. Fixes QubesOS/qubes-issues#3588 --- qvm-tools/qvm-sync-clock | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/qvm-tools/qvm-sync-clock b/qvm-tools/qvm-sync-clock index 0e607f19..18e0bcf8 100755 --- a/qvm-tools/qvm-sync-clock +++ b/qvm-tools/qvm-sync-clock @@ -32,6 +32,11 @@ def main(): app = Qubes() clockvm = app.clockvm + if not clockvm.is_running(): + sys.stderr.write('ClockVM {} is not running, aborting.\n'.format( + clockvm.name)) + sys.exit(0) + p = clockvm.run_service('qubes.GetDate') untrusted_date_out = p.stdout.read(25).decode('ascii', errors='strict') untrusted_date_out = untrusted_date_out.strip()