Am Thu, 20 May 2021 09:45:03 +0200
schrieb Olaf Hering :
> Am Thu, 20 May 2021 09:03:34 +0200
> schrieb Jan Beulich :
>
> > Just to be sure - you did not need the other patch that I said I suspect
> > is needed as a prereq?
> Yes, I needed just this single patch which moves x86_configure_nx up.
Am Thu, 20 May 2021 09:03:34 +0200
schrieb Jan Beulich :
> Just to be sure - you did not need the other patch that I said I suspect
> is needed as a prereq?
Yes, I needed just this single patch which moves x86_configure_nx up.
Olaf
pgpmf2cPPAnBx.pgp
Description: Digitale Signatur von OpenPGP
On 19.05.2021 20:42, Olaf Hering wrote:
> Am Mon, 17 May 2021 12:54:02 +0200
> schrieb Jan Beulich :
>
>> x86/Xen: swap NX determination and GDT setup on BSP
>>
>> xen_setup_gdt(), via xen_load_gdt_boot(), wants to adjust page tables.
>> For this to work when NX is not available, x86_configure_nx(
Am Mon, 17 May 2021 12:54:02 +0200
schrieb Jan Beulich :
> x86/Xen: swap NX determination and GDT setup on BSP
>
> xen_setup_gdt(), via xen_load_gdt_boot(), wants to adjust page tables.
> For this to work when NX is not available, x86_configure_nx() needs to
> be called first.
Thanks. I tried t
On 13.05.2021 12:24, Olaf Hering wrote:
> Recent pvops dom0 kernels fail to boot on this particular ProLiant BL465c G5
> box.
> It happens to work with every Xen and a 4.4 based sle12sp3 kernel, but fails
> with every Xen and a 4.12 based sle12sp4 (and every newer) kernel.
>
> Any idea what is g
On 13/05/2021 14:00, Olaf Hering wrote:
> Am Thu, 13 May 2021 13:29:32 +0100
> schrieb Andrew Cooper :
>
>> Warning: NX (Execute Disable) protection not active
> There was a knob in the BIOS, it was set to "Disabled" for some reason.
> Once enabled, the flag is seen and the dom0 starts fine.
>
> If
Am Thu, 13 May 2021 13:29:32 +0100
schrieb Andrew Cooper :
> Warning: NX (Execute Disable) protection not active
There was a knob in the BIOS, it was set to "Disabled" for some reason.
Once enabled, the flag is seen and the dom0 starts fine.
If Xen is booted with 'cpuid=no-nx', the dom0 crashes
Am Thu, 13 May 2021 13:29:32 +0100
schrieb Andrew Cooper :
> Can we first establish whether this box really does, or does not, have NX ?
According to lscpu of a native boot: no.
Architecture: x86_64
CPU op-mode(s):32-bit, 64-bit
Byte Order:Little Endian
CPU(s):
Am Thu, 13 May 2021 13:11:10 +0100
schrieb Andrew Cooper :
> If I'm counting bits correctly, that is Xen rejecting the use of the NX
> bit, which is suspicious.
I tried 'dom0=pvh,debug':
...
(XEN) mcheck_poll: Machine check polling timer started.
(XEN) Running stub recovery selftests...
(XEN) Fi
On 13/05/2021 13:22, Olaf Hering wrote:
> Am Thu, 13 May 2021 13:11:10 +0100
> schrieb Andrew Cooper :
>
>> If I'm counting bits correctly, that is Xen rejecting the use of the NX
>> bit, which is suspicious. Do you have the full Xen boot log on this
>> box? I wonder if we've some problem clobbin
Am Thu, 13 May 2021 13:11:10 +0100
schrieb Andrew Cooper :
> If I'm counting bits correctly, that is Xen rejecting the use of the NX
> bit, which is suspicious. Do you have the full Xen boot log on this
> box? I wonder if we've some problem clobbing the XD-disable bit.
Yes, it was attached.
Is
On 13/05/2021 11:24, Olaf Hering wrote:
> Recent pvops dom0 kernels fail to boot on this particular ProLiant BL465c G5
> box.
> It happens to work with every Xen and a 4.4 based sle12sp3 kernel, but fails
> with every Xen and a 4.12 based sle12sp4 (and every newer) kernel.
>
> Any idea what is go
Recent pvops dom0 kernels fail to boot on this particular ProLiant BL465c G5
box.
It happens to work with every Xen and a 4.4 based sle12sp3 kernel, but fails
with every Xen and a 4.12 based sle12sp4 (and every newer) kernel.
Any idea what is going on?
(XEN) Freed 256kB init memory.
(XEN)
13 matches
Mail list logo
