Am Thu, 13 May 2021 13:11:10 +0100 schrieb Andrew Cooper <andrew.coop...@citrix.com>:
> 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) Fixup #UD[0000]: ffff82d07fffe040 [ffff82d07fffe040] -> ffff82d040394a17 (XEN) Fixup #GP[0000]: ffff82d07fffe041 [ffff82d07fffe041] -> ffff82d040394a17 (XEN) Fixup #SS[0000]: ffff82d07fffe040 [ffff82d07fffe040] -> ffff82d040394a17 (XEN) Fixup #BP[0000]: ffff82d07fffe041 [ffff82d07fffe041] -> ffff82d040394a17 (XEN) HPET: 0 timers usable for broadcast (3 total) (XEN) Warning: NX (Execute Disable) protection not active (XEN) Dom0 has maximum 864 PIRQs (XEN) (XEN) **************************************** (XEN) Panic on CPU 0: (XEN) Presently, iommu must be enabled for PVH hardware domain (XEN) **************************************** ... The other logs have: (XEN) Warning: NX (Execute Disable) protection not active Olaf
pgpOfLWE00c84.pgp
Description: Digitale Signatur von OpenPGP
