On 13/05/17 22:16, Andrew Cooper wrote: > On 13/05/2017 21:05, PGNet Dev wrote: >> On 5/13/17 12:59 PM, Andrew Cooper wrote: >>> Ok. Lack of a clocksource is to be expected. >>> >>> The reason why the HPETs are unavailable is that dom0 is not a position >>> to program them; dom0 doesn't know what Xen has set up in the IDT. >>> >>> Use `xl dmesg` to get to the hypervisor dmesg log. You should see >>> mention of the HPET in there if Xen has found it. >> >> back to the error at hand ... >> >> xl dmesg | grep -i hpet >> [ 1.365876] hpet_acpi_add: no address or irqs in _CRS >> [ 1.365876] hpet_acpi_add: no address or irqs in _CRS >> >> again, only present when booting with Xen. >> >> same kernel, no Xen, no such error. > > We don't have code like that in upstream Xen. No function with that > name, or a string which looks like that error message.
This is a Linux kernel message. Juergen
