On 09/03/2018 03:35 PM, Jan Beulich wrote:
On 03.09.18 at 15:24, wrote:
>> (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
>> (XEN) ACPI: LAPIC (acpi_id[0x10] lapic_id[0x20] enabled)
>> (XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x10] enabled)
>> (XEN) ACPI: LAPIC (acpi_id[0x18] lapic
>>> On 03.09.18 at 15:24, wrote:
> (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
> (XEN) ACPI: LAPIC (acpi_id[0x10] lapic_id[0x20] enabled)
> (XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x10] enabled)
> (XEN) ACPI: LAPIC (acpi_id[0x18] lapic_id[0x30] enabled)
> (XEN) ACPI: LAPIC (acpi_id[
On 09/03/2018 03:13 PM, Jan Beulich wrote:
On 03.09.18 at 13:55, wrote:
>> I ran into the situation where I got this banner in the xl dmesg...
>>
>> (XEN) ***
>> (XEN) Booted on L1TF-vulnerable hardware with SMT/Hyperthreading
>> (XEN) enabled.
>>> On 03.09.18 at 13:55, wrote:
> I ran into the situation where I got this banner in the xl dmesg...
>
> (XEN) ***
> (XEN) Booted on L1TF-vulnerable hardware with SMT/Hyperthreading
> (XEN) enabled. Please assess your configuration and choose an
Hi,
I ran into the situation where I got this banner in the xl dmesg...
(XEN) ***
(XEN) Booted on L1TF-vulnerable hardware with SMT/Hyperthreading
(XEN) enabled. Please assess your configuration and choose an
(XEN) explicit 'smt=' setting. See XSA