linux-kernel - Re: [Xen-devel] Can't boot as Xen dom0 due to commit fe055896

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1759e235-b514-7a5d-4eae-e898437bdbd2@citrix.com>
Date:   Thu, 15 Dec 2016 16:59:49 +0000
From:   Andrew Cooper <andrew.cooper3@...rix.com>
To:     Jan Beulich <JBeulich@...e.com>, Borislav Petkov <bp@...e.de>
CC:     Juergen Gross <JGross@...e.com>,
        xen-devel <xen-devel@...ts.xenproject.org>,
        Boris Ostrovsky <boris.ostrovsky@...cle.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [Xen-devel] Can't boot as Xen dom0 due to commit fe055896

On 15/12/16 16:53, Jan Beulich wrote:
>>>> On 15.12.16 at 17:46, <bp@...e.de> wrote:
>> On Thu, Dec 15, 2016 at 05:12:04PM +0100, Juergen Gross wrote:
>>> with today's kernel the system isn't coming up when booted as Xen dom0:
>> Remind me again pls, is dom0 even supposed to load microcode? Isn't the
>> hypervisor supposed to apply microcode?
> Yes, it's the hypervisor. Dom0 can at best hand the blob to it via
> hypercall, but iirc upstream Linux doesn't make use of that.

Xen has the same logic as Linux does to look for an uncompressed
microcode blob in the initrd and apply it early in boot.

If dom0 goes looking, it should see the same microcode version as it has
in its initrd.

~Andrew