[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: regression in recent pvops kernels, dom0 crashes early


  • To: Olaf Hering <olaf@xxxxxxxxx>
  • From: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
  • Date: Thu, 13 May 2021 14:09:53 +0100
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=citrix.com; dmarc=pass action=none header.from=citrix.com; dkim=pass header.d=citrix.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=tLLMue0pia2RSHPtu+KRxD5gYBb/zBQVw+kdxIB/vzQ=; b=hf1unGZKuU4uHtD6mJ926BvYYoubNi1v1Yg4QhnB854DrYzeWz2ZK6ar2MJVYj2xbLzAISBOHCgpdB5ioGMl5+zAsxpKzFJ+Q+kAd7JSKGyrSNxBJCSX5ypsQbo1bAB963r4c9wKhjCoOr0Rjs7bCcNYXvTXUXcz/UyEp8lXYt0P/MESwZNSOCHlidMRl9o3fEtxlgdD5cyxFF44O/FcbZ5GWQ4U8htGLUAAbZQKpBlFSi/fEdcS0SmNaq1jisNv346ZCg1/E17T92UYR/5rudaE50Tv9RYntzjTxKUkEniJBYOci4zcJNtZ8WC7KYP4eV9DnzRf3VYHtDRrwqnX9g==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ku20cUilb4VzVGm/0dCFNWBFFTMIU3hMW77YxdKICvcmhGtfjNed0iX0HztiYrUTTNi6m3MhT/Rzd/yl9m31GD3OsoE04O2lkRlJtD4+ZIY4lLIe99cC8HwoDQX1yF8kw8Yueil+hJI3Z6N2a8j7rlJeoGfLxS1I7HhIxIxoaaM2UXBZDuCbS2dxBqWSjwVWYs9kb7F0g3kno4JVomcTYHtSezjlbfWuMnk1hbzhOn5PhlVmKDv070lVgRMffNKq2zLCOvYeYHYfDs1N2o2UElGEb7KAgOwbJTn1ERVKrGesigq/CJn7Xcoq0bM6a4YQlXinvY03yzRZAfNTXryDPA==
  • Authentication-results: esa5.hc3370-68.iphmx.com; dkim=pass (signature verified) header.i=@citrix.onmicrosoft.com
  • Cc: <xen-devel@xxxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Thu, 13 May 2021 13:10:10 +0000
  • Ironport-hdrordr: A9a23:AJNt6KrgmCKZ5mqdEnP1w28aV5rReYIsimQD101hICG9Evb0qy lhppQmPH7P+VIssRQb8+xoV5PufZqxz/BICOoqTNKftWvdyQiVxehZhOOP/9SJIUbDH4VmpM VdmsZFaeEZDTJB/LvHCAvTKadd/DFQmprY+ts3zB1WPH9Xg7kL1XYfNu4CeHcGPzWvA/ACZf yhz/sCnRWMU1INYP+2A3EUNtKz3eEixPrdEGc77wdM0nj3sQ+V
  • Ironport-sdr: BP9Lngatup1QCAh0563TstMMBV3EgkQGRO1N2HDsaZ32tK94BE+XToakAvDamANOeIe2vm+MpK EQiumc7iHU8ZAaazCRNFJBVNP6Tak/wuorFG9YrnIe/RQlm7MQNsXBzgvfPAh1MdygIN0ZgIUT Im6RtWh5GY0TxfhJgUaDQg971Sx9Efb+qLNNUbc5pTJRTqjSJ6eS597rs6TqYQFQjC40ema3zv jH8Ev2j59R3cvUEUYce5jpXMxFOO/v8jJpszK1ijO0qjRLAlPl0MNKgR4G7yDd+8iD70ysR8ho g5Q=
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On 13/05/2021 14:00, Olaf Hering wrote:
> Am Thu, 13 May 2021 13:29:32 +0100
> schrieb Andrew Cooper <andrew.cooper3@xxxxxxxxxx>:
>
>> 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 again.
>
> Thanks for the help, Andrew.

Well - I wouldn't say we're quite done yet.

Clearly between sle12sp3 and sle12sp4 you've picked up a regression
where Linux decides to use NX despite its absence.

If NX is a mandatory feature now, then dom0 ought to error out cleanly
stating this fact.

~Andrew



 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.