On 08/10/2019 06:54, Roman Shaposhnik wrote:
> Sorry -- was traveling last week, but I'm still very curious to get to
> the bottom of this:
>
> On Tue, Oct 1, 2019 at 1:25 AM Jan Beulich <jbeul...@suse.com> wrote:
>> On 01.10.2019 00:38, Roman Shaposhnik wrote:
>>> Btw, forgot to attach the patch with maxcpus=2 -- interestingly enough
>>> Xen seems to hang much further down than before (basically after
>>> attempting to build out Dom0)
>> All 3 logs contain
>>
>> (XEN) TSC_DEADLINE disabled due to Errata; please update microcode to 
>> version 0x52 (or later)
> Ok. This makes some sense. Btw, in a situation like this, do we expect
> Xen to cope with a broken microcode or we always expect microcode to
> be updated?

Intel consider you to be running out-of-spec if you don't have
up-to-date microcode.  As for functioning correctly, all bets are off.

It is quite possible the updated microcode doesn't have an impact here,
but it is not worth your time or ours trying to diagnose issues in the
face of an out-of-spec system.

>
>> Please load up-to-date microcode on the system and,
> I couldn't find any kind of HP guide on how to do this on this box.
> Any chance someone here may have a pointer for me?

Here is some documentation I prepared earlier:

https://xenbits.xen.org/docs/sphinx-unstable/admin-guide/microcode-loading.html

To a first approximation, install the intel-ucode package into dom0, and
it should DTRT.

If it doesn't,
https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files is
upstream for Intel's microcode, and you can manually arrange for Xen to
find and use it.

~Andrew

P.S. I'd also appreciate any feedback you have on the microcode
documentation, because that is the style/quality I'm aiming for across
the board in the Sphinx docs, and you are possibly the first user to use
it in anger.  In particular, if things are not clear, I'd like to see
about fixing that.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

Reply via email to