Peter Krempa wrote:
Not every timer model is supported with each hypervisor. Explicitly mention the driver supporting each timer model. --- docs/formatdomain.html.in | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in index 77126a5..d77bf3f 100644 --- a/docs/formatdomain.html.in +++ b/docs/formatdomain.html.in @@ -1310,8 +1310,10 @@ <dt><code>name</code></dt> <dd> The <code>name</code> attribute selects which timer is - being modified, and can be one of "platform", "hpet", - "kvmclock", "pit", "rtc", or "tsc". + being modified, and can be one of + "platform" (currently unsupported), + "hpet" (libxl, qemu), "kvmclock" (xen, libxl, qemu),
xen supports hpet too, but I don't think xen or libxl support kvmclock.
+ "pit" (qemu), "rtc" (qemu), or "tsc" (libxl).
xen and libxl support rtc too. Regards, Jim