cat /sys/devices/system/clocksource/clocksource0/current_clocksource xen
Bad. Should not be set to xen. (--> Clock Correlation Attack)
cat /sys/devices/system/clocksource/clocksource0/available_clocksource xen tsc
Probably bad. We don't want compromised VMs being able to access dom0's or any other VMs clock. I.e we probably don't want clocksource xen.
Questions:
- What does clocksource=xen do? Is there documentation on clocksource xen? -> https://github.com/QubesOS/qubes-issues/issues/1764#issuecomment-195619793 (w)
- Can we make clocksource=xen unavailable to Qubes-Whonix VMs?
Related Qubes upstream bug:
libvirt domain validation error; virsh edit issue