This is the output from ​"dmesg | fgrep -i hpet":

​[    0.000000] ACPI: HPET 0x00000000BFFE274F 000038 (v01 BOCHS  BXPCHPET
00000001 BXPC 00000001)
[    0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000
[    0.000000] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff,
max_idle_ns: 19112604467 ns
[    0.000000] hpet clockevent registered
[    0.362335] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
[    0.362339] hpet0: 3 comparators, 64-bit 100.000000 MHz counter
[    0.661731] rtc_cmos 00:00: alarms up to one day, y3k, 114 bytes nvram,
hpet irqs



On 25 January 2017 at 22:17, Jonathan Morton <chromatix99@gmail.com> wrote:

>
> > On 25 Jan, 2017, at 23:13, Hans-Kristian Bakke <hkbakke@gmail.com>
> wrote:
> >
> > dmesg | grep HPET
> > [    0.000000] ACPI: HPET 0x00000000BFFE274F 000038 (v01 BOCHS  BXPCHPET
> 00000001 BXPC 00000001)
> > [    0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000
> >
> > I seem to indeed have a HPET in my VM. Does that mean that I should be
> able to use fq as intended or could the HPET be some kind of virtualized
> device?
>
> Try “dmesg | fgrep -i hpet” - that’ll also tell you whether you have
> drivers for your HPET device, and whether it is being used.
>
>  - Jonathan Morton
>
>