On Wed, Oct 08, 2025 at 03:35:10PM +0200, Ján Tomko via Devel wrote:
> On a Wednesday in 2025, Michal Privoznik via Devel wrote:
> > From: Michal Privoznik <mprivozn@redhat.com>
> >
> > The hv-time feature was introduced in QEMU commit
> > v2.0.0-rc0~119^2~3 which means the first version the feature is
> > available in is 2.0.0. But our docs say 1.2.2. Fix it.
> >
>
> Those are libvirt versions, "qemu" means it's supported by our qemu
> driver:
Good point, we should unify how we refer to features available only in
some drivers as currently some of the forms can be confusing. But that's
work for different series.
Pavel
> commit 600bca592b2352b683856f4b7f2694f366feac36
> Author: Peter Krempa <pkrempa@redhat.com>
> CommitDate: 2014-02-10 11:30:10 +0100
>
> qemu: hyperv: Add support for timer enlightenments
>
> git describe: v1.2.1-143-g600bca592b contains: v1.2.2-rc1~149
>
> Jano
>
> > Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
> > ---
> > docs/formatdomain.rst | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/docs/formatdomain.rst b/docs/formatdomain.rst
> > index f50dce477f..fcf3ad8d29 100644
> > --- a/docs/formatdomain.rst
> > +++ b/docs/formatdomain.rst
> > @@ -2437,7 +2437,7 @@ Windows, however, expects it to be in so called 'localtime'.
> > The ``name`` attribute selects which timer is being modified, and can be
> > one of "platform" (currently unsupported), "hpet" (xen, qemu, lxc),
> > "kvmclock" (qemu), "pit" (qemu), "rtc" (qemu, lxc), "tsc" (xen, qemu -
> > - :since:`since 3.2.0` ), "hypervclock" (qemu - :since:`since 1.2.2` ) or
> > + :since:`since 3.2.0` ), "hypervclock" (qemu - :since:`since 2.0.0` ) or
> > "armvtimer" (qemu - :since:`since 6.1.0` ). The ``hypervclock`` timer adds
> > support for the reference time counter and the reference page for iTSC
> > feature for guests running the Microsoft Windows operating system.
> > --
> > 2.49.1
> >